A parallel structure shadows every page in your browser. The accessibility tree takes a button decorated with CSS classes, framework hashes, and utility tags and reduces it to two facts: its role and its name. Button. Sign In.
This representation exists because screen reader developers in the mid-1990s had to reverse-engineer every application individually. Microsoft's Active Accessibility, released in 1997, offered the first standardized answer: expose interface elements as structured, semantic objects. WAI-ARIA extended the idea to the web. The design premise was consistent throughout. A human who cannot see the screen needs to know what's there and what it does.
Now agent frameworks like Playwright's MCP server send that same tree to language models as their primary view of a page. Not screenshots. Not raw HTML. The accessibility tree, consuming roughly 200–400 tokens per snapshot instead of thousands for the full DOM.
Screen reader users couldn't see the interface, so the tree translated visual layout into navigable structure. Agents can see the interface, pixel by pixel, but can't reliably extract meaning from what they see. Both need the tree because pixels alone don't carry enough semantic information.
The tree was built to answer a specific question: What does this element mean to a human who will then decide what to do? Agents read those same labels and act directly. The tree tells you a button exists and what it's called. It was never designed to say whether anything should press it.
1997 · Microsoft Active Accessibility ships as a Windows 95 add-on. First OS-level attempt to expose UI elements to screen readers as structured objects.
2008 · W3C's Web Accessibility Initiative begins developing ARIA to handle dynamic web content that native HTML semantics can't describe.
2014 · WAI-ARIA 1.0 becomes a W3C Recommendation, standardizing roles like button, checkbox, dialog across browsers.
2025–26 · Agent frameworks adopt the accessibility tree as their default perception layer, using it to determine which elements are actionable.
The compliance gap · 95.9% of the top million homepages had detectable WCAG failures in February 2026, averaging 56.1 errors per page. 48.2% had unlabeled form inputs. The same missing labels that left screen reader users guessing now leave agents guessing too.
Early signal · MSAA was immediately picked up by test automation tools like QuickTest Pro and SilkTest. Machines borrowing accessibility infrastructure is nearly as old as the infrastructure itself.