{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiatyhdqt2qggazdanuwimcvbbn5eit334vspu3b4fmab2aayveutq",
    "uri": "at://did:plc:mz7h4r2iyp2egghuqaolnsev/app.bsky.feed.post/3mo57ptohpmg2"
  },
  "path": "/forum/accessibility-advocacy/if-accessibility-was-treated-engineering-or-right-not-favour",
  "publishedAt": "2026-06-12T07:40:39.000Z",
  "site": "https://applevis.com",
  "textContent": "If accessibility were treated like engineering, we would not still be writing newsletters in 2026 saying:\n“Here are the five most common accessibility issues. Please try harder.”\nWe have known these issues for decades.\nBad contrast.\nMissing alt text.\nUnlabelled form fields.\nAnonymous buttons.\nBroken document structure.\nBad ARIA.\nThese are not mysterious edge cases. They are not advanced accessibility theory. They are not the sacred mysteries of inclusive design.\nThey are recurring, measurable, preventable failures.\nAnd 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.\nAt some point, this stops being an awareness problem.\nIt becomes an engineering failure.\nIf a build pipeline can stop code shipping because of a syntax error, it can stop code shipping because a form field has no label.\nIf 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.\nIf a design system can enforce brand colours, spacing, typography, and component behaviour, it can enforce contrast, names, labels, headings, and actual assistive technology output.\nThis stuff should not depend on whether the right person remembered the right checklist on the right Tuesday afternoon.\nThat is not engineering.\nThat is hope.\nAnd accessibility is still treated far too often as hope.\nHope the developer cares.\nHope the designer remembers.\nHope the content editor has been trained.\nHope the procurement team asks the right question.\nHope the disabled user complains politely enough.\nHope the organisation feels embarrassed for long enough to fix it.\nBut disabled people’s access to information, services, money, medicine, education, work, travel, culture, and public life should not depend on hope.\nIt should not depend on kindness either.\nKindness 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.\nIt is part of whether the thing works.\nA button without a name does not work.\nA form field without a label does not work.\nA page that cannot be navigated non-visually does not work.\nA service that silently excludes people and then calls itself digital transformation does not work.\nThe 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.\nA checklist is not a control.\nA webinar is not a fix.\nA guideline is not an interlock.\nA request for vigilance is not a safety system.\nIf 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.\nAnd then human accessibility expertise could move where it actually belongs up a level.\nNot endlessly re-explaining alt text and labels but asking the real questions.\nCan the journey be completed?\nCan the user recover from error?\nDoes the service make sense through assistive technology?\nDoes the system preserve dignity?\nWhere do people give up?\nWhat information casualties are we not counting because the person simply closed the tab?\nThat is the scandal at the heart of this.\nThe 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.\nAccessibility treated as a favour says: “Please care more.”\nAccessibility treated as a right says: “You do not get to exclude people by accident and call the system successful.”\nAccessibility treated as engineering says: “Known failures should not be shippable.”\nThat is the change I want.\nNot more guilt.\nNot more awareness theatre.\nNot another annual ritual of telling the same conscientious people what they already know.\nBuild the horn.\nInstall the interlock.\nCount the casualties.\nStop pretending advice is the same as repair.\nBecause 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.\nThe problem is that the system was never forced to learn.",
  "title": "If Accessibility was treated like engineering or a right, not a favour!"
}