ARIA Anti-Patterns: Why LLMs Should Not Be Pointed at the APG

X postzeldmanOpinion

Jeffrey Zeldman highlights an article by web developer David Bushell warning against directing LLMs to the ARIA Authoring Practices Guide (APG). The APG demonstrates the ARIA specification in theory rather than accessible best practices, which should rely on native HTML instead.

Key points

  1. The ARIA Authoring Practices Guide (APG) exists to showcase how the ARIA specification works in theory for assistive technology and browser developers, not as a general guide to web accessibility best practices.
  2. The first rule of ARIA dictates that native HTML elements must be preferred whenever they provide the required semantics and behaviour.
  3. APG examples include constructs like `<div role="button">`, which should not replace a standard `<button>` element in production code.
  4. According to the WebAIM Million report, higher ARIA usage on web pages correlates with an increased rate of detected accessibility errors.
  5. Bushell strongly advises against instructing LLMs to generate components from APG patterns, which risks propagating improper ARIA usage across the web.

Why it matters

As teams increasingly adopt AI agents for front-end development, pointing models at reference specifications rather than practical semantic markup risks degrading real-world accessibility. Over-relying on ARIA instead of native HTML introduces avoidable bugs for users of assistive technologies.

Analysis

Bushell critiques the emerging workflow of prompting LLM agents with APG patterns to draft component code. Because the APG was authored to demonstrate ARIA capabilities, its examples disproportionately rely on ARIA roles rather than native HTML alternatives. Zeldman amplifies the message that accessibility relies on understanding context and adhering to the first rule of ARIA, which generative AI shortcuts often bypass.

Original post

zeldman

@zeldman · 7 August 2026

t.co/EKYchAZpgG #aria #antipatterns #a11y 2/2

7 likes0 replies10 bookmarks846 views

View on X
More posts in the thread (1)
  1. “Avoid ARIA wherever possible. Don’t point a freaking LLM at the APG!” #aria #antipatterns #a11y 1/2

Links and tools from this entry

Summary generated by AI (Gemini 3.8 Flash, 27 September 2026). It may contain errors – the original source is authoritative.

Similar in content, found by the AI search.

  • Link:ibelick

    fixing-accessibility: Agent Skill for Frontend Accessibility Audits

    ibelick has released fixing-accessibility, an agent skill designed to audit and patch HTML and UI accessibility issues. Installed via npx skills, it guides AI coding assistants through ARIA attributes, keyboard navigation, focus management, form validation, and contrast checks using a clear priority hierarchy.

    AI & LLMs· Tool

  • Link:Jeremy Howard

    The /llms.txt Specification v2 for Web-Browsing AI Agents

    Jeremy Howard presents version 2 of the /llms.txt proposal, specifying how websites can provide structured Markdown overviews and direct links so AI agents can navigate content efficiently.

    AI & LLMs· Resource

  • X post:zeldman

    The Future of the Website: From Google-Centricity to an Interface Bundle for Agents

    Jeffrey Zeldman highlights an essay by Joost de Valk analysing the existential shift facing websites. With Google no longer being the only surface worth optimising for, websites must evolve into interface bundles serving both human users and AI agents that complete actions directly.

    68bookmarks9kviews

    AI & LLMs· Opinion

  • Link:Addy Osmani

    Addy Osmani Releases Accessibility Skill for WCAG 2.2

    Addy Osmani has published an accessibility skill and audit guide aligned with WCAG 2.2 standards and Lighthouse audits. Installable via npx, the skill outlines an evidence-based workflow combining automated checks and manual inspection.

    AI & LLMs· Tool

Let's talk about your project

Locations

  • Mattersburg
    Johann Nepomuk Bergerstraße 7/2/14
    7210 Mattersburg, Austria
  • Vienna
    Ungargasse 64-66/3/404
    1030 Wien, Austria

Parts of this content were created with the assistance of AI.