A template & resources for creating good accessibility templates for your website & apps.
-
Updated
Mar 11, 2022
A template & resources for creating good accessibility templates for your website & apps.
Accessibility testing that maps WCAG failures to EN 301 549 and national law across 17 jurisdictions: CLI + CI reporting, accessible React components, and a machine-readable regulatory database.
Generate an accessibility statement from real audit results. Untested criteria say "Not Evaluated" instead of being assumed to pass.
WCAG 2.2 accessibility audits for Craft CMS 5: scan every page, fix what fails, and keep the record, statement and VPAT to show for it.
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.
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.
Generate an honest English/French accessibility statement from an a11y-audit report (never claims more than was tested), and diff two audits to show progress.
Toetst je WordPress-site op de machinaal toetsbare punten van EN 301 549 en schrijft een toegankelijkheidsverklaring die klopt met de meting. Geen overlay. Gratis GPL-plugin van theseo.nl.
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
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
Builds the German accessibility statement from the operator's settings and runs three pattern checks on stored page content. WordPress plugin · GPLv2+ · AS IS, zero support.
Generate the EU accessibility statement the European Accessibility Act requires, from your axe results. Deterministic, offline, contributor-driven jurisdiction packs.
To associate your repository with the accessibility-statement topic, visit your repo's landing page and select "manage topics."