Three perspectives that keep accessibility off the agenda
Front-end developers share a job title but often little else. Views on accessibility diverge just as widely, and looking at three recurring stances may help bridge the gap between the people who use websites and the people who build them.

The developer who feels attacked
“I just don’t know how developers don’t think about accessibility.”
Building for the web demands more than HTML, CSS, ARIA and JavaScript. Careers accumulate package management, workspaces, code generators, collaboration tooling, asset loading and management, CDN and bundle optimizations, unit, integration and visual regression tests, browser integration tests, code reviews, linting, formatting, semantic versioning, security, deployment, rollbacks, continuous delivery and more. Only a small fraction of the world’s population can do all of this, and shipping something that works feels great.
So when an accessibility expert effectively says you have not only been unskilled but wrong for years, the reaction is defensive. The dissonance is heavy: you did the clever work, and in the process told a whole group of people that they do not matter. It is understandable that a developer would rather stay in the story where they are still clever and the lone expert is easy to ignore.
The user who has stopped expecting to be heard
“I feel like I don’t matter at all.”
People who rely on assistive technology often find sites unusable. Poor color contrast makes text unreadable; nested interactive elements can block someone from logging in to pay a utility bill or buy essentials; a shop whose buttons are divs and cannot be reached by keyboard may be hopeless even as it looks interactive to sighted visitors.
That frustration is frequently born by the people already trying to deliver more inclusive products, and the result is a negative feedback cycle: some technologists opt out of listening because “it’s rude”, while others buckle under the emotional weight of the work. Users who have been ignored so long feel they are screaming into a void, and being loud enough to demand the treatment the law affords them often seems like the only way to be acknowledged.
The designer who treats contrast as censorship
“I know it doesn’t pass color contrast, but I feel like it’s just so restrictive on my creativity as a designer. I don’t like the way this looks, at all.”
Inclusive design gets cast as a dampener on creative freedom. But web design is not physical art: it is for the web, and its artistic vision must be usable by everyone. The fix is to move the conversation forward — you just have not found the right design yet. Beautiful and accessible is not a choice between two options.
Why a retrofit never happens
Other stances are familiar: the project manager who wants to ship features and promises to return to accessibility later, the developer who jokes that blind people would not use the internet anyway, or who will care only “once browsers make them do it.” We know how these play out. The retrofit never comes; the company pays to build the product, pays for an audit, then pays again when the audit shows that retrofitting costs more than starting over.
The deeper problem is timing. Designers and developers learn accessibility far too late. A developer who began with JavaScript can be technically correct from a JavaScript point of view yet leave out many people, the way someone who learned only a language’s slang cannot be understood by its native speakers.
The minimum viable product for anything web-related therefore needs to be accessible: documentation with accessible code samples, designs with accessible annotations, conference talks that cover accessibility, and internal tooling that is itself accessible.
Existing code, existing content
None of that repairs what already exists — articles, talks, libraries, nice tools that emit inaccessible code, popular CSS frameworks that ignore tab order or color contrast. Punishing the people behind it yields nothing. Progress comes from compassion and curiosity, because guilt is not a sustainable driver.
Concrete gaps remain. Google Developer training covers only the super basic parts of accessibility. JavaScript frameworks get caught up in their own cleverness and forget that HTML exists. Ember had been around for about eight years before adding an accessibility-focused community group, though it has advanced since. React needed a separate router in Reach. Vue has not begun to address accessibility in the core framework publicly, despite community efforts. Accessibility engineers have long asked for inert to be implemented natively in browsers, and it is often underfunded and deprioritized.
Curiosity still points somewhere better: the accessibility object model, where our markup is translated by operating systems and fed into assistive technology. Technologists who once debugged for hours over a missing semicolon already know how to develop compassion through logical thinking, and they already know how to learn hard things — tests, CSS, that one API forever burned into memory. Accessibility is the next one.
Action steps
Improve yourself
- Follow people with disabilities on social media to learn from their experience. Listen, don’t argue, don’t tone police, and attend to what they are telling you.
- Retrofit your knowledge. Write the next component in HTML first, then add JavaScript. Learn what HTML and the browser give you for free, and take courses focused on accessibility for engineers.
- Turn on a screen reader. Learn the settings: text-only mode, changing the voice, stopping speech or speeding it up, browsing by headings, listing links, and the keyboard shortcuts.
Bonus challenge: Build accessibility tooling. The open source A11y Automation Tracker catalogues automation that could exist but has not been created yet.
Fix the code you already have
Treat the following as critical blockers and use them to make the code better rather than to feel bad:
- Nested interactive elements, such as a button inside a link or a button inside a button.
- Missing or non-associated labels on input fields.
- Keyboard traps that halt users in their tracks.
- Images that carry meaning but lack an
altattribute with a meaningful value. - Empty links, or links used where a button belongs.
The A11y Project checklist is not exhaustive but makes a good starting point. The best place to begin is where you are; the best time is today.



