Consider ALL users

Accessibility Audits

Conducting an accessibility audit is an essential part of evaluating the accessibility of your site

  • Our Approach

    We approach accessibility from a standpoint of practicality of implementation. The solutions recommended are assessed in terms of priority and effort of implementation. We have designed our audit to give you worked solutions to any problems found, and a context within which to apply them.

     

    A representative selection of pages from your site is identified and is then subjected to a series of tests:

    Each page is first checked for compliance with the 65 Web Content Accessibility Guidelines (WCAG v2.0 and 2.1, as laid down by the W3C). The testing does not rely on automated checking – each page is evaluated ‘by hand’, as the W3C recommends. Further best practice checks are conducted as appropriate to the client. These might include:

    • Best practice guidelines for accessible PDF documents
    • Best practice guidelines for accessible Macromedia Flash content
    • Best practice guidelines for multi-language (e.g. where information is presented in English, Bengali, Urdu for UK audiences) or bilingual sites
    • UK Government Guidance for public sector websites
    • Assistance with PAS78 requirements
    • Practical and aesthetic performance tests across a range of browsers (e.g. Internet Explorer, Opera, Mozilla) and assistive technologies (e.g. JAWS, HomePage Reader, Lynx)
    • A formal readability test is conducted on the site with results given according to the Flesch Reading Ease scale. Clients may also request a Plain English Review, a service from the Plain English Campaign, and apply for an Internet Crystal Mark.

     

    Read More
  • Outputs

    A report is produced that sets out:

    • A summary of the key issues, with graphs showing the progress made to each of the three levels of accessibility: A, AA and AAA
    • A prioritised list of issues to be addressed that indicate the severity of the issue and an estimate of the resource required to address this
    • For each page reviewed, a detailed description of the accessibility issue, why it isn’t compliant with the WCAG v2.0 and 2.1 checkpoints, illustrated with screenshots where appropriate, with recommendations of how the issue should be addressed and examples of revised coding where appropriate. (NB where issues are generic to a number of pages the issues and their solutions will be identified once and a reference made on each page where this occurs).
    • The Browser testing report would include a set of screen grabs, details of the cross browser issues and recommendations about how these should be addressed

    We also recommend a half day meeting, where we would present the outputs of the audit and discuss how best the changes can be implemented in light of the constraints faced by the client. This helps develop practical solutions to the accessibility issues identified so the client can more easily implement the required changes.

     

  • Additional Service – Template build

    As an additional service, once the evaluations are complete, our designers will take an existing page from the site and rebuild it from the ground up, incorporating all recommendations from the report documents, and commenting the code extensively:

    •  A template visually reproducing the existing page.
    • Fully separating style from content

     

    Tested across a range of browsers, including:

    • Internet Explorer v 8-11
    • Chrome (latest Version)
    • Firefox (latest version)
    • Opera (latest version)
    • Safari for Mac (latest version)
    • JAWS screen reader (various versions)
    • Window Eyes screen reader (various versions)
    • Any others as specified by the client e.g. Mobile phone browsers