The solution, that accessibility advocates have been clamoring for for decades now, is to s"shift left".
replyIf you know you're going to add accessibility, which ... we have had WCAG since 2005, not knowing that at this point is negligence imho, just make sure you work with frameworks and libraries that won't require overhauling all the things when the PO or management finally get sued into letting devs actually implement it properly. If that kind of functionality takes a backseat to "stunning" and "beaituful" designs that a bunch of people can't use, we take the user out of user interface.
We should stop thinking about accessibility as if it's some kind of feature that you "add" into the product later in development. This "add it later" mentality doesn't work for security, and it definitely doesn't work for accessibility. Like security, accessibility should be baked into the product's design from the very beginning. It should be part of the product's basic requirements.
replyThe web has its own problems, but at least bad HTML is often still visible enough to repair. A custom canvas-like desktop UI can be basically a black box to assistive tech
reply