Lotobingo Accessibility: Feedback and Takeaways

Associated themes:
  • Web
  • Mobile
  • Beginner
  • Intermediate
  • Advanced

Publication date

Description #

We’ve all heard excuses for not making digital content accessible from people working in tech — developers, designers, product owners, marketers, and everyone else.
These kinds of remarks tend to wear down accessibility folks in their day-to-day work, whether they’re talking with clients, colleagues, or even family.
So let’s see how we can come up with a shared, constructive response to the usual lines like: “It’s too expensive,” “We don’t have time,” and plenty of others!

Accessibility Lotobingo (or LoTota11y Bingo) is a 3-part workshop.

First phase - Habits #

We build a bingo card together.

Each card has 11 cells with a number from 1 to 11, where we list the typical things people say about digital accessibility, one by one.

Duration: about 45 minutes.

Second phase - The competition #

We estimate how many times we’ve heard these phrases in our lives.

Everyone answers individually and scores each randomly drawn phrase from the set we defined:

  • Often (once a week or more): 3 points
  • Regularly (between once a month and once a week): 2 points
  • A few times (fewer than 10 times a year): 1 point
  • Never: 0 points

There’s 1 salted butter caramel up for grabs for each completed line, and whoever gets the most points on a single card wins a bag of salted butter caramels to share (or not). All subject to available stock, of course.

Duration: about 15 minutes

Third phase - The responses #

The discussion #

First, in small groups, we share our best responses — our punchiest lines — to these typical phrases.

The debrief #

Then we share the most constructive punchline with the rest of the group.

Duration: about 60 minutes

Typical phrases and their associated comeback lines from Lotobingo accessibility #

Up to now, this workshop has been run three times, and below we offer you a summary of the discussions and results.

Thank you all for the stories shared and the punchy lines we came up with together!

A11Y Ouest 2026 - Tuesday, March 31, 2026 in Rennes #

  1. Tools, overlays, and AI will fix everything!
    Who’s checking the AI? AI hallucinates and makes mistakes.

  2. It’s not a priority, we’ll deal with it at the end…
    It needs to be built into the project process and considered at every step.

  3. It’s expensive and it’ll take time
    Yes, it’s a bigger investment in time and money — but if you take it into account as early as possible, it opens your service up to more people and improves performance too.

  4. We’re not at risk, we’re too small and there aren’t enough of them
    Not addressed that day.

  5. People with disabilities don’t use it
    20% of people have a disability, and 80% of those are said to be “invisible” disabilities. It would be a shame to shut them out of your services — and to shut yourself off from that audience.

  6. We’re already at 50%, that’s good enough, we consider ourselves accessible
    Not addressed that day.

  7. It’s going to look ugly!
    If the government can do it, so can we!

  8. No need for responsive design, the spec says ...XXX....
    Not addressed that day.

  9. It doesn’t concern us, we’re not responsible
    This is everyone’s business — we’ll raise awareness so we all know what we’re talking about.

  10. The rules change too often and nobody agrees
    Not addressed that day.

  11. Am I required to do it?
    What’s your “fine” budget? Your competitors have done it — so ask yourself why, and how much ground you’re going to lose!

Accessibility Workshop at Orange - Wednesday, November 26, 2025 in Arcueil #

  1. It’s not my fault!
    Dear PO or project manager, this is everyone’s concern. You’re responsible for prioritization, and everyone can help improve it — even if you’re not the one who started it.

  2. No time, or we’ll deal with it later
    You need to do it from the start, otherwise it’ll cost you more in the end.

  3. No users with disabilities
    How do you know? Some disabilities are invisible.

  4. Too expensive or no budget
    Don’t think of it as a cost — we’re talking about an investment here! How much are you ready to spend to gain a few NPS points and 20% more customers or users? And while we’re at it, take advantage of the Black Friday deal: 2 audits for the price of 1!

  5. It’ll be ugly, or it’ll change the functionality
    There are always solutions that don’t change the look and feel or the functionality.

  6. I don’t care, or I’m not concerned
    You don’t really have a choice — there are legal obligations and the company’s CSR goals. So I’d suggest you listen to a testimonial from a person with a disability, so you can understand why it matters, or try experiencing a disability situation yourself.

  7. The team doesn’t have the skills (provide them! Too complicated!)
    The support we offer will help you feel supported and learn how to put accessibility in place in your project.

  8. I’d rather pay the fine
    Fines can add up, and there’s also a reputational hit to the brand.

  9. There’s no regulation in this country
    That was then! Since June 28, 2025, all European countries are concerned!

  10. I followed the style guide, so it’s not my fault
    Even if each component is accessible on its own, the way they work together on a page may not be — which is why testing matters.

  11. We have a tool that makes it accessible
    The site must not get in the way of users using their own tools and settings.

Paris Web 2025 - Saturday, June 28, 2025 in Paris #

  1. There are no users with disabilities
    If it’s inaccessible, then you can’t have any!

  2. It’s ugly, it kills creativity
    Creativity comes alive within constraints.

  3. The product won’t be useful to them; the project team is okay with not making it accessible
    You may not be affected today, but tomorrow you might. Think about the curveballs life can throw at you.

  4. Too expensive/Too complex
    There’s already tech debt in the product, so we might as well limit the damage.

  5. We’ll do it later, we’re waiting for the redesign
    We can start small by folding it into the changes we’re already making.

  6. Only for internal use
    What if a key person on the team becomes disabled?

  7. A specific version/interface for people with disabilities
    It works for everyone. Did you know a lot of things were first built for people with disabilities? And you’re pretty glad they were!

  8. I’m not too worried (legal risk, penalties)
    The law can change, so we need to protect our future and reduce the risks.

  9. It’s natively accessible (someone told me so)
    I’d bet it isn’t accessible. We need to test it early — and I’m going to show you why right now!

  10. What is accessibility? Confused with cybersecurity, SEO
    Not addressed that day.

  11. The overlay/AI makes my interface accessible
    A visual tweak doesn’t make your site usable with a keyboard and screen reader.