1 / 24

Preparing judgments that can be listened to Frédéric Pelletier fred@lexum

Preparing judgments that can be listened to Frédéric Pelletier fred@lexum.com. Web accessibility. Web accessibility. WCAG. 1999 - Web Accessibility Initiative ( W3C ) 2008 - WCAG 2.0 4 principles

keefe-brady
Download Presentation

Preparing judgments that can be listened to Frédéric Pelletier fred@lexum

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. Preparing judgments that can be listened toFrédéric Pelletierfred@lexum.com

  2. Web accessibility

  3. Web accessibility

  4. WCAG • 1999 - Web Accessibility Initiative (W3C) • 2008 - WCAG 2.0 • 4 principles • 12 guidelines, each of which having numerous “success criteria” at three levels: A, AA, AAA

  5. WCAG Main Checkpoints • 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

  6. WCAG Main Checkpoints • 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.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 • 3.1 Readable: Make text content readable and understandable • 3.2 Predictable: Make Web pages appear and operate in predictable ways

  7. 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.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 • 3.1 Readable • Make text content readable and understandable • 3.2 Predictable • Make Web pages appear and operate in predictable ways

  8. Create structured content • Separate information from presentation

  9. WCAG 2.0 Implementation

  10. Preparation Conversion

  11. Drafting • Judges are not to be asked to take web accessibility into consideration when drafting their reasons

  12. Formatting • Spacing and alignments are defined through paragraph parameters • The document is exempt of empty paragraphs or multiple consecutive tab and space characters • Structural elements are explicitly defined through the proper functionality of the word-processing application • Headings • Lists • Quotations • Tables

  13. Metadata and markup • Information conveyed by images or other graphical objects is also available textually • Data tables include explicit • Caption • Table header and data cells • Header, footer and body groups of rows • Summary (if not available textually) • Emphasized or other special text is explicitly defined using semantic markup • The primary language of the document is explicitly defined, as well as words and phrases that are not in the document’s primary language

  14. Authoring tools features

  15. Workarounds

  16. Preparation Conversion

  17. Conversion • MS-Word’s raw HTML • Upside: provides very granular markup • Downside: markup is not WCAG compliant • WCAG HTML • Lexum’s conversion software makes use of Word’s HTML markup to produce WCAG 2.0 compliant HTML decisions

  18. Conclusion • Judgments’ web accessibility • Challenges • Diversity of authors and inherent complexity • Authoring tools not fully WCAG-compliant • Expected benefits • More structured and re-usable information

More Related