Open calebtr-metro opened 2 years ago
This issue is duplicated from https://github.com/emulsify-ds/emulsify-drupal/issues/151. Automated accessibility testing of components more properly belongs in this project because this is where the components are now.
As a developer, I want all components to be automatically covered by accessibility testing.
Compound does no accessibility testing from the command line, but Emulsify-ds does, using a manually curated list.
A solution to generate the list of components using npx sb extract was proposed at https://github.com/emulsify-ds/emulsify-drupal/issues/151 and implemented in https://github.com/emulsify-ds/emulsify-drupal/pull/252.
npx sb extract
In addition, the npm a11y script and a11y.config.js, the related test, the node dependency on the pa11y project will need to be moved to this project. Maybe more stuff, too.
npm a11y
a11y.config.js
pa11y
This issue is duplicated from https://github.com/emulsify-ds/emulsify-drupal/issues/151. Automated accessibility testing of components more properly belongs in this project because this is where the components are now.
Expected Behavior
As a developer, I want all components to be automatically covered by accessibility testing.
Current Behavior
Compound does no accessibility testing from the command line, but Emulsify-ds does, using a manually curated list.
Possible Solution
A solution to generate the list of components using
npx sb extract
was proposed at https://github.com/emulsify-ds/emulsify-drupal/issues/151 and implemented in https://github.com/emulsify-ds/emulsify-drupal/pull/252.In addition, the
npm a11y
script anda11y.config.js
, the related test, the node dependency on thepa11y
project will need to be moved to this project. Maybe more stuff, too.