equal-access
Metrics as of , from the GitHub or GitLab API of each repository. Refreshed monthly.
What equal-access is
equal-access is the repository for the automated accessibility testing tools of the IBM Equal Access Toolkit. Browser extensions for Chrome, Firefox and Edge add accessibility checking to each browser's developer tools. The extensions visualize issues and help locate their source. The Node package accessibility-checker runs automated accessibility tests in continuous integration pipelines. It works with Selenium, Puppeteer and Playwright, compares results against baseline files and scans local files. A separate package wraps accessibility-checker for Cypress. A shared rules and evaluation engine underlies the tools. A rule server deploys the rules and engine. The Toolkit places these tools in its Verify phase.
Written from the project's README, read .
- Category
- Accessibility testing
- License
- Apache-2.0
- Language
- JavaScript
- Changelog
- Releases on GitHub
Repository metrics
Status
activeLast commit within 90 days of the fetch date.Computed from the last commit date and the archive flag on the fetch date. See the status rules.
Alternatives
Listed accessibility testing tools, same primary language first, then by GitHub stars. Each line gives one fact from the tool's documentation where it differs from equal-access's, with its source.
Lighthouse: Rules or standards: Accessibility audits, weighted by axe user impact assessments. source: Docs: Lighthouse accessibility score
Lighthouse CI: Rules or standards: Lighthouse regression checks for accessibility, SEO, offline support and performance. source: README
Pa11y: Rules or standards: WCAG2A, WCAG2AA (default), WCAG2AAA (HTML_CodeSniffer runner only). source: README
axe-core-npm: Rules or standards: axe-core rules selected by tag, such as wcag2a (CLI --tags). source: Docs: @axe-core/cli
Pa11y CI: Browsers: Chrome (executable path set in defaults.chromeLaunchConfig.executablePath). source: README
axe-core: Rules or standards: WCAG 2.0, 2.1 and 2.2 at levels A, AA and AAA; additional rules outside WCAG. source: README
Accessibility Insights for Web: Rules or standards: WCAG 2.2 Level AA success criteria (Assessment). source: Docs: Assessment
cypress-axe: Rules or standards: axe-core rules; README example filters by tag wcag2a. source: README
Questions
Is equal-access open source?
Yes. equal-access is released under Apache-2.0, an OSI-approved license, as reported by the GitHub API on 2026-09-22.
Is equal-access maintained?
On 2026-09-22, the last commit to the default branch was on 2026-09-08, so the listed status is active. Rule: Last commit within 90 days of the fetch date.
How many GitHub stars does equal-access have?
778 stars on 2026-09-22, from the GitHub API. The number is refreshed at each monthly update.
What language is equal-access written in?
The repository's primary language, as reported by the GitHub API, is JavaScript.
Sources
- GitHub REST API: repository, read
- GitHub REST API: commits, read
- GitHub REST API: latest release, read
- GitHub REST API: contributors, read
- README, read