Accessibility,
engineered.
A workshop of browser modules, AI integrations, CLI testing, and screen-reader tooling — each repo solving one piece of the accessibility workflow, held together by a consistent method.
One engine, one workflow.
The engine is the home: the tool developers run on every pull request. Around it, grouped by where each sits in an accessibility engineer's day — from scanning a page, to drafting a ticket, to shipping the fix with regression coverage.
Tools
05 reposUmbrella repo — audit panel and UX widget. The page you're reading now.
CLI for screen-reader-driven testing — scan, live SR, audit, and test generation (Virtual Screen Reader + Playwright).
Turns screenshots and recordings into WCAG-compliant accessibility tickets.
Shows what a screen reader says next to each part of the page, for designers, product managers and training.
Drop in an image, get alt text: for content editors.
AI & agents
02 reposEducation
01 repoArchived, superseded by the engine, which now holds their useful parts: accessibility-engine, a11y-agent, a11y-expert-mcp and wcag-alt-generator. The inventory has every repo's fate and why.
The five-step pattern behind every repo.
Investigate a component against WAI-ARIA Authoring Practices, screen-reader behaviour, and WCAG criteria before proposing a contract.
Document the accessible contract — roles, states, keyboard interaction, focus management, announcement expectations.
Layered testing — axe, Vitest with Testing Library, Playwright, plus manual screen-reader verification.
Every violation gets a WCAG criterion, reproduction steps, expected vs. actual, and acceptance criteria — before it reaches a developer.
Ship the fix with tests that lock in the accessible behaviour, so the regression is caught automatically next time.
Why the portfolio is shaped this way.
Accessibility knowledge is scattered.
Patterns, heuristics, test recipes, and ticket templates live across people's heads, wikis, and ad-hoc scripts. AI tools don't consistently apply them.
One engine, shared patterns.
One engine runs every check on each pull request, and the same ARIA patterns explain every finding, so people and AI tools apply the same guidance.
One home, a few companions.
The engine holds the checks, AI suggestions and fixes, so they are built and tested once. Separate products and the shared patterns stay in their own repos; an earlier attempt is archived only when a kept product already does its job.
Two browser tools, one click away.
Preview each tool on this page, drag it into your bookmarks bar for permanent use, or copy the bookmarklet code to paste into a new bookmark manually.
A11y Audit Panel
Visual accessibility auditor — headings, landmarks, alt text, labels, hidden content, tab order, contrast, focus, ARIA, and form checks.
Bookmarklet source (manual paste)
A11y UX Widget
Live accessibility customization — contrast, color vision filters, dyslexia font, font size, focus, motion, spacing, reading guide, and big cursor.