1 / 51

Making Your Web Site Accessible: AODA Compliance Joanne Oud , Session 415

Making Your Web Site Accessible: AODA Compliance Joanne Oud , Session 415. Overview. Background Legislation & Standards Common Errors How to Conform. A. Background. Ontarians with Disabilities . 15%. Disabilities Affecting Web Use. Common Assistive Technologies.

keita
Download Presentation

Making Your Web Site Accessible: AODA Compliance Joanne Oud , Session 415

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Making Your Web Site Accessible: AODA ComplianceJoanne Oud, Session 415

  2. Overview • Background • Legislation & Standards • Common Errors • How to Conform

  3. A. Background

  4. Ontarians with Disabilities 15%

  5. Disabilities Affecting Web Use

  6. Common Assistive Technologies

  7. B. Legislation & standards

  8. Ontario Standards • AODA: how-to • Principles: • Dignity • Independence • Removing barriers

  9. New Legislation on Web Sites • Integrated Standard • Information and Communication section • June 2011

  10. Comply with WCAG 2.0

  11. What It Applies To “to websites and web content, including web-based applications, that an organization controls directly or through a contractual relationship that allows for modification of the product”

  12. WHAT IS WCAG 2.0?

  13. Good News • Major international standard • Very specific • Lots of guidance • Relatively easy to check

  14. Bad News • Very specific • Relatively easy to check • Not used in U.S. • Most tools, advice doesn’t apply

  15. WCAG 2.0: Four Major Principles • Perceivable • Operable • Understandable • Robust

  16. Each Principle Has Guidelines 2. Operable 2.1 Accessible by keyboard 2.2 Allow time to read and use content 2.3 Avoid content known to cause seizures 2.4 Help users find content

  17. Each Guideline Has Subsections

  18. Each Subsection Has Techniques

  19. Techniques: Example #2

  20. Each Technique Is Described

  21. C. Common Errors

  22. Research Project • Question: • How well do Ontario library web sites currently conform with WCAG 2.0? • Study population: • 64 library web sites (university, college, public) • Method: • Automated testing using Total Validator & Contrast Checker

  23. Results: All Libraries 15 errors per page (average) 6 6 3

  24. Error 1: Invalid Markup • Markup doesn’t match doctype • Html/xhtml/css errors • Code not valid, well-formed

  25. Error 2: Poor Contrast

  26. Error 3: Absolute Units <table> <tr> <td width="974px"> <div style="padding: 0px; border: solid 0 #cccccc; border-bottom-width: 1px;"> <table cellpadding="0" cellspacing="0"> <tr>

  27. Error 4: Missing alt text

  28. Describe Function in Alt Text

  29. Error 5: Incorrect Alt Text

  30. Use Null Alt Text if Decorative “”

  31. Error 6: Using HTML For Formatting

  32. Error 7: Bad Heading Structure Correct order: h1>h2>h3>h4

  33. Error 7: Link Text Not Unique

  34. Title Attribute <a title=“more about finding books” href=“/books.html”> More…</a> • Use when needed to give more information • Don’t use if repetitive/redundant

  35. Error 8: Link Text Not Descriptive

  36. Error 9: Form Control Problems • Associate labels with form controls <label for="firstname">First name:</label> <input type="text" name="firstname" id="firstname" /> • Form controls need title attribute if no label • Proper reading order if using tab key • Need submit button for search boxes

  37. Error 10: Tables • Make sense if read linearly • Have captions or summaries <table summary=“Opening hours for main and branch libraries during fall term”> <caption>Opening Hours</caption> • Column & row headings <tr> <th scope=“row”>Opening Hours</th> <td>9am</td>

  38. Error 11: Embedding <embed src="/sites/all/swf/topic.swf"> <noembed>Please use the links on this page to access alternate versions.</noembed> </embed>

  39. Many Things Not Checked For • Consistency • Skip navigation • Keyboard accessibility • Timing • New windows/popups • Flash or moving content • Accessible document formats • Accessible version of non-accessible content

  40. D. How to conform

  41. WCAG 2.0 Conformance • Required: • Meet all sufficient techniques/success criteria • Levels A, AA • Optional (but recommended): • Meet advisory techniques

  42. Getting There

  43. Test Existing Site

  44. Automated Testing Tools • For html/css: • W3C validators • For WCAG 2.0: • Total Validator (whole site) • TAW 3 (page by page) • Contrast Checker (page by page)

  45. Sample Report: WCAG Errors

  46. Expert Testing Methods • Checklist • Enlarge using browser • Navigate using keyboard • Emulate assistive technology

  47. Fangs Screen Reader Emulator Fangs Screen Reader Emulator

  48. Web Anywhere webanywhere.cs.washington.edu/wa.php

  49. User Testing • Usability test • Common tasks • Different content • Different assistive technologies

  50. Plan & Implement Changes • Site template > 80% of errors • Non-template page content: • Identify most common issues • Educate content creators • Monitor: • Validation • Checking

More Related