Click here to load reader

Introduction to WCAG, ATAG and UAAG

  • View

  • Download

Embed Size (px)


Introduction to WCAG, ATAG and UAAG. Jan Richards, Project Manager Inclusive Design Research Centre OCAD University W3C-WAI Model. Web Content Accessibility Guidelines (WCAG) 2.0 Recommendation: Guidelines for making Web content more accessible. - PowerPoint PPT Presentation

Text of Introduction to WCAG, ATAG and UAAG

Taking Accessibility to the Clouds

Introduction to WCAG, ATAG and UAAGJan Richards, Project ManagerInclusive Design Research CentreOCAD University

http://idrc.ocad.ca1W3C-WAI ModelWeb Content Accessibility Guidelines (WCAG) 2.0 Recommendation:Guidelines for making Web content more accessible.Authoring Tools Accessibility Guidelines (ATAG) 2.0 Working Draft (1.0 is Rec): Guidelines for: (1) making authoring tools more accessible to authors and (2) supporting the production of accessible content by all authors.User Agent Accessibility Guidelines (UAAG) 2.0 Working Draft (1.0 is Rec): Guidelines for making user agents (browsers, media players) more accessible to end users.

2WCAG 2.0Version 2.0 is a Full Recommendation.Applies to:Various web content technologies (HTML, SVG, PDF, etc.) Static pagesWeb applicationsEtc.Notes:Only Accessibility-Supported Ways of Using TechnologiesFull Pages/Compete Processes

WCAG 2.0: Perceivable1.1 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:Control or accepts user input: Describe its purpose. Time-Based Media: Provide descriptive identification. Test or exercise: Provide descriptive identification. Sensory experience: Provide descriptive identification. CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart): Note purpose and provide alternative forms of CAPTCHA in another mode (sound).Decoration, Formatting, Invisible: Help assistive technology ignore it (i.e. alt=).

WCAG 2.0: Perceivable1.2 Provide alternatives for time-based media.:AudioCaptions (Prerecorded)Captions (Live)Sign language translationVideo:Audio DescriptionsExtended Audio DescriptionsInteraction:Text alternatives including interaction

WCAG 2.0: Perceivable1.3 Create content that can be presented in different ways (for example simpler layout) without losing information or structure.Labels for form controlsTable headingsRoles, states, etc. (WAI-ARIA)

WCAG 2.0: Perceivable1.4 Make it easier for users to see and hear content including separating foreground from background:Sufficient contrastResizabilityAbility to control audioLow or no background audioNo one appreciates this.and this isnt nice either.

WCAG 2.0: Operable2.1 Make all functionality available from a keyboard:No keyboard traps.2.2 Provide users enough time to read and use content.2.3 Do not design content in a way that is known to cause seizures.2.4 Provide ways to help users navigate, find content, and determine where they are.Provide structure to help the user navigate (headers, bypass links, tab order, etc.).

WCAG 2.0: Understandable3.1 Make text content readable and understandable.3.2 Make Web pages appear and operate in predictable ways.Dont shift the users context just because they move the focus or change the setting of a control.

Keep navigation and control labelling consistent.3.3 Help users avoid and correct mistakes.

WCAG 2.0: Robust4.1 Maximize compatibility with current and future user agents, including assistive technologies.Web content must be compatible with a wide range of user agents:Being parsablePassing along semantic information such as name, role and values (e.g. WAI-ARIA information)

ATAG 2.0Version 1.0 was published in 1999.Version 2.0 is nearing completion.Applies to:WYSIWYG editors, plain text editors conversion tools (e.g., "Save as HTML")blogging tools, wikis, online forums, email clientsmultimedia authoringCMS systems,Etc.

