Thank you for your interest in writing a post! Please fill out the following information:
Your idea
The article talks about how to automate parts of the guidance offered in A11Y Project's checklist (which is a great guide for designers) to help small teams with limited resources still meet accessibility standards. It describes how to do this by customizing accessibility testing tool like, AxeCore, so it includes A11Y Project guidance. It is beneficial for small teams limited on resources/time, who want to advocate for higher accessibility standards, but need to figure out how best to balance manual with automated testing.
Outline (optional)
What AxeCore is, and how it uses impact designations for accessibility
Why improving the impact designations in AxeCore according to A11Y Project guidance will help teams better prioritize accessibility + increase your standards
A list of the AxeCore rules that you can either enable or enhance so they better align with A11Y Project Guidance, and how to work with your developers
Limitations and challenges
Additional information (optional)
I implemented this process on my project, and found it very helpful for improving our accessibility process as a solo designer on a very over-stretched team. I feel many designers / developers may be in similar situations, so this practical scenario may be very helpful for them to apply. They can take the list of rules I found and go ahead and customize AxeCore right away.
Thank you for your interest in writing a post! Please fill out the following information:
Your idea
The article talks about how to automate parts of the guidance offered in A11Y Project's checklist (which is a great guide for designers) to help small teams with limited resources still meet accessibility standards. It describes how to do this by customizing accessibility testing tool like, AxeCore, so it includes A11Y Project guidance. It is beneficial for small teams limited on resources/time, who want to advocate for higher accessibility standards, but need to figure out how best to balance manual with automated testing.
Outline (optional)
What AxeCore is, and how it uses impact designations for accessibility Why improving the impact designations in AxeCore according to A11Y Project guidance will help teams better prioritize accessibility + increase your standards A list of the AxeCore rules that you can either enable or enhance so they better align with A11Y Project Guidance, and how to work with your developers Limitations and challenges
Additional information (optional)
I implemented this process on my project, and found it very helpful for improving our accessibility process as a solo designer on a very over-stretched team. I feel many designers / developers may be in similar situations, so this practical scenario may be very helpful for them to apply. They can take the list of rules I found and go ahead and customize AxeCore right away.
Terms