Freedom251 › Accessibility Testing Software
Sa11y
What Sa11y is
Sa11y is a free, open-source collection of automated accessibility testing libraries based on axe-core. It supports Jest and Vitest unit tests, WebdriverIO component and integration tests, browser integrations, and custom test runners. Jest and Vitest provide a toBeAccessible() matcher, while WebdriverIO offers synchronous and asynchronous assertAccessible APIs for rendered browser pages. A framework-agnostic matcher exposes programmatic testing APIs. Base, Extended, and Full axe rule presets are available, with Base used by default in the matchers and assert APIs. The formatter combines axe findings, filters exception lists, and adds WCAG metadata. A minified browser bundle supports Selenium Java and WebdriverIO patterns. Packages install through npm or yarn, and CI/CD integration is supported. Checks require a rendered DOM rather than static HTML. In JSDOM, color-contrast and audio/video checks are disabled or unavailable; WebdriverIO documentation also cautions that color-contrast checks do not work in headless mode.
Who it suits
Sa11y suits teams adding automated accessibility checks from unit tests through browser integration tests. It can test any axe-core-supported interface, not only Salesforce products.
What it does well
- Free open-source packages
- Jest and Vitest matchers included
- WebdriverIO browser assertions
- Base, Extended, and Full rule presets
- WCAG metadata in reports
What to know first
- Checks require a rendered DOM
- JSDOM limits visual and media checks
- Headless WebdriverIO skips color-contrast checks
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Sa11y | Open-source accessibility testing libraries · packages installable from npm | Free |
As opensource.salesforce.com lists them, read 12 Oct 2026. The maker's own page has the final word.
Verdict
Sa11y offers integrations across unit, component, integration, and browser testing workflows. Teams should account for rendered-DOM requirements and browser-mode limitations when planning coverage.
Facts from Sa11y's own pages
- Browser integrations
- A minified bundle can be injected into a browser for integration testing and supports Selenium Java and WebdriverIO patterns. · opensource.salesforce.com, 5 Oct 2026
- Browser testing
- The WebdriverIO package checks browser-rendered pages with `assertAccessible()` or `assertAccessibleSync()`. · opensource.salesforce.com, 12 Oct 2026
- Custom runners
- The framework-agnostic matcher package exposes programmatic accessibility checks for custom test runners and integrations. · opensource.salesforce.com, 12 Oct 2026
- Distribution
- The project documents installation of its packages using npm or Yarn. · opensource.salesforce.com, 12 Oct 2026
- DOM requirement
- Accessibility checks require a rendered DOM, and template elements cannot be checked directly unless rendered. · opensource.salesforce.com, 12 Oct 2026
- Frameworks
- The project provides integrations for Jest unit tests, Vitest unit tests, and WebdriverIO component and integration tests. · opensource.salesforce.com, 5 Oct 2026
- Intended audience
- The project describes its libraries as tools for teams adding automated accessibility testing from unit tests through integration tests. · opensource.salesforce.com, 5 Oct 2026
- Jest
- The Jest package provides a `toBeAccessible()` matcher and can run accessibility checks automatically at the end of each test. · opensource.salesforce.com, 12 Oct 2026
- Jest matcher
- The Jest package provides a toBeAccessible() matcher and can run accessibility checks automatically after each test. · opensource.salesforce.com, 5 Oct 2026
- JSDOM limits
- The Jest documentation says color-contrast and audio/video checks are disabled or unavailable in JSDOM and recommends a real browser for checks requiring visual rendering. · opensource.salesforce.com, 5 Oct 2026
- Maker headquarters
- Salesforce identifies San Francisco as its home and headquarters. · careers.salesforce.com, 12 Oct 2026
- Not Salesforce-specific
- The libraries can test any user interface supported by axe-core and are designed to be flexible, customizable, and reusable across testing workflows. · opensource.salesforce.com, 5 Oct 2026
- Other integrations
- A browser bundle supports Selenium Java and WebdriverIO integration patterns. · opensource.salesforce.com, 12 Oct 2026
- Purpose
- Sa11y is a collection of automated accessibility testing libraries and tools based on axe-core. · opensource.salesforce.com, 12 Oct 2026
- Rendered DOM required
- The Jest documentation says checks run against a rendered DOM and cannot be run on static HTML markup. · opensource.salesforce.com, 5 Oct 2026
- Reporting
- The results formatter can filter exceptions and add WCAG metadata to accessibility results. · opensource.salesforce.com, 12 Oct 2026
- Rule presets
- Sa11y provides Base, Extended, and Full axe rule presets, with Base used by default in the Jest and Vitest matchers and assert APIs. · opensource.salesforce.com, 5 Oct 2026
- Rule sets
- Sa11y provides base, extended, and full axe rule sets; base is the default, while extended includes WCAG AAA, experimental, and non-WCAG best-practice rules. · opensource.salesforce.com, 12 Oct 2026
- Supported users
- The libraries can test any user interface supported by axe-core and are not specific to Salesforce. · opensource.salesforce.com, 12 Oct 2026
- Testing caveat
- The WebdriverIO documentation cautions that color-contrast checks do not work in headless mode and recommends windowed mode when possible. · opensource.salesforce.com, 12 Oct 2026
- Vitest
- The Vitest package provides a `toBeAccessible()` matcher and supports automatic checks and custom results processing. · opensource.salesforce.com, 12 Oct 2026
- Vitest matcher
- The Vitest package provides a toBeAccessible() matcher for checking HTML elements or the DOM in unit tests. · opensource.salesforce.com, 5 Oct 2026
Where Sa11y stands on Freedom251
- Accessibility Testing Software#67 of 169