Jeanne Spellman W3C Web Accessibility Initiative (WAI) W3C/WAI Standards for Creating and Displaying Accessible Web Content eAccessibility Forum

W3C Web Accessibility Initiative (WAI) Components of Web Accessibility  Content  Browsers, media players (user agents)  Assistive Technology  Users  Developers & Authors  Authoring Tools  Evaluation Tools

W3C Web Accessibility Initiative (WAI)

WCAG 2.0 Web Content Accessibility Guidelines

W3C Web Accessibility Initiative (WAI) UAAG User Agent Accessibility Guidelines

W3C Web Accessibility Initiative (WAI) ATAG Authoring Tool Accessibility Guidelines

W3C Web Accessibility Initiative (WAI) Authors have disabilities  S oftware must follow accessibility guidelines  E diting view must be perceivable  E diting view must be operable  E diting view must be understandable

W3C Web Accessibility Initiative (WAI) Perceivable  T ext appearance is described  N on text content is identified  S pellchecking results are detected  E diting view settings are independent of published appearance

W3C Web Accessibility Initiative (WAI) Operable  A ll functions available from the keyboard  D iscoverable keyboard shortcuts  N o keyboard traps  C ontrol of timed functions (auto save as, stop animations  P rotection from flashing video or animations  P owerful search and navigation through content.

W3C Web Accessibility Initiative (WAI) Understandable  H elp prevent mistakes  U ndo  D ocument features

W3C Web Accessibility Initiative (WAI) Produce Accessible Content  P roduces WCAG 2.0 conforming content  P rovides guidance to authors  C hecks and supports repair of accessibility problems  P romotes accessible choices  D ocuments and demonstrates accessible “best practices”

W3C Web Accessibility Initiative (WAI) ATAG 2.0 improvements  C hoosing base technology  A ccessible templates  G uidance to authors  A ccessibility Checking and Repair functions

W3C Web Accessibility Initiative (WAI) Implementing ATAG 2.0 Plain language explanation Intent Examples Resources

W3C Web Accessibility Initiative (WAI) ATAG 2.0 Status Last Call Working Draft soon Implementations needed

W3C Web Accessibility Initiative (WAI) What can I do?  L et developers know about ATAG for internal authoring tools (CMS, blogs, etc)  L et developers know about UAAG for embedded video players  T alk to Purchasing Department to write WCAG, ATAG and UAAG compliance into contracts

W3C Web Accessibility Initiative (WAI) What can I do? ATAG  I mplement ATAG in your organization  R eview, evaluate or translate ATAG  W rite conformance claims on the tools you use

W3C Web Accessibility Initiative (WAI) What can I do? UAAG  P articipate in the Working Group  R eview and comment on working drafts  C omment on the latest draft

W3C Web Accessibility Initiative (WAI) What can I do? WCAG  D ocument new techniques – especially for: PDF Flash Silverlight SMIL SVG Xforms  R eview new techniques

W3C Web Accessibility Initiative (WAI) For more information…  W AI w3.org/WAI/w3.org/WAI/ WCAG Overview ATAG Overview UAAG Overview  A TAG 2.0 Guidelines w3.org/TR/ATAG20/ w3.org/TR/ATAG20/  I mplementing ATAG 2.0 w3.org/TR/implementing-ATAG20/ w3.org/TR/implementing-ATAG20/