Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Implementing WCAG by Making Your Website Accessible for Everyone

Implementing WCAG by Making Your Website Accessible for Everyone

Presented at TRY 2013. Full write up: http://cynng.wordpress.com/2013/05/07/making-your-website-accessible-for-everyone/
--
The deadline in Ontario to make our websites accessible is next January. While we have a set of guidelines to follow, it’s not always clear how to best implement the Web Consortium Accessibility Guidelines (WCAG) in a practical manner. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. To make a website accessible, you will also need material that your content creators understand. Come learn how to make a website more accessible for everyone.

This presentation will focus on HTML and CSS, but will touch on custom interfaces.

Cynthia "Arty" Ng

May 07, 2013
Tweet

More Decks by Cynthia "Arty" Ng

Other Decks in Technology

Transcript

  1. What is WCAG? Web Consortium Accessibility Guidelines 2.0 by the

    Web Accessibility Initiative (WAI) group, W3C Cynthia Ng @TheRealArty 6
  2. AODA Deadline Accessibility for Ontarians with Disabilities Act (AODA) under

    Section 14, subsection 4 • By January 1, 2014, new internet websites and web content on [public sector] sites must conform with WCAG 2.0 Level A. • By January 1, 2021, all internet websites and web content must conform with WCAG 2.0 Level AA, other than, o success criteria 1.2.4 Captions (Live), and o success criteria 1.2.5 Audio Descriptions (Pre-recorded). Cynthia Ng @TheRealArty 7
  3. Template Consistent navigation (3.2.3) & identification (3.2.4) Multiple Methods of

    Discovery (2.4.5) Meaningful Order (1.3.2, 2.4.3) Use CSS for presentation (1.3.1) Cynthia Ng @TheRealArty 11
  4. <!DOCTYPE html> <html lang="en"> <head> <title>Your Page Title</title> </head> <body>

    <header> <a href=“#menu” class=“skiplink”>Skip to Main Menu</a> <h1>site name</h1> <h2>tagline</h2> <nav id=“menu”> <a href=“#content” class=“skiplink”>Skip to Content</a> <a href=“...”>Global Nav Link</a> <a href=“...”>Second Nav Link</a> <a href=“...”>Yet Another Nav Link</a> </nav> </header> <div id="content”> <article> <!-- your content, a blog post for example --> </article> <article> <!-- another standalone piece --> </article> </div> <div id="secondary”> <!-- typically your sidebar --> </div> <footer > copyright and other info </footer> </body> </html> Cynthia Ng @TheRealArty 18
  5. <!DOCTYPE html> <html lang="en"> <head> <title>Your Page Title</title> </head> <body>

    <header role="banner"> <a href=“#menu” class=“skiplink”>Skip to Main Menu</a> <h1>site name</h1> <h2>tagline</h2> <nav id=“menu” role="navigation"> <a href=“#content” class=“skiplink”>Skip to Content</a> <a href=“...”>Global Nav Link</a> <a href=“...”>Second Nav Link</a> <a href=“...”>Yet Another Nav Link</a> </nav> </header> <div id="content" role="main"> <article role="article"> <!-- your content, a blog post for example --> </article> <article role="article"> <!-- another standalone piece --> </article> </div> <div id="secondary" role="complementary"> <!-- typically your sidebar --> </div> <footer role="contentinfo"> copyright and other info </footer> </body> </html> Cynthia Ng @TheRealArty 21
  6. Headers <h1>TRY Conference</h1> <h2>Presentations</h2> <h3>Making the Website Accessible</h3> <h2>Registration</h2> Cynthia

    Ng @TheRealArty 27 Page Title: TRY Conference Topic: Presentations Subtopic: Making the Website Accessible Topic: Registration
  7. Audio/Video Etc. Autoplay Control (2.2.2) Audio – 3 second rule

    (1.4.2) Flash – 3 in 1 second rule (2.3.1) On a Timer (2.2.1) Cynthia Ng @TheRealArty 39
  8. Assessing Web Accessibility WCAG Quick Reference HTML Codesniffer W3C Web

    Accessibility Tools list - WAVE & Fangs Cynthia Ng @TheRealArty 46