A Trump team wants to automate U.S. Web Design System accessibility testing

Human accessibility testing is important too.

Re: the new WebMCP spec: https://news.ycombinator.com/item?id=45623194 :

> Could this help with accessibility reviews?

> "Lighthouse accessibility score" https://developer.chrome.com/docs/lighthouse/accessibility/s...

> awesome-a11y > Tools: https://github.com/brunopulis/awesome-a11y/blob/main/topics/...

I've been working with Playwright e2e tests (End to End) in a number of projects lately.

Playwright is a useful and justified abstraction in the testing workflow because: Playwright tests can be run interactively in vscode (with just bwrap sandboxing but unfortunately no VM isolation), Playwright tests can be run in a dedicated local browser or in a headless browser for example in a container on GitHub Actions (a CI Continuous Integration system that runs then tests and saves the output artifacts automatically when any change is pushed to the source code repo), Playwright test can be recorded from an interactive browser session, and Playwright tests can be written by AI prompted to implement 100% branch test coverage with tests and e2e tests with {Playwright or Puppeteer} in {language}.

And then there's the Computer Use model (and the need for process or full VM sandboxing e.g. with ai-sandbox)

Find existing open source agent instructions and agent skills for UI/UX agents that could or should be adapted to a11y testing?

More websites would be more accessible if you can throw good automation at it. AI seems particularly well-suited to evaluate various dimensions of accessibility of a website.

Awesome initiative! I really like axe-core for automated accessibility testing.

Its great for pre-production and live product testing alike!