Accessibility testing enables developers to understand whether developed software can be easily used by the differently abled people. Once errors are found in the developed software, the developer has to understand the same and fix it. Effective accessibility recommendations are provided on how to fix identified issues. These are pointers which aid a developer or engineer in his work.
There are times when recommendations and remediation are used synonymously. But both do not mean the same. Recommendations are pointers for reference while remediation refers to the act of fixing an issue or reversing a change. Thus these are unique identifier code snippets on which ARIA attributes, roles, codes etc., are all applied.
Categories of bugs found in accessibility testing
The categories of bugs or errors that are found during accessibility testing can be divided into 4 different types following the POUR principles i.e. bugs which:
- Hinder user Perceivability,
- Affect the Operability of functionalities,
- Adversely affect content Understandability and
- Affect content Robustness.
Some examples of common bugs from each of the above categories include:
- On-focus bugs affect Understandability,
- Colour-contract bugs affect Perceivability,
- Name, role and value bugs affect Robustness,
- Content not meaningfully structured or sequenced affect Perceivability,
- Wrong heading hierarchy affects Operability,
- Disassociated labels affect Operability,
- Elements not keyboard accessible affect Operability etc.
With the new WCAG 2.1 guidelines coming in, finding bugs and fixing them might require certain new recommendations. These guidelines are extremely important and developers and engineers have to incorporate the same and make their software compliant with its terms and conditions. Acceptability of the developed software depends on the same.
Some bugs that enhance accessibility issues and their corresponding WCAG2.1 guidelines for recommendations and remediations are:
- Accessible name not the same as visible label text: In such instances, it is recommended that the element label be changed to match the visual label. Remediation codes need to be adapted accordingly.
- Input purpose unclear: Herein inspecting the element would reveal that the type attribute is generally not correct. It is recommended that the appropriate type attribute be used for the input field so that input purpose can be programmatically determined. Remediation changes in the relevant code needs to be done accordingly.
There are other bugs that have also been defined in the new WCAG2.1 guidelines. For all of these bugs, recommendations and remediation tactics that have been applied need to be as per the guidelines. This will enable engineers to give effective accessibility recommendations based on the new guidelines so that remediation codes can be written accordingly.
Watch the video below to understand everything in more detail.