Section 508 and WCAG
Section 508 and WCAG are both accessibility "standards"
- Section 508 is US-only, WCAG is referenced internationally
- WCAG is developed by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C)
- Section 508 was similar to WCAG 1.0 Level A - but the differences caused problems for developers
- WCAG 2.0 is more
- Section 508 refresh is closely aligned with WCAG 2.0
Web Content Accessibility Guidelines (WCAG) 2.0
- Guides authors how to make Web sites accessible
- Not a legal requirement
- Is referenced by legal and organization requirements
- One part of a larger accessibility picture
WCAG Principles
Perceivable - Information and user interface components must be presentable to users in ways they can perceive.
- This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses)
Operable - User interface components and navigation must be operable.
- This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform)
Understandable - Information and the operation of user interface must be understandable.
- This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding)
Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
- This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible)
For more info, see WCAG 2 at a Glance and WCAG Overview
What's New with WCAG 2?
- New accessible Flash techniques have been added to the Techniques document and updates to the Understanding document.
- This is not an endorsement that all Flash content is accessible, it is a resource for developers to make their Flash or Flex content more accessible.
User Agent Accessibility Guidelines (UAAG) 2.0
More accessible browsers and media players (aka "user agents") will improve accessibility for all, without requiring more knowledgeable developers
- think about how hard it is to create accessible tooltips, when it should be done by the browser
- five principles: Perceivable, Operable, Understandable, Meets Standards, and Supports Assistive Technology
- approaching Last Call Working Draft stage
- needs more public comment and input
- For more info: User Agent Accessibility Guidelines (UAAG) Overview
Authoring Tool Accessibility Guidelines (ATAG) 2.0
Why not have tools that create accessible content by default, like: HTML Editors, blogs, wikis, social networking, content management systems (CMS), integrated development environments, etc?
- Authors have disabilities, so authoring tools need to be accessible - especially the editing view
- Authoring tools need to support the production of accessible content
- What's new? ATAG 2.0 went to Last Call Working Draft in July, and the working group is reviewing the comments in preparation for another Last Call Working Draft.
WAI-ARIA
- NOT an accessibility guideline
- NOT an upgrade of WCAG 2.0
- WAI-ARIA is a technical spec like HTML and CSS, that allows developers to code their dynamic web content so it is more accessible.
- Not finalized, but presently open for public comments (Last Call Working Draft) until 29 October. This is the second Last Call for WAI-ARIA that includes all the comments resolved from the previous Last Call.
- Looking for help with setting up testing and evaluation of WAI-ARIA implementations
Other new work from Web Accessibility Initiative
Authors have disabilities, too
ATAG PART A: Make the authoring tool user interface accessible
Develop tools that meet accessibility standards
Principle A.1: Authoring tool user interfaces must follow applicable accessibility guidelines .
- web-based authoring tools, like blogs, wiki's, social networks meet WCAG 2.0
- platform based software follow the appropriate accessibility guidelines.
Perceivable
Principle A.2: Editing-views must be perceivable
- Text appearance is described
- Non text content is identified
- Spellchecking results are detected
- Editing view settings are independent of published appearance
Operable
Principle A.3: Editing-views must be operable
- All functions available from the keyboard
- Discoverable keyboard shortcuts
- No keyboard traps
- Control of timed functions (auto save as, stop animations
- Protection from flashing video or animations
- Powerful search and navigation through content.
Understandable
Principle A.4: Editing-views must be understandable
- Help prevent mistakes
- Undo
- Document features
Produce accessible content
ATAG PART B: Support the production of accessible content
- Produces WCAG 2.0 conforming content
- Provides guidance to authors
- Checks and supports repair of accessibility problems
- Promotes accessible choices
- Documents and demonstrates accessible “best practices”
July 19 Brainstorming Session
Co-hosted by
- White House Office of Science & Technology Policy
- FCC
- Commerce Department
Tech Challenges that could make a difference for accessibility?
- Accessible Apps
- Gallery of Templates and Widgets for Easier Authoring
Authoring Accessible Content Should be Easier
Gallery of Accessible Web Templates & Widgets
Templates
This is a template file you can copy and edit on your own server.
- Accessibility-supporting templates are content patterns that can be filled in by authors or by the authoring tool itself, such as:
- splash page
- order forms
- blog layout
- sign up for newsletter
- display photos
- ... that support production of accessible Web pages
Widgets
Accessibility-supporting widgets are code or scripts for interactive functions such as:
- navigation menus
- embedded media players
- forms
- calendar date picker
- slider
Challenge.gov
A White-House sponsored forum for posting challenges for public contributions
- for gathering submissions
- for public feedback
- also vetting for conformance to WCAG 2.0, ATAG, WAI-ARIA
Accessible Templates Gallery
- A repository for public use
- Provide a resource of accessible templates and widgets for reuse
- organized by type of template & widget
- sourced from government, industry, community
- Showcase the work of people making accessible content
How Can I Contribute?
- Gather templates & widgets to post
- Develop templates & widgets for gaps
- Review submissions for accessibility
- Help spread the word
Resources to Help Build Gallery Submissions
Web Accessibility Initiative Home Page
http://www.w3.org/WAI/
- How to Meet WCAG 2.0
- Authoring Tool Accessibility Guidelines
- WAI-ARIA
- Evaluating Web Accessibility
