Skip to main content

For Designers & Developers

WVU information and communications technology (ICT)—including websites, emails and digital documents—must be ADA compliant through Section 504 of the Rehabilitation Act of 1973 and Title II of the Americans with Disabilities Act. Accessibility is measured through the Web Content Accessibility Guidelines (WCAG 2.0).

Before going live, your web site or app must contain zero WCAG 2.0 A/AA errors.

WCAG 2.0: P.O.U.R

The Web Content Accessibility Guidelines operate on the following tenets:

  • Percievable
  • Operable
  • Understandable
  • Robust

The web has many resources explaining the POUR success criteria. For a quick overview, read WCAG 2.0 at a Glance.

Tools for Accessibility Testing:

You can test your website with the following tools:

  • Siteimprove Chrome Extension
    • To date, we've found this to be the best free accessibility tool to test any single page.
    • It doesn't matter if your page or application requires authentication. This tool checks pages as long as you can view the URL it in your browser.
  • Siteimprove
    • WVU uses Siteimprove (it's SaaS platform) to monitor accessibility compliance, quality assurance, and search engine optimization.
    • University Relations pays for a limited Siteimprove license. If you have questions about Siteimprove or how to get your site added, please contact us.
  • Tenon.io
  • Lighthouse by Google
    • Chrome Developer tools includes Lighthouse by default. To use it, open developer tools (right click on a web page > Inspect Element) and go to the "Audits" tab. Click, "Perform an audit." Be sure to check the Accessibility option.
    • You can also test your site's Performance, Best Practices, and Progressive Web App scores.
    • Lighthouse is also available from the command line or as a Node module.

Tools don't catch everything

Don't forget—automated testing is only part of the accessibility process. Experts estimate tooling can only catch about 40-50% of accessibility issues. In addition to running automated accessibility checkers, you'll want to do manual accessibility testing.

For example, you could perform some manual testing with a screen reader or double check alternate text on images (since they are often written incorrectly).

Develop with accessible patterns

When creating web sites or applications, choose your technology wisely. Using appropriate color contrast, semantic HTML5 markup and accessible front-end components go a long way to ensure your site or application will be accessible.

What to do before submitting a site or web application for approval

As stated above, before release to the public, all WVU web properties must have zero WCAG 2.0 A/AA errors. Follow these steps to check accessibility prior to approval:

  • Use Siteimprove to check for errors.
    • If your site is in Siteimprove ( SaaS), log in and resolve any accessibility errors.
    • If your site is not in Siteimprove, check your site with Siteimprove Chrome Extension and Tenon or one of the other tools above.
    • Different tools catch different errors. Always use two or more.
  • Follows all of our Golden Rules for Content Creators.
  • Avoids Common Accessibility Pitfalls.
  • Manually check your site using a screen reader.
  • Check alternate text.
  • Check that you’re using HTML elements for what they are designed for.
    • This includes making sure every section of your page is wrapped by an HTML5 tag (like <header>, <main>, <aside>, etc).
  • Use a keyboard to navigate your site, making sure keyboard focus is apparent.
  • Validate any linked PDF documents for accessibility.

Accessibility monitoring for live sites and apps

Siteimprove is our primary accessibility compliance monitoring tool. Siteimprove scans sites weekly for accessibility, quality assurance, and search engine optimization. To help users stay on top of errors, Siteimprove emails users a weekly site report.

Oftentimes, sites in production have errors from new content, updated templates, or content authors with little knowledge of accessibility. Do your best to fix these errors and maintain a high accessibility score in Siteimprove. Keep in mind, sites in production are the ones people are using. They are simultaneously our biggest asset and our biggest liability.

If you make changes to a site, use the Siteimprove Chrome Extension to test changes against accessibility guidelines—making sure no errors exist.

Resources