If Accessibility was treated like engineering or a right, not a favour!

By Charli-Jo, 12 June, 2026

Forum
Accessibility Advocacy

If accessibility were treated like engineering, we would not still be writing newsletters in 2026 saying:
“Here are the five most common accessibility issues. Please try harder.”
We have known these issues for decades.
Bad contrast.
Missing alt text.
Unlabelled form fields.
Anonymous buttons.
Broken document structure.
Bad ARIA.
These are not mysterious edge cases. They are not advanced accessibility theory. They are not the sacred mysteries of inclusive design.
They are recurring, measurable, preventable failures.
And yet year after year, we keep finding the same things, publishing the same checklists, giving the same talks, writing the same advice, and then acting surprised when the same errors come back again.
At some point, this stops being an awareness problem.
It becomes an engineering failure.
If a build pipeline can stop code shipping because of a syntax error, it can stop code shipping because a form field has no label.
If a CMS can warn you about SEO, image size, broken links, cookies, analytics, metadata, and whether your headline is “engaging” enough, it can stop you publishing an image with no useful alternative text.
If a design system can enforce brand colours, spacing, typography, and component behaviour, it can enforce contrast, names, labels, headings, and actual assistive technology output.
This stuff should not depend on whether the right person remembered the right checklist on the right Tuesday afternoon.
That is not engineering.
That is hope.
And accessibility is still treated far too often as hope.
Hope the developer cares.
Hope the designer remembers.
Hope the content editor has been trained.
Hope the procurement team asks the right question.
Hope the disabled user complains politely enough.
Hope the organisation feels embarrassed for long enough to fix it.
But disabled people’s access to information, services, money, medicine, education, work, travel, culture, and public life should not depend on hope.
It should not depend on kindness either.
Kindness is lovely. I am very pro-kindness. But accessibility is not a favour. It is not a nice extra. It is not a charitable flourish added after the real work is done.
It is part of whether the thing works.
A button without a name does not work.
A form field without a label does not work.
A page that cannot be navigated non-visually does not work.
A service that silently excludes people and then calls itself digital transformation does not work.
The accessibility field has spent a generation educating the people who were willing to listen. That work matters. But it has also allowed education to be mistaken for remediation.
A checklist is not a control.
A webinar is not a fix.
A guideline is not an interlock.
A request for vigilance is not a safety system.
If accessibility were treated like engineering, the known mechanical failures would be blocked at the point they are introduced. The tools would carry the discipline. The frameworks, CMSs, design systems, site builders, component libraries, and publishing platforms would stop accepting defects as normal output.
And then human accessibility expertise could move where it actually belongs up a level.
Not endlessly re-explaining alt text and labels but asking the real questions.
Can the journey be completed?
Can the user recover from error?
Does the service make sense through assistive technology?
Does the system preserve dignity?
Where do people give up?
What information casualties are we not counting because the person simply closed the tab?
That is the scandal at the heart of this.
The casualties are real, but invisible. There is no wreckage. No incident number. No manifest. No investigation. Someone cannot complete the task the system was built to provide, and the system records nothing.
Accessibility treated as a favour says: “Please care more.”
Accessibility treated as a right says: “You do not get to exclude people by accident and call the system successful.”
Accessibility treated as engineering says: “Known failures should not be shippable.”
That is the change I want.
Not more guilt.
Not more awareness theatre.
Not another annual ritual of telling the same conscientious people what they already know.
Build the horn.
Install the interlock.
Count the casualties.
Stop pretending advice is the same as repair.
Because if the same five failures are still dominating the web after twenty-seven years, the problem is not that disabled people have failed to explain themselves clearly enough.
The problem is that the system was never forced to learn.

Options

Comments

By TheBlindGuy07 on Friday, June 12, 2026 - 11:28

At university. And she told me that in her 5 years, accessibility was hardly mentioned as a footnote in a random slide and but for my existence she wouldn't even have noticed it.
At the same time, I'm in college doing CS too, we are 3 blind students in the program. Even before us accessibility was actually taught, I've heard that with us they are apparently redesigning some courses to enforce it even more.
It's definitely a problem in the education system in north america, as the real r and d seems to happen within the engineers at google, meta, apple and microsoft, while the universities still don't care about it at all.
Whether we hate meta or not, react for example, when properly used, is one of the best things for accessibility. Same for the popular cms. When I generate razor pages crud layout in asp there are aria tags everywhere for example, and it's a template nobody will use even for a prototype 1. The contrast is huge.

By Holger Fiallo on Friday, June 12, 2026 - 12:46

humans are not thinking being. As we get old we need it, be it glasses or hearing aid. That is accessibility. Those who work on coding and do not think of it, will need it in the future. Go figure. Long live cats.

By Ann Marie B on Friday, June 12, 2026 - 14:59

Fortunately I work at a university that does care about accessibility and we are way ahead of the game compared to other Florida universities. This was because of a complaint made by OCR regarding inaccessibility of a university webpage and now i'm highly involved in manual accessibility testing of university websites, webpages, PDFS, and the like. At the same time when departments state that they fixed X,Y, and Z related to the website, I shouldn't be finding that the issues in an initial manual review of a website are still present in the second or possibly third go around. Getting people who don't use screen readers on a daily basis to understand how time consuming it is to check a website using a screen reader is the problem. Accessibility has come a long way in the last 25 years however it still needs work.

By Brian on Friday, June 12, 2026 - 21:18

During my college days, I had a single class that actually cared about accessibility. The class was labeled, "Webpage Coding with Dreamweaver".
It was, as you might guess, a webpage coding class using Adobe Dreamweaver. Back then, Dreamweaver was not very accessible with JAWS, unless you put it into text mode. Then it was like writing code in Notepad or Notepad++.

The professor was meticulous with proofreading our code, and if we missed adding Alt text, or proper labels for buttons, edit fields, etc., she would not accept our work.

In the 20+ classes I took during my college days, that was the only class that actually gave a damn about proper accessibility. 🫤

By Omar on Friday, June 12, 2026 - 22:06

You make a compelling case for treating accessibility as engineering rather than hope, and I want to add a real-world example that takes this even further — because what I recently encountered is not an oversight or a forgotten checklist item. It is an active, deliberate architectural decision to exclude disabled users.
I am a customer of a major bank whose mobile app detects whether VoiceOver is enabled on the device. If it is, the app refuses to launch and displays the following message:
"Security Alert: For security reasons, this app cannot be used with VoiceOver enabled. Please disable VoiceOver to continue using the app."

By jim pickens on Saturday, June 13, 2026 - 07:26

How is this legal? I understand where they think they're coming from but having someone else read you the screen is certainly less secure than voiceover in headphones or at a high enough speech rate.