Accessibility Industry Update: November 2026
From the Desk of the Editor
November has arrived with an unusually crowded calendar of events, the need to revisit what accessibility agents are capable of, a survey collecting the salaries of accessibility practitioners, and a fresh stack of resources that you’re sure to find informative.
Standing Notes
If you are new here, welcome. We compile this update every month to keep you informed on the changing landscape of digital accessibility. Whether you are a developer, product manager, QA specialist, leader, or somewhere in between, we want to give you the context you need to stay in the know.
As always, reach out if you think we missed something, or share the link with your colleagues or partners who may benefit from some or all of this information. You can also sign up to receive these accessibility updates via email.
– The QualityLogic Editorial Team
What’s Inside
- Quick Updates
- AI-Augmented Accessibility Is a Good Idea, Until It Isn’t
- Legal Stuff
- Upcoming Conferences and Events
- What We’ve Been Reading
- Jobs and Opportunities
Quick Updates
WebAIM Opens Its Third Accessibility Salary Survey
WebAIM and the GAAD Foundation have opened the third Global Digital Accessibility Salary Survey.
If you work in digital accessibility, we encourage you to fill this out. It’s the only datapoint on compensation that our industry has (at least at the moment). It should only take five minutes, and no personally identifiable information is collected.
While salary data is always imperfect, especially across countries and job types, it can give practitioners and employers a useful reference point. The more responses, the better the information.
We look forward to reviewing the results in the coming year.
Axe-core 4.14.0 Expands Label in Name Testing
Axe-core 4.14.0 now reports violations for WCAG 2.5.3 Label in Name (added in WCAG 2.1). This requirement is important for people who interact with their computer using their voice, either due to preference or physical limitations that make it difficult to move a mouse or type on a keyboard.
The update also improves scan performance and fix guidance, and begins adding support for EN 301 549 version 4.1.1.
This feature hasn’t yet been rolled out to axe DevTools (the browser extension). However, it’s ready for use in automated tests that directly call the axe-core library.
Canada Publishes New Accessible Procurement Resources
The Canadian government recently expanded its Digital Accessibility Toolkit for procurement. The collection includes a remediation roadmap template, guidance for adding accessibility to information and communication technology procurements, and a requirements generator based on EN 301 549.
These resources are written for Canadian government departments, agencies, and suppliers, but the underlying materials are useful no matter where you happen to reside.
It’s been a while since Canada has published accessibility-related guidance or resources, so this is a promising development.
AI-Augmented Accessibility Is a Good Idea, Until It Isn’t
It’s been a few months since AI was our feature topic, mostly because the intersection between accessibility testing and AI has remained somewhat stagnant. However, we have anecdotally been seeing a huge resurgence in organizations trying to automate as much of the accessibility testing process as possible with internal tooling.
It is easy to understand the appeal. In 2026, AI models actually got good at using computers. In fact, leading models now outscore human testers on a standard computer-use benchmark. Since your agent of choice can click around with the mouse and keyboard, take screenshots, fill out forms, and even intercept screen reader output faster than humans can, why not let it in on more of the testing?
It’s a tempting prospect, to be sure. We would never say don’t investigate it because we are pragmatists here, and pragmatism in 2026 is understanding that if you don’t, you’re certain to fall behind. So by all means, do experiment and innovate. But do so responsibly and think twice before you discount the value of your human testers.
Here’s a short list of tasks that accessibility testing agents don’t do well, and that we don’t expect them to get better at for a while:
- Agents may be able to capture screen reader text output, but they can’t hear pronunciation, pauses, tone, or the natural flow of speech.
- Agents aren’t deterministic, which is to say that they almost never complete the same tasks in the same way. This makes it nearly impossible to objectively measure whether the user experience is a good one.
- Agents have no way of measuring complexity, which is a leading cause of checkout abandonment since people started monitoring the metric. A user might emotionally feel that something is not worth their time, while an AI will go full steam ahead.
- Agents often take different paths than humans do.
- Agents don’t have the ability to use multiple assistive technologies simultaneously. It’s cool when AI intercepts output from one screen reader, except half a dozen are in use today, all of which have their own quirks. And then there’s magnification, voice control, switch access, switching orientation, and more. Combine these across browsers, and the intricacy of your tests suddenly blossoms out of control.
In short: if an agent completes checkout using NVDA and Chrome, we know that one agent completed one route with one browser, one screen reader, one configuration, and the information available to it. We don’t know how much effort the route required, whether the experience made sense, how easy it was to recover from a mistake, what challenges the user ran into along the way, or whether another person with a different disability could complete it efficiently.
Until the day that everyone is using agents to do everything for them and user experience stops mattering, human-backed usability reviews remain critical.
Why Should I Trust You?
The hard truth that leaders don’t seem to want to acknowledge is that there is no script or workflow that you could ever hope to build that will eliminate the need for human review. “But you’re an accessibility testing company,” you say. “Of course you’d say that, because you sell manual audits.”
Yes and no. Most accessibility testing companies do have a clear incentive to convince you that AI is capable of less than it is (if they survive on audits alone). The ones that don’t probably have an “AI something” to sell you.
We like to think that we occupy the perfect spot in the middle because we have no shiny AI tooling to sell. Our partners want the best of the best for their needs, and so we have the freedom to explore everything the market has to offer, and you’d better believe we’ve done it. As of yet, we have found nothing that comes close to the quality of the firsthand perspective. If we do, we’ll be the first to say so.
What Should I Use AI For, Then?
AI-augmented accessibility testing is most promising when it handles narrow, repeatable work inside an expert-led process.
- Perform a code-level automated scan and fix those issues before burning tokens.
- Allow agents to navigate the page, observe screen reader output, and determine where focus order and labels fall short.
- Let AI help expand your test cases.
- Let AI take screenshots of anything that looks weird (bad contrast or stuff that refuses to resize)
- Let AI help write your tickets.
Never let AI decide whether a product is accessible.
Only humans can judge what other people actually care about comprehension, effort, efficiency, recovery, compatibility, and the ability to complete real tasks on one’s own terms.
Legal Stuff
The Colorado Attorney General’s office is preparing rules for the state’s Automated Decision-Making Technology Act and Chatbot Safety Act.
What does this have to do with accessibility? The draft rules from October 6 would require covered interfaces and notices to be reasonably accessible to people with disabilities, referencing WCAG 2.2 as an example of a generally recognized industry standard.
The formal hearing took place October 26, and the Colorado Attorney General’s rulemaking page says the office is now considering comments while preparing the final rules. The underlying laws are scheduled to take effect January 1, 2027.
The October legal update from Converge Accessibility covered Wilson v. Family Footwear Center (N.D. Ill. 2026). The gist:
- A blind individual sued Family Footwear Center, claiming that he could not use its website.
- Family Footwear Center challenged the complaint, saying that the specific shoes the plaintiff wanted to buy were discontinued, he did not establish intent to return, it had an accessibility statement, and the site was static.
- When asked to show standing by demonstrating the barriers he experienced, the plaintiff filed no evidence, so the judge ruled in favor of the defendant.
Also, the Department of Justice sued Lyft on November 9 over allegations that drivers routinely denied rides to passengers with service animals and stowable wheelchairs. The complaint seeks $53 million for affected passengers, policy changes, training, and a civil penalty.
Upcoming Conferences and Events
- Accessing Higher Ground, November 16-20, Denver and online: This conference focuses on accessible media, web, and technology, with particular relevance to higher education. The program includes two days of preconference workshops followed by three days of conference sessions.
- European Accessibility Summit 2026, November 17, Brussels and online: The European Disability Forum and Microsoft are bringing together disability advocates, policymakers, accessibility experts, and industry representatives. The agenda includes implementation and enforcement of the European Accessibility Act, accessible technology, procurement, and artificial intelligence.
- Canadian Disability Tech Summit, November 18, Toronto: This national conference focuses on assistive technology and disability innovation. It is intended for disability leaders, researchers, accessibility teams, healthcare practitioners, startups, and investors working in the disability technology ecosystem.
- VRATE 2026: Vision Without Limits, November 20, Phoenix: The Vision Rehabilitation and Assistive Technology Expo brings the blind, low vision, and DeafBlind communities together with assistive technology specialists, educators, rehabilitation professionals, researchers, and vendors.
- A11y Camp 2026, November 23 to 25, Sydney and online: Australia’s largest event for digital accessibility and inclusive design includes two conference days followed by a day of practical workshops. Topics span design, development, content, policy, research, and strategy.
What We’ve Been Reading
- Accessibility Considerations Toolkit – Microsoft: Microsoft’s toolkit organizes access considerations, assistive technology patterns, usability heuristics, and evaluation guidance for people building AI agents and evaluation tools.
- Why Accessibility Overlays Don’t Work – Lainey Feingold, Alison Walden, and Matt Vitale: Walden and Vitale tested overlays on state government websites and found they left barriers unresolved, sometimes making content harder to read or breaking functionality.
- Debunking AI Agent Accessibility Claims and Solving AI Alignment for Accessibility – Dylan Barrell (Deque): Barrell argues that an agent’s accessibility claims need independent, deterministic verification. The article reflects Deque’s product approach, but the verification principle applies more broadly.
- Sustainable Accessibility: Compliance, Culture, and Capability – TetraLogical: We’ve shared this one before, and we’re sharing it again because it remains an excellent starting point for anyone who feels accessibility is too complicated or doesn’t know where to begin. The article explains the purpose of an audit (to provide a snapshot), then connects compliance with the skills, support, and organizational culture needed to keep producing accessible work.
- Web Accessibility Smoke Testing – Rachele DiTullio: Six quick browser checks that developers should always complete before submitting a pull request.
- A Design System Is What It Does – Matt Henry: Examines how design system defaults reveal which users and use cases the system prioritizes, using USWDS (the U.S. government web design system) and shadcn as examples.
- Reflections from TPAC 2026 – Hidde de Vries: A useful report on WCAG 3, the modernization of ATAG, accessibility support, and W3C policy work.
- ACD – Accessibility Compatibility Data: A look at the effort to create machine-readable support data for browser, operating system, and assistive technology combinations.
Jobs and Opportunities
QualityLogic does not explicitly endorse these companies. Should you decide to seek a position with one of them, please perform your own due diligence.
- Accessibility Specialist at Coforma (Remote in select U.S. states)
- Software Engineer, WebKit Accessibility at Apple (Cupertino, California)
- Instructional Technologist, Digital Learning and Digital Accessibility at Elon University (Charlotte, North Carolina)
Looking for more opportunities? Check out A11yJobs, Indeed, and LinkedIn.
Thanks for Reading!
That’s a wrap for this month.