ARIA, Anti-Patterns, and Common Misunderstandings of the APG

ArticleDavid BushellOpinion

David Bushell warns against treating the ARIA Authoring Practices Guide (APG) as a best-practice manual or feeding it to LLM agents. Native HTML should always take precedence over ARIA.

Key points

  1. The ARIA Authoring Practices Guide (APG) exists to showcase theoretical ARIA capabilities and help vendors test support, not to define best practices for production websites.
  2. The first rule of ARIA requires using native HTML elements like <button> whenever possible instead of custom elements with ARIA roles like <div role="button">.
  3. Prompting LLM agents to convert APG specifications directly into component markup leads to fragile, over-engineered code.
  4. Findings from the WebAIM Million report indicate that heavier ARIA usage is correlated with a higher number of detected accessibility errors.

Why it matters

Front-end developers often misapply ARIA attributes to emulate accessibility rather than relying on native semantic elements. Automating component generation from APG examples via AI agents compounds these issues and degrades real-world accessibility.

Analysis

Bushell highlights a dangerous disconnect in modern front-end workflows: treating theoretical specification demonstrations as production-ready patterns. The APG deliberately uses ARIA-heavy constructs for specification testing. Relying on LLMs to translate these into component libraries bypasses foundational accessibility rules. The WebAIM Million data cited confirms that overuse of ARIA directly corresponds to increased accessibility defects.

Found in

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.

  • X post:zeldman

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

    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.

    10bookmarks846views

    AI & LLMs· Opinion

  • 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: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

  • Article:Tejas Kumar

    What Is an Agent Harness? Harness Engineering Explained

    Tejas Kumar explains the concept of an agent harness: the runtime layer around a model that enforces reliable execution in real environments. Using a practical browser automation example, he demonstrates how deterministic code around GPT-3.5 Turbo fixes agent failures without altering the prompt.

    AI & LLMs· Tutorial

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.