Find out what is causing your website's WCAG 2.0 issues discovered by the detailed automated WCAG 2.0 scan and how you can fix them
The WCAG 2.0 AA Remediation Report is an automated analysis that not only identifies WCAG 2.0 A/AA issues, but also provides you with detailed recommendation as to how to fix them. Your public-facing website will be scanned and tested using the following WCAG 2.0 principals:
- Principle 1: Perceivable Information and user interface components must be presented to users in ways they can perceive. This means that users must be able to comprehend the information being depicted.
- Principle 2: Operable User interface components and navigation must be operable. The interface cannot require interaction that a user cannot perform.
- Principle 3: Understandable Users must be able to understand the information as well as the operation of the user interface.
- Principle 4: Robust Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. As technologies and user agents evolve, the content should remain accessible.
Specific issues discovered under each of the guidelines are detailed with an explanation as to why it's considered noncompliant and includes suggestions for techniques as to how to fix them. To help your team easily find each infraction within the website, we include the links to the exact URL on which it was found as well as provide snippets of the code in question and screenshots of the issue when applicable.
Developers Guide Remediation Report
The Developer's Guide Remediation Report includes an analysis of your website summarized into the following logical groupings:
- Media: Ensure that all Media items such as animations/video and audio have an alternative means of understanding the content. Test results include: Text Equivalency; Image Mapping & Media Plugins
- Structure: Ensure that your HTML layout structuring is necessary and informative. Test results include: Table Layout; Frame Layout; Animation Flicker; Skip Content; Descriptive Content and Adjustable Text.
- Text: Text should be readable, understandable and appropriately marked up. Test results include: Descriptive Content and Appropriate Text.
- Cascading Style Sheets (CSS): Pages that use one or more of the listed external style sheets should be checked to make sure they’re still readable and well organized without the stylesheet(s). Test results include: Usable Without Styles, Adjustable Text, Keyboard Accessible and No Blink.
- Form: Forms must be usable and properly labeled and identified with tag and attribute based relationships. Testing results includes Usable Forms.
In addition to the PDF Report, BoIA delivers a pipe delimited file of the data that can be imported directly into a bug tracking system, like JIRA or Trello. This has proven to be a great time-saver, allowing your team to spend their valuable time and resources on fixing the issues, not having to create each IT ticket.
Ready to get started?
Our accessibility professionals will answer your questions and help you determine next steps.