Skip to content

Comment on Implementing Web accessibility guidelines for nondisabled users (2016)parent

Comments

Cost, knowledge deficit of the designer &/or eng side, inertia.. there are a lot of reasons. Many html a11y features are as easy to implement as adding an attribute (but people are unaware) -- other things, like designing a product flow to be accessible, can't be fixed with engineering; they have to be redesigned.

My team at LinkedIn is trying to solve the eng side of this with a combination of automated tooling like linting & headless testing, reporting, etc., trying to make it as painless as possible for an engineer to fall into a pit of success re: a11y for web/mobile experiences.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.