Lesson 11Post-design steps: how to implement and monitor your accessible design?
Notion 81
Create a checklist and document solutions that work
Target skills
The design team could work with a checklist for accessibility that would be improved over time. They would benefit from a feedback loop each time a review with new issues is transmitted.
Iterative design
An iterative design is a moving, self-improving and adapting design phase. The idea is to improve the design over the version. New elements added to the checklist will make it more useful over time, and improve the designers’ skills.
Find more efficient design processes
By its constraining nature, a checklist will favour some processes that are more efficient. Some elements will be reused between designs and can become part of a greater system design that is accessible. The creation of a system design will save time by ensuring its elements are compliant.
Checklist length
Your checklist can be as long as the WCAG criteria, or focused on the most common problems. Better start small and add your own criteria over time. You can have a look at checklist examples to start building your own.
Checklist examples
- The United States government created an accessibility checklist of 20 elements based on their importance: https://accessibility.18f.gov/checklist/
- Mozilla published a checklist with Mobile usage in mind: https://developer.mozilla.org/en-US/docs/Web/Accessibility/Mobile_accessibility_checklist
- Opquast, a training organisation, has a checklist of 240 elements that can be filtered by topics and keywords, and even depending on the project phases you are in: https://checklists.opquast.com/en/web-quality-assurance/