Skip to content

Summary of recommendations and improvements of accessibility 16

For the optimization of CASUS for screen readers, required for a project, we used the tool “WAVE” available at The website also includes other useful resources for optimizing own websites/web applications. The WAVE tools are entirely online, so no installation is needed.

While the tool “WAVE” is very easy to use for static websites, using it for a dynamic webapp required some tricks which we would like to share in this section.

Once you go to the only available interface element is a input field for a URL which you have to fill with the page you would like to analyze and press return. fetches the typed in page and will give you the results:

Image: Start screen of check application alt text sample result screen

The summary contains number of “errors”, “alerts”, “features, “structural elements”, “html5 and ARIA” and “contrast errors”

Errors: Critical structural issues, which prevent screen readers from being able to read the content in a meaningful way, examples: missing labels for input fields. to get more than the summary you can go to the “details” section in the left menu, for each issue you can even get more explanations and hints how to fix these with “i” icon next to the issue category.

Alerts: even though not critical for reading the page, improvements would help the screen readers to process the page better, examples are broken headline structures, not meaningful links names like “read more” without more context.

Features: same as alerts but even less critical, like alternative texts of images

Structural Elements: scan for headlines, lists, etc. which help screen readers

HTML5 and ARIA: checks whether additional context tags like