ATAG 2.0: Definition of Authoring ToolAny web-based or non-web-based application(s) that can be used by authors (alone or collaboratively) to create or modify web content for use by other people (other authors or end users).Note 1: "application(s)": ATAG 2.0 may be conformed to by stand-alone applications or by collections of applications. If a conformance claim is made, then the claim must provide identifying information for each application and also for any required extensions, plug-ins, etc.Note 2: "alone or collaboratively": Multiple authors may contribute to the creation of web content and, depending on the authoring tool, each author may work with different views of the content and different author permissions.Note 3: "to create or modify web content": This clause rules out software that collects data from a person for other purposes (e.g., online grocery order form) and then creates web content from that data (e.g., a web-based warehouse order) without informing the person (however, WCAG 2.0 would still apply). This clause also rules out software used to create content exclusively in non-web content technologies.Note 4: "for use by other people": This clause rules out the many web applications that allow people to modify web content that only they themselves experience (e.g., web-based email display settings) or that only provide input to automated processes (e.g., library catalog search page). ATAG 2.0: Supports WCAG 2.0ATAG 2.0 uses the Web Content Accessibility Guidelines (WCAG) as the determinant of Web content accessibility.ATAG 2.0 has special checkpoints related to checking, repair, etc. of content that take their level directly from WCAG.ATAG 2.0: Accessible Authoring UIPart A: Make the authoring tool user interface accessiblePrinciple A.1. Authoring tool user interfaces must follow applicable accessibility guidelinesA.1.1. (For the authoring tool user interface) Ensure that web-based functionality is accessibleA.1.2. (For the authoring tool user interface) Ensure that non-web-based functionality is accessiblePrinciple A.2. Editing-views must be perceivableA.2.1. (For the authoring tool user interface) Make alternative content available to authorsA.2.2. (For the authoring tool user interface) Editing-view presentation can be programmatically determinedATAG 2.0: Accessible Authoring UIPrinciple A.3. Editing-views must be operableA.3.1. (For the authoring tool user interface) Provide keyboard access to authoring featuresA.3.2. (For the authoring tool user interface) Provide authors with enough timeA.3.3. (For the authoring tool user interface) Help authors avoid flashing that could cause seizuresA.3.4. (For the authoring tool user interface) Enhance navigation and editing via content structureA.3.5. (For the authoring tool user interface) Provide text search of the contentA.3.6. (For the authoring tool user interface) Manage preference settingsA.3.7. (For the authoring tool user interface) Ensure that previews are as accessible as existing user agentsPrinciple A.4. Editing-views must be understandableA.4.1. (For the authoring tool user interface) Help authors avoid and correct mistakesA.4.2. (For the authoring tool user interface) Document the user interface including all accessibility featuresATAG 2.0: Accessible content productionWe shouldnt rely on the average author to implement WCAG on their own becauseaccessibility requirements can be complex to manage (e.g. keeping navigation consistent),most authors are not (nor do they wish to be) accessibility experts (and WCAG is a technical document, on par with a format recommendation),the delivery of Web content is becoming more complex,and tools are being produced that hide many of the low-level details of the final content.

16ASSUME the author has the necessary knowledge, the tool allows sufficient author access, and the format is appropriate (e.g. simple HTML; but not dynamically generated HTML, complicated SVG, SMIL, etc.)

ATAG 2.0: Accessible content productionPart B: Support the production of accessible contentPrinciple B.1: Fully automatic processes must produce accessible contentB.1.1. Ensure automatically specified content is accessibleB.1.2. Ensure accessibility information is preservedPrinciple B.2: Authors must be supported in producing accessible contentB.2.1. Ensure accessible content production is possibleB.2.2. Guide authors to produce accessible contentB.2.3. Assist authors with managing alternative content for non-text contentB.2.4. Assist authors with accessible templatesB.2.5. Assist authors with accessible pre-authored contentPrinciple B.3: Authors must be supported in improving the accessibility of existing contentB.3.1. Assist authors in checking for accessibility problemsB.3.2. Assist authors in repairing accessibility problemsPrinciple B.4. Authoring tools must promoted and integrate their accessibility featuresB.4.1. Ensure the availability of features that support the production of accessible contentB.4.2. Ensure that documentation promotes the production of accessible content17ASSUME the author has the necessary knowledge, the tool allows sufficient author access, and the format is appropriate (e.g. simple HTML; but not dynamically generated HTML, complicated SVG, SMIL, etc.)

ATAG 2.0: Automating AccessibilityAuthoring tools need to support accessibility in the same way as they support correct syntax and spelling:

ATAG 2.0: Automating AccessibilityIn case people think developers arent paying attention (from the iPhone Accessibility Programming Guide).

UAAG 2.0Version 1.0 was published in 2002.Version 2.0 is in progress.Appliers to:BrowsersMedia playersWeb-based user agents

UAAG 2.0: Supports WCAGUAAG 2.0 supports WCAG 2.0 but because it gives guidance to user agents rendering any Web content, it cannot assume WCAG requirements have been followed.UAAG 2.0: PrinciplesPRINCIPLE 1: PerceivableGuideline 1.1: Alternative contentGuideline 1.2: Missing contentGuideline 1.3: HighlightingGuideline 1.4: Text configurationGuideline 1.5: Volume configurationGuideline 1.6: Synthesized speech configurationGuideline 1.7: Style sheets configurationGuideline 1.8: ViewportsGuideline 1.9: FocusGuideline 1.10: Source viewsGuideline 1.11: Element InformationUAAG 2.0: PrinciplesPRINCIPLE 2. OperableGuideline 2.1: Keyboard accessGuideli

Search related