Skip to navigation
Build and Run Tests

Accessibility Checks

View as Markdown

Automated accessibility checks are unavailable.

Accessibility findings complement functional assertions. Start with the pages and interactions in a critical Web journey, then record the standard, severity expectations, and owner for follow-up.

An accessibility finding does not automatically mean the functional journey failed. Teams should review accessibility findings separately unless the Test contains a specific accessibility assertion.