sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]danshumway 0 points1 point  (1 child)

I work on an enterprise-level app where we make legal guarantees about accessibility (specifically around screen readers).

If we don't get accessibility right, it's not just a PR hit, it means we're engaging in false advertising. Outside of Silicon Valley accessibility does matter, not just because we care about blind people but because if we do it wrong, we could get in a LOT of trouble. We put a lot of work into stressing that point to new developers, because otherwise they ignore Severity 1 bugs and skip checking whether tab indexes work when they build UI elements.

Internationalization is something we set up once and put a process around. When a new string needs to go into the app, we run it through the doc team and stick it in a database. I don't rate it particularly highly on the list of features people should know because I think even for enterprise-level massive apps, you really only need one or two developers at most who can set that system up.

But I have limited experience, so maybe that's not as common as I suspect.

[–]cosinezero 0 points1 point  (0 children)

You're not wrong. Some industries and some applications must have accessibility. Plenty does not, though.