[542458]

I mostly agree… but one thing:

> And what's the price to fix it?

I’m currently doing accessibility work with an in-house web framework of reasonable complexity. 90% of the accessibility issues are relatively straightforwards. Things like keyboard usability are easy to explain to devs and behave fairly consistently across browsers.

But the last 10%… things like “what should happen to focus when you open a modal?” get messier fast (the ARIA docs give several different behaviours for several different scenarios, which means every dev who wants to open a modal needs to understand enough to correctly select the behaviour for their circumstance), especially since different screen readers can behave in different ways when encountering the same content. The cost to investigate and properly solve these can be nontrivial.

That’s not to excuse people who don’t even try for that first 80-90% of the low hanging fruit… but please forgive the designers and devs who fall short of the last 10%!

[Eduard]

The last 10 percent are hard. Welcome to software development.

[ximm]

Welcome to the world

[black_puppydog]

As a perfectly-sighted user: please don't use modals, they're basically always very frustrating.

[542458]

There are lots of scenarios where a modal is the expected way to accomplish a task. Preventing irreversible errors (Are you absolutely sure you want to delete this user’s data irreversibly?), save/load dialogs, etc. Modal overuse is a real problem (and one we’re addressing in our product), but there are some situations where they solve a real problem.

[lolinder]

OP's point is that most websites, in their experience, fail to get the easy 90%. If what you've got left is a few focus issues, it sounds to me like OP can at least accomplish their task.