This is the "Meet Level A" page of the "Accessibility Guidelines for Websites" guide.
Alternate Page for Screenreader Users
Skip to Page Navigation
Skip to Page Content

Accessibility Guidelines for Websites  

To meet the Accessibility for Ontarians with Disabilities Act, we must meet the Level A standard for Web Content Accessibility Guidelines (WCAG) 2.0 by January 2014. Get the Core Resources to meet the Level A standard here.
Last Updated: Mar 8, 2016 URL: Print Guide RSS Updates

Meet Level A Print Page

Table of Contents

This guide provides core resources only so you can assess your websites for compliance to Level A standards for WCAG 2.0.

Tools to Assess Compliance

  • WAVE website
    Web-based version of WAVE, a tool to check for accessibility issues on your website. Good for any browser: just enter the URL of the site you want to test.
  • WAVE Toolbar
    Get the Firefox extension that checks for accessibility issues.
  • Fangs Screen Reader Emulator
    Get the Firefox extension that generates text similar to the output of screen readers. It allows a sighted user to better understand the experience that a screen reader user would have.
    Use it by right-clicking on the page.

Accessibility: Waterloo LibGuides for Guide Authors

  • Usability & Content
    Tab within Waterloo LibGuides for Guide Authors.
    Get information on creating good & accessible websites.


Contact Web Operational Management Group with questions related to this site & its content.

Contact Liam Morland with questions about creating accessible web content.

Level A Guidelines for WCAG 2.0

  • 1.1 Text Alternatives
    Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
  • 1.2 Time-based Media
    Provide alternatives for time-based media.
  • 1.3 Adaptable
    Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
  • 1.4 Distinguishable
    Make it easier for users to see and hear content including separating foreground from background.
  • 2.1 Keyboard Accessible
    Make all functionality available from a keyboard.
  • 2.2 Enough Time
    Provide users enough time to read and use content.
  • 2.3 Seizures
    Do not design content in a way that is known to cause seizures.
  • 2.4 Navigable
    Provide ways to help users navigate, find content, and determine where they are.
  • 3.1 Readable
    Make text content readable and understandable.
  • 3.2 Predictable
    Make Web pages appear and operate in predictable ways.
  • 3.3 Input Assistance
    Help users avoid and correct mistakes.
  • 4.1 Compatible
    Maximize compatibility with current and future user agents, including assistive technologies.

Loading  Loading...