You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automated accessibility testing would allow contributors to easily check and update their contributions to match WCAG guidelines.
It would also allow contributors to easily flag areas of the website that may not be completely accessible yet, which were missed through manual testing.
Most appropriate sub-area of p5.js?
Home
Feature request details
I believe there's currently no automated accessibility testing on p5.js-website. The tool I'm most familiar with is Axe-Core, which can be set up to run with an E2E or component testing framework (Cypress, Playwright or Storybook), and test pages or components against specified WCAG standards.
The work I'm proposing for the initial set up Axe-Core for automated testing for eventual continuous adoption on all pages of the website:
Choose an E2E or component testing framework & set this up
Set up Axe-Core to run on one page locally as a proof-of-concept
Get community agreement on the version of WCAG to use, and rules to add or omit
Create a new GHA workflow to run automated Axe-Core tests on new PRs
The text was updated successfully, but these errors were encountered:
Thanks for this idea @clairep94 ! This will have to be discussed a bit more, but anyone who is interested to potentially support this is welcome to add their thoughts below.
It might be useful to find recent accessibility bugs (eg keyboard traps on code snippets: #667) or discussions, and use those to suggest what to prioritize during implementation? I believe there were also some color contrast bugs recently.
Increasing Access
Automated accessibility testing would allow contributors to easily check and update their contributions to match WCAG guidelines.
It would also allow contributors to easily flag areas of the website that may not be completely accessible yet, which were missed through manual testing.
Most appropriate sub-area of p5.js?
Home
Feature request details
I believe there's currently no automated accessibility testing on p5.js-website. The tool I'm most familiar with is Axe-Core, which can be set up to run with an E2E or component testing framework (Cypress, Playwright or Storybook), and test pages or components against specified WCAG standards.
The work I'm proposing for the initial set up Axe-Core for automated testing for eventual continuous adoption on all pages of the website:
The text was updated successfully, but these errors were encountered: