Skip to content
#

accessibility-statement

Here are 12 public repositories matching this topic...

For web agencies and freelancers who look after many small-business websites: every client site's accessibility status on one screen, a dated log of problems found and fixed, a draft accessibility statement per site and a monthly report under your own name. Runs in the browser. Built with Claude Code.

  • Updated Nov 17, 2026
  • TypeScript

EAA-2025-ready accessibility compliance platform — 21 npm packages: 31-rule WCAG 2.2 AA scanner pack, TypeScript scanner runtime (engine + browser + Playwright), reusable GitHub Actions workflow, EN 301 549 statement generator, 11-jurisdiction penalty estimator, VPAT 2.5 INT evidence emitter.

  • Updated Nov 18, 2026
  • HTML

Versioned accessibility statements: the conformance target and status claimed against WCAG 2.0, 2.1 or 2.2, unmet criteria with their reason, alternative and fix date, the alternatives offered, the feedback contact, the enforcement procedure and the last evaluation, as plain data, and the next version generated from phil/accessibility-check reports

  • Updated Nov 12, 2026
  • PHP

The accessibility statement of a Symfony application: versioned, from configuration or a table, at /accessibility and /accessibilite in English and French with the wording of WCAG, EN 301 549 or the Accessible Canada Act, drawn with the PHIL UX kit, a footer link, an admin page that publishes, and a command fed by phil/accessibility-check

  • Updated Nov 16, 2026
  • PHP

Add this topic to your repo

To associate your repository with the accessibility-statement topic, visit your repo's landing page and select "manage topics."

Learn more