AI & Accessibility

W3C’s Plan for the Agentic Web Puts Accessibility First on Paper. Here Is What It Leaves Open.

In October 2026 the W3C Strategy Team published a discussion paper on the web in the AI era, with a nine-point declaration and a proposed Agentic Web Working Group. It says accessibility for people comes first and warns against bending ARIA for agents. We read it in full: where it protects disabled users, and where consent, handoff and agent-mediated access are still unwritten.

The Accessibility.build Team
14 min read

On 21 October 2026 the World Wide Web Consortium published a discussion paper called W3C and the State of the Web in the AI Era. It was prepared by Philippe Le Hegaret, W3C’s VP of Technical Strategy, and collects the Strategy Team’s view of how the web’s technical agenda should change now that AI agents do not just read websites but click, type and buy on them. It was written to start discussion at TPAC 2026, W3C’s annual community meeting, and was presented to the Web and AI Interest Group on 29 October.

We have argued on this blog that the web is being made accessible for AI agents rather than for disabled people: businesses are fixing the accessibility tree because agents read it, not because screen reader users have been asking for years. So the obvious question is which way W3C leans. We read the whole paper. The short answer is that it leans the right way in its principles and in one specific, useful recommendation about ARIA, but the parts that will decide how agents actually behave (consent, human handoff, forms, payments) are written without disabled people in view.

A note on status: this is a discussion paper from W3C staff, not a standard, a W3C Statement or a consensus position. Its recommendations are proposals that the Strategy Team says it will take to each group. The page has been revised since publication (its revision stamp is dated 29 October), so we describe the version online on 18 November 2026.

The paper at a glance

  • What it is: a Strategy Team discussion paper, finalized on 20 October 2026 and announced the next day, seeking feedback from W3C Members and the public. The paper notes it was developed with AI assistance, with its human editor taking full responsibility.
  • The declaration: a proposed nine-point statement of the value of the web in the AI era, meant to extend the existing Ethical Web Principles and the Ethical Principles for Web Machine Learning rather than replace them.
  • The new group: a proposed Agentic Web Working Group, with WebMCP, agent identity, permissions and transparency in its orbit, and an explicit brief to work out the relationship between WebMCP, HTML and ARIA.
  • The central claim: agents have not bypassed the browser for APIs. Services keep relying on websites because the browser already provides sandboxing, authentication, trust and a point where a human can step in.
  • The accessibility recommendation: guidance from the ARIA and APA groups that instructions aimed at agents must not degrade the accessibility tree, plus guidance against prompt injection through ARIA.
  • How to respond: the public-webai@w3.org mailing list or issues on the w3c/webai-roadmap GitHub repository.

Where accessibility shows up in the paper

Accessibility has no section of its own, but it appears in five places.

1. As a named risk

The risks section lists accessibility alongside security, privacy and trust. It makes four points: optimizing ARIA for agents may break the experience for humans; generated alt text may be inaccurate and should not entirely replace authored descriptions or the author’s intent; bias in training data can misrepresent what users need; and AI may amplify the accessibility debt already sitting in large codebases. The alt text point links to a draft from W3C’s Accessible Platform Architectures (APA) Working Group on the accessibility of machine learning, which gives the example of an automated description of a bar chart that is technically accurate and tells the reader nothing about the data.

2. As an opportunity

The opportunities list is generous: generated audio description and sign language, richer real-time captions, translation, read-aloud, adaptive layouts, reading inaccessible documents without OCR, and summaries for neurodivergent readers. It also lists using and improving poorly coded content, a phrase we return to below.

3. In the declaration

The first of the nine points says the web is for all people, including people who choose to use agents, and that agents serve people. The seventh is the one this site would have written: “Accessibility for people comes first.” It goes on to say that semantics, alt text and author intent are not to be repurposed for machines at the expense of humans. Other points matter for disabled users too: consequential actions need real human consent, people can see what an agent did and undo it where possible, and there should be no AI-only side channels that replace the human web.

4. In what the community said

W3C surveyed 48 groups about AI and half replied. The paper reports that ARIA participants cautioned against bending human-centred semantics to suit agents, and that the Timed Text Working Group and Media and Entertainment Interest Group set up a task force (AIRFOT) on requirements for AI-sourced captions. Nearly half of W3C groups have not answered at all.

5. In the work plan

Two concrete items follow. The ARIA Working Group is asked to draft guidance against agent-oriented misuse of ARIA, including prompts placed in aria-label. And every group whose technology agents already use is asked to write two paired lists, modelled on how APA’s Research Questions Task Force documents user requirements: what an agent needs to act reliably, and what a person needs to stay safe and in control. Where the two conflict, the paper says, the person’s needs win, and it cites the ARIA discussion as the reason. APA itself gets the row on how agents and assistive technology can share the accessibility tree without degrading it, paired with screen reader and cognitive accessibility needs in agent-mediated tasks.

Where the paper genuinely helps

The ARIA recommendation is the most important accessibility sentence in the document, and it is aimed at a real, current problem. Once teams learn that agents read the accessibility tree, the temptation is to write for the agent: stuff an aria-label with keywords or task hints, add an aria-description telling a model what to do, or hide machine-only text from sighted users with ARIA tricks. Every one of those strings is also read aloud to a screen reader user. A W3C position that agent instructions must not degrade the tree, together with a security framing (prompts in aria-label as an injection vector), gives accessibility teams something better than a style preference to point to when someone proposes it.

The conflict rule matters too. Saying in advance that the person’s needs win over the agent’s is a commitment, and the paper credits the ARIA discussion for it, which suggests the accessibility community’s warnings reached the strategy level. It also sits on solid ground: the Ethical Web Principles, which the declaration would extend, already say the web platform must be accessible to people with disabilities and should enable a fully accessible end-user experience.

And the paper takes a privacy issue seriously that disabled people rarely see named in AI policy: fingerprinting. Among the Privacy Working Group’s proposed actions is examining whether assistive technology adaptations can identify users, which picks up a TPAC breakout about people whose access needs become a tracking signal.

Where accessibility is under-specified

Disabled people are present by implication only

The words disability and disabled do not appear anywhere in the paper, and nor does WCAG. Accessibility is discussed as a property of semantics and content. Disabled people appear only obliquely: neurodivergent readers in the opportunities list, screen reader and cognitive needs in one row of a table, assistive technology in two passing mentions. That matters most in the sections that will turn into specifications.

Consent and handoff are written for a generic user

Human handoff is listed as a main gap for agents on the web, and the proposed Agentic Web Working Group is to own handoff and consent patterns. The paper worries, rightly, that confirmation dialogs cause prompt fatigue, and asks the Security Interest Group what makes a confirmation trustworthy. It never asks whether that confirmation can be perceived and operated by a screen reader user, a switch user or someone with a cognitive disability. If the moment an agent hands control back to a person is a modal that traps focus badly, an unlabelled approve button or a timed prompt, the safeguard fails exactly the people most likely to be using an agent in the first place. The paired user requirements for forms say review before submit and no silent autofill of sensitive data; for payments, spending caps and clear receipts. None of them says the review or the receipt must be accessible.

There is a structural reason for this. In the requirements table, the new Agentic Web group’s user column lists consent, visibility of what the agent did and choice of agent. Screen reader and cognitive needs are assigned to APA, a horizontal group. That is normal W3C practice, but it means accessibility reaches the new group through review, not as one of its own requirements.

The agent as a workaround

The first point of the declaration speaks of people who choose to use agents. For many disabled people an agent is less a choice than a way round a site that does not work with their assistive technology, and the opportunities list openly includes agents that use poorly coded content. That is a real benefit today. But the paper does not say whether access through an agent counts as access, or whether a site that an agent can navigate and a keyboard user cannot is acceptable. It also notes that agents prefer markdown and structured data to HTML and would benefit from explicit descriptions alongside existing accessibility information. The declaration rules out side channels that replace the human web, but a clean channel for agents that sits beside a broken human one is not addressed. That is the scenario our earlier piece warned about, and it is still open.

What to do while W3C deliberates

None of this is a standard yet, but the direction is clear enough to act on now:

  • Keep agent instructions out of ARIA. Accessible names and descriptions are for people. If you want to give agents more context, use visible text, structured data or a separate documented mechanism, never strings a screen reader will announce.
  • Do not let generated alt text replace authored alt text. The paper and the APA draft agree that machine descriptions miss intent. Treat them as a draft for a human to check against success criterion 1.1.1.
  • Make every confirmation step accessible. Any point where an agent or your own flow asks a human to approve, review or undo should meet the same bar as checkout: proper names and roles, managed focus and error prevention for legal and financial commitments.
  • Measure the human experience, not the agent’s. If an agent completes a task and a screen reader user cannot, the site is not accessible. Test both, and fix the second first.
  • Respond to the paper. W3C is asking for feedback. Accessibility practitioners are well placed to point out where consent and handoff need explicit accessibility requirements.

Our resources for the parts you can fix today:

The verdict

On the question we started with, W3C’s strategy paper keeps people at the centre in its principles, and on ARIA it goes further than we expected, naming the exact failure the accessibility community has been warning about and proposing guidance against it. Where it falls short is in the machinery: consent, handoff, forms and payments are being designed for a user who can see the confirmation dialog. If the Agentic Web Working Group is chartered, the test of the seventh point will be whether accessible handoff is written into its own requirements rather than left for horizontal review to catch.

Sources

Written by
The Accessibility.build Team

The Accessibility.build team publishes practical guides, tools, and research on web accessibility, WCAG compliance, and inclusive design.

Found this useful? Share it.

Prefer Accessibility.build on Google

Add us as a preferred source and Google will show our new articles and research more often in your Top Stories and AI Overviews.

Add as a preferred source on Google

Essential Accessibility Resources

Comprehensive tools, checklists, and guides to help you create inclusive digital experiences

How to Use ARIA: Roles, States & Properties

The cornerstone guide to using ARIA correctly: the five rules of ARIA, when native HTML wins, roles vs states vs properties, accessible names (aria-label vs aria-labelledby vs aria-describedby), landmark roles, the aria-hidden traps that break keyboard users, live regions, and the most common ARIA mistakes, mapped to WCAG 2.2
how to use aria
using aria
aria accessibility
View guide

Web Accessibility by Industry

Average detected accessibility errors per home page across 29 industry sectors and 17 languages, showing why regulated sectors such as government and education lead while retail trails
accessibility by industry
View resource

Accessibility by Industry

Industry-specific accessibility compliance guides
industry accessibility
View resource

Other posts filed under AI & Accessibility.