Home

Even Grounds, Accessibility Consulting

Making web sites, documents, software and hardware accessible to people with disabilities. Accessibility, WCAG and Section 508 compliance testing and auditing.

  • Books
  • Articles
  • Blog
  • Developers' Corner
  • Resources

Are You Receiving the Accessibility Tips and Tricks?

  • Learn to make information accessible to people with disabilities
  • Implement what you learn right away
  • Understand how people with disabilities use technology
  • Receive our monthly newsletter packed with news, articles and updates
  • Bonus workbook: Ten steps to a more accessible web site


Do you need help with accessibility? Hire us!

Accessibility for Ontarians with Disabilities Act: Making the Web More Accessible

  • articles
  • accessibility
  • AODA
  • Canada
  • Ontario
  • WCAG

While the exact date is not decided, based on the Accessibility for Ontarians with Disabilities Act (AODA), it is expected that in the near future web sites will have to be made accessible.

In this article, we will take a look at the Accessibility for Ontarians with Disabilities Act, 2005, and the significance of web standards such as the WCAG 2.0 to this legislation.

What is the Accessibility for Ontarians with Disabilities Act (AODA)

The Accessibility for Ontarians with Disabilities Act, 2005, or AODA, is a law that focuses on the development of accessibility standards for all Ontarians. The government of Ontario is responsible for developing and implementing these standards.

The accessibility standards will be mandatory and will be designed to identify, remove, and prevent barriers for people with disabilities. Both private and public sectors within Ontario are required to adhere to these standards.

On January 1, 2010, the public sector is expected to have met the first stage of compliance. This stage consists of new customer service standards. Private businesses, non-profit organizations, and other service providers have to complete this stage by 2012.

The AODA became law on June 13, 2005. It derived most of its principles from the Ontarians with Disabilities Act, 2001.

Purpose of the Accessibility for Ontarians with Disabilities Act

The following text discusses the purpose of the AODA. This was taken from e-laws.gov.on.ca.

Recognizing the history of discrimination against persons with disabilities in Ontario, the purpose of this Act is to benefit all Ontarians by,

(a) developing, implementing and enforcing accessibility standards in order to achieve accessibility for Ontarians with disabilities with respect to goods, services, facilities, accommodation, employment, buildings, structures and premises on or before January 1, 2025; and

(b) providing for the involvement of persons with disabilities, of the Government of Ontario and of representatives of industries and of various sectors of the economy in the development of the accessibility standards. 2005, c. 11, s. 1.

Key Areas of the AODA

The AODA focuses on the following Key Areas:

  • Accessible Customer Service
  • Accessible Information and Communications
  • Transportation
  • Accessible Built Environment
  • Employment Accessibility

AODA and web accessibility

As stated above, a key area of AODA is accessible information and communications. This includes the World Wide Web. AODA, therefore, aims to ensure the accessibility of all public and privately owned websites developed by individuals and groups in Ontario.

In order for websites to meet this AODA standard, the government of Ontario will require web developers to follow the Web Content Accessibility Guidelines (WCAG) 2.0.

WCAG 2.0 refers to a set of internationally recognized guidelines and methods used by web developers to make their sites accessible for persons with disabilities. This document describes in detail the things you need to do, as well as the things you should avoid, to make your site accessible. Basically, you need to refer to WCAG 2.0 while developing and adding content to your website.

At first glance, you may find the WCAG 2.0 quite lengthy and hard to follow. However, you only need to focus on the requirements for web content which your site contains, and the whole documentation is really not as complicated as it seems. By doing so, you eliminate many of the apparently intimidating aspects of WCAG 2.0. In addition, the efforts you make to meet the WCAG 2.0 requirements would greatly benefit all visitors of your website.

To further help you realize that the WCAG 2.0 is truly not complex, we have prepared a free WCAG 2.0 tutorial (opens in new window). Through this tutorial, we aim to help website owners in better understanding and following WCAG 2.0.

Useful AODA Resources

Below are links to pages containing useful information regarding the AODA:

  • Full Text of the AODA
  • A Guide to the AODA

AODA TESTING

Submitted by gina (not verified) on Thu, 08/04/2011 - 22:33.

IS THERE ANYONE WHO CAN GIVE US SOME TIPS ON HOW WE CAN FURTHER IMPROVE OUR WEBSITE AND COMPLY WITH AODA STANDARDS ESPECIALLY JAWS AND ZOOM READER

  • reply

Re: AODA TESTING

Submitted by Tom on Sun, 08/14/2011 - 12:44.

Sure, we can help you. I will contact you privately.

  • reply

Re: Accessibility for Ontarians with Disabilities Act: ...

Submitted by Bren (not verified) on Mon, 09/17/2012 - 10:58.

Honestly, some of this stuff is pretty un realistic. If you thought cross browser testing was a pain, try adding this list of regulations on top of it. I think the only way to have a "designed" site, and a site which is AODA compliant is to have two sites. One which looks great and functions as normal, and one which is basically text on a white background.

Although I feel people with disabilities should be able to access the web in an easy manner, a site should be made AODA compliant if the site owner so chooses. It should not be required.

  • reply

Re: Accessibility for Ontarians with Disabilities Act: ...

Submitted by Tom on Tue, 09/25/2012 - 15:54.

Text on white only works if the page does not have any functionality. However, the problem in reality with text-only pages is that they are often forgotten to be updated.
Also, I believe that a site can be both accessible, user friendly and attractive.

  • reply

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

This blog uses CommentLuv plugin which will try and parse your sites feed and display a link to your last post, please be patient while it tries to find it for you
CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Accessibility Tips and Tricks


RSS

  • Articles
  • Blog
  • Developers' Corner
  • News
  • Press

Follow us on Twitter, YouTube, or on Facebook

You Might Also Like:

  • Is Accessibility Overwhelming?
  • Section 508 Update Enters Public Comment Phase
  • Web accessibility a pressing issue in Ontario
  • Accessibility standard now in effect for public sector
  • Greater accessibility promised  

If you like it, share it!




 

Privacy Policy

Copyright 2007-2013 - Even Grounds Inc., Accessibility Consulting