Smartstaff, administrator
3,579
edits
Changes
→Beyond Automated Testing
* Test for [[usability]].
* Consider a 3rd party audit.
==Our Design, Development and Testing Methodology==
Our '''design''' methodology uses an inclusive framework like WCAG. The design process starts with empathetic research and analysis, followed by the POUR methodology. We ensure our experiences are Perceivable, Operable, Understandable, and Robust. This allows us to pay special attention when designing for people with a diverse range of sight, hearing, movement, and cognitive ability such as dyslexia, autism, and anxiety. This also includes disabilities that are permanent, temporary, or situational. The design methodology and reviews happen before and after changes are made and includes feedback loops with the community as changes are deployed and amended.
Our '''development''' methodology is similar to the design methodology in that it takes into account similar factors. This includes but is not limited to writing accessible code and following best practices as out lined within WCAG and by W3C. We also use SonarQube to continuously inspect code as well as internal code reviews and automated testing tools.
Our accessibility '''testing''' methodology follows WCAG standards and the standardized baseline testing as prescribed by Section 508 (https://ictbaseline.access-board.gov/introduction/). In addition, we may retain outside auditors and experts to assist in aspects of the quality assurance process. We also use automated testing tools.
=Accessibility - Advanced=