Accessibility checks on AI-built websites

We gave Codex CLI and Claude Code the same everyday website briefs without accessibility instructions. Then we scanned the pages they built.

Results

A run is one coding tool with one model. Open a run to see all its sites.

AIMAC Debt counts critical and serious axe-core violations only. Lower is better. The ranking covers the 28 categories that every run completed and captured.

Runs ranked by AIMAC Debt
RankRunAIMAC Debt (median)Sites scoredViolationsHTML elements
1Codex CLI GPT-6.2-Astra0.02803130
2Codex CLI GPT-6.2-Sol0.02842957
3Antigravity CLI GPT-OSS 120B0.028651166
4Codex CLI GPT-6-Luna5.7283174256
5Claude Code Opus 5.57.32857212247
6Antigravity CLI Gemini 3.8 Flash8.0284407705

Method

Each run used the same six website briefs. Codex used its default model. Claude Code ran once with its default, Opus 5.5, and once with Fable 5.2 selected at launch. We sent the opening instructions through the /goal command in Codex and as a regular message in Claude Code. All six sites from each run passed validation. We opened the saved pages in Chromium with external requests blocked and ran axe-core once per page with its default rules.

Capture tools and settings
ToolVersion or setting
axe-core4.14.1
@axe-core/playwright4.14.0
playwright1.65.1
chromium159.0.8154.6
nodev26.7.0
Injected axe-core script (SHA-256)29348999450cdf2849a8e70b7912fc2da85a849da39c0d0d5394f51d4a9ed95c
Viewport1280 by 1024 pixels
Locale, timezone, color schemeen-US, UTC, light

Limits

  • Each run used a separate Linux container on a Mac mini. Room checks confirmed that the host home folders, tested local network services and other rooms were inaccessible, while public internet access worked. Full clean-room qualification is pending. The containers came without a web browser, so Codex downloaded Chromium to test its pages. In Claude Code, Opus 5.5 used jsdom to simulate a browser, and Fable 5.2 reviewed the code without rendering the pages.
  • Each model ran once. We did not measure how much the results vary between runs.
  • A failed capture leaves the result unknown. The table displays a separate status for failures.
  • Axe-core scanned the page as it first loaded at one desktop size, with no clicks, scrolling or other interaction. The totals exclude color contrast checks that axe-core could not decide and left for manual review. A full accessibility assessment or a judgment of conformance with the Web Content Accessibility Guidelines (WCAG) would require further testing.
  • The briefs required pages to load without external resources, which can change what a model builds. The demo reports violations for individual sites without a combined score or rankings.