Hacker News new | past | comments | ask | show | jobs | submit
recursivedoubts | on: Don't put aria-label on generic elements like divs
No one has done more damage to web accessibility than the web accessibility industry. Arcane rules like this make any sane developer throw up their hands in disgust.

I think the accessibility consultants like this state of affairs: they can threaten more lawsuits and extract more in consulting fees.

jbreckmckye | parent | next
> I think the accessibility consultants like this state of affairs: they can threaten more lawsuits and extract more in consulting fees.

I think there is truth in this. A lot of the assistive technology (AT) vendors, also sell consultancy.

Go to the Vispero career pages (who develop JAWS for Windows) and a big chunk of the jobs are remote consultancy roles advising clients on accessibility errors and selling for billable hours.

What makes a web page accessible? Why, it has to work with JAWS, of course!

Vispero makes a lot of money from this; the consultants are all in India, the clients are all in the West, so they can hoover up the difference. I get the impression most AT vendors are extremely cheap, which may explain why it takes decades for them to improve things

micromacrofoot | parent | next
It's not really arcane, a div is meaningless because it's simply a container. If you want it to have meaning you can't just add a label. If I put the word "button" on a rock, it doesn't make it a button. That's the same story here.
nostats | parent
Is this an arcane rule? "Don't label divs" and "aria-label is for when there's no content in the DOM that can be read" are pretty simple rules. Labels are ways to tell a screen reader about content it can't read, like an image or icon. Pretty straightforward.

It's way way simpler than, say, var hoisting in JavaScript.

bryanrasmussen | root | parent
it's a somewhat stupid rule. People process information differently visually than they do via aural methods. If you have a reason why something should not be read by a screen reader, because say the order you would be reading it makes sense visually but not at all aurally, then you have to jump through hoops to visually hide the aural content, and then aria-hide the visual content, and there may be more complicated things dependent on button position etc.

Not be able to aria-label anything and have the screen reader say ok I take that in priority seems badly thought out.

Also - screenreaders could have a setting to read aria-label on divs and then read the content if the user wanted it. If the user determined the labels on divs were inadequate, they would flip this setting, if they decided this seems to be working well they would just go with what the site does.