# Machine Consumers Make Semantic Markup a Commercial Requirement ## Claim AI agents parse the same accessibility tree that assistive technology reads, so correct semantic markup becomes a revenue condition for any site that wants agents to complete transactions on it, not only an ethical obligation to human users. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when an agent completes a task (purchase, form submission, booking) by reading page structure and acting on named, labeled controls, and the business outcome depends on task completion. - Breaks when agents route around bad markup using vision models or site-specific integrations — that weakens the commercial argument without touching the human-accessibility case, which stands on its own regardless. - Does not establish how often agent-driven purchase flows currently fail on inaccessible stores; that measurement doesn't yet exist. ## Evidence Jessica Lyschik's compressed line: "An AI agent is a screen reader." Google announced (per Lyschik, unsourced in the transcript) a focus on accessibility for AI agents. Her example: an agent asked to buy coffee beans can only pick the product, add to cart, and check out if the shop exposes correct elements and accessible names — the same technical requirement a screen-reader user depends on. The analogy is strong because it names the shared mechanism (both consume the accessibility tree rather than the visual rendering), not just a surface resemblance. ## Links - [[WordCamp Europe 2026 MOC]] — accessibility work repricing once agents read the same tree assistive technology does - [[3. Resources/Permanent Notes/Adoption Gaps in Standards Are Usually Documentation Gaps]] — because extends; same source, the documentation gap this note argues for closing is what would make agent-readiness achievable at scale - [[3. Resources/Permanent Notes/Native HTML Semantics Beat Re-Implemented ARIA]] — because applies-in; native semantics are exactly what both screen readers and agents can reliably parse - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in; agent-readiness of the web as a design constraint - [[3. Resources/MOCs/Accessibility & Disability Inclusion MOC]] — the commercial argument for the same semantics assistive technology depends on ## Tests / falsifiers - Run matched accessible vs. inaccessible commerce flows through an agentic purchase task and compare completion rates. If accessible and inaccessible flows complete at similar rates, the commercial argument is weaker than claimed. - If agents increasingly succeed via vision-model page understanding regardless of markup quality, the "revenue condition" framing loses force even as the human-accessibility case remains untouched. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [226 – Jessica Lyschik on Why Accessibility in WordPress Themes Is Easier Than You Think](3.%20Resources/Readwise/Articles/%23226%20–%20Jessica%20Lyschik%20on%20Why%20Accessibility%20in%20WordPress%20Themes%20Is%20Easier%20Than%20You%20Think.md) — WP Tavern Jukebox #226.