Ken Bengtsson


Auditing and Remediation

Once the Policy and Standards were in place the next step was to identify the auditing process, prioritize the websites, perform the audits, and develop a remediation plan for each.


A two prong approach is necessary to find accessibility violations:

1. Automated tools – which will catch about half of the violations and,
2. Manual testing – which is necessary to catch violations such as:
a. Inconsistent navigation.
b. Illogical tab order.
c. Site not working for screen readers.
d. Keyboard traps.
e. Links not making sense out of context.
f. That dynamic screen context works with accessibility tools.

Automated Tools

We chose to use the aXe DevTools extension on FireFox. It’s free yet gives highly detailed analysis of violations and how to remedy them.

A screenshot of the aXe dev tool extension.

The aXe dev tool extension in FireFox in action.

To mimic screen reader output we chose to use the Fangs Screen Reader Emulator extension on FireFox. This free tool displays the written output as one of the most popular screen readers on Windows would read it – the Jaws Screen Reader. Written output is easier to show to developers to help them understand issues than having them listen to a screen reader, which they may not be able to understand. (Note that the Fang extension appears to no longer be supported.)

Screenshot of the Fang extension in Firefox.

The Fang extension in Firefox displaying text as a screen reader would read it.