←back to thread

125 points robin_reala | 2 comments | | HN request time: 0.579s | source
Show context
gampleman ◴[] No.46203385[source]
Is this really true? Messaging like this will cause a lot of developers to just give up. Most places I've worked at did accessibility at best as a best effort sort of thing. After reading this, there will be no attempts made to improve the state of affairs.

Perhaps that will be an improvement? I don't know.

replies(5): >>46203428 #>>46203474 #>>46203552 #>>46203918 #>>46204092 #
1. robin_reala ◴[] No.46204092[source]
Let’s give a concrete and catastrophic example of something I’ve seen in the wild in a professional product. A developer there had obviously seen the application role[1] in the ARIA specs, thought “I’m building a web app”, and added it to their html element.

What role="application" means to assistive tech is: “I’m building a really complex application, so I’m going to handle absolutely everything for you, I don’t want you to have any default behaviour.” This meant that the web app in question was 100% unusable for any people using assistive technology, as that was broadly as far as they’d got with accessibility support.

[1] https://developer.mozilla.org/en-US/docs/Web/Accessibility/A...

replies(1): >>46205008 #
2. tdeck ◴[] No.46205008[source]
Stories like this make me wonder if we could build a Chrome extension with a collection of crowd-sourced site-specific accessibility tweaks. Things like removing that bad ARIA tag or bodging in proper labels or tabindexes. It wouldn't be perfect, but neither is AdBlock and it offers a lot of benefit.