A suite of accessibility tests that integrate axe-core into the Ember.js testing framework.
ember-a11y-testing is an Ember addon that wraps the axe-core accessibility testing engine, enabling developers to run automated accessibility audits within their Ember test suite. It helps ensure web applications are accessible by detecting common violations during development and testing.
Ember developers who need to integrate automated accessibility testing into their existing test workflows, particularly those building web applications that must comply with accessibility standards.
Developers choose this addon because it seamlessly integrates axe-core into Ember's testing ecosystem, providing a native test helper and global hooks that fit into standard Ember testing patterns without disrupting development workflows.
A suite of accessibility tests that can be run within the Ember testing framework
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides native test helpers like `a11yAudit` and `setupGlobalA11yHooks` that integrate directly into Ember's QUnit and Testem environments, as shown in the setup examples for application, integration, and unit tests.
Supports extensive customization of axe-core audits through `setRunOptions` and `setConfigureOptions`, allowing rule adjustments, locale settings, and targeted component checks, with documentation linking to axe-core APIs.
Enables conditional auditing via query parameters (`enableA11yAudit`) and programmatic control with `setEnableA11yAudit`, making it easy to run audits only in pipeline environments without modifying test code.
Offers both console logging via `setupConsoleLogger` for immediate feedback and middleware-based JSON reporting for persistent violation analysis, enhancing debugging and compliance tracking.
The addon has removed components for live accessibility checking during development, directing users to external tools like Accessibility Insights, which may fragment the workflow and require additional setup.
Advanced features like custom invocation strategies and middleware setup require a deep understanding of both Ember testing and axe-core options, increasing the learning curve for new users.
The middleware reporter generates accumulating JSON files without automatic cleanup, as noted in the README warning, necessitating manual intervention to prevent storage issues over time.