Accessibility

Meticulous supports accessibility regression testing. When a pull request is opened, Meticulous verifies that it does not introduce new accessibility regressions. If it does, the author of the pull request is notified with a comment and a failing CI check. Meticulous reports only new regressions, ignoring pre-existing ones.

Every time Meticulous takes a screenshot of your application, it runs an accessibility check on the rendered web page. It then compares the pre-existing defects with the new ones and reports the freshly introduced regressions. Because Meticulous already has extensive coverage of your application from visual regression testing, it achieves exhaustive accessibility coverage for free: every screen and state your recorded sessions reach is scanned on every run, with no extra tests to write or maintain.

Meticulous checks your application against a curated list of accessibility rules. These include text alternatives for images, accessible names for interactive elements and form fields, ARIA validity and required attributes, and a handful of high-signal document and semantic checks. You can customize this list of rules from your project settings, enabling only a subset of those.

The accessibility check is blocking by default, but it can be configured to never block pull requests. You can change this yourself in the project settings, no Meticulous admin needed.

Reach out to the Meticulous team at support@meticulous.ai and we'll turn it on for your project. The check can optionally be enabled for a subset of users rather than the entire team.