Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
Promoting Components & ATAG
(Promoting ATAG 2.0 is now in a separate page.)
Nav: EOWG wiki main page
- Doc: Essential Components of Web Accessibility
- presentation: Components Presentation and Step-by-Step Guide
- Conference paper (ACM W4A 2005)
- Components translations (12!)
- Outreach for ATAG 2.0
Audience & Messages
- Users of authoring tools, general public to raise awareness of relation to other standards
- Tool makers and vendors to understand that WAI has resources to guide them
- Procurement staff, buyer to include in purchasing process
- Policy makers to reference ATAG in policy documents
- Developers are not solely responsible for accessibility. Vendors who make authoring software, evaluation tools, browsers and extensions, assistive technologies, and other web related software also have responsibility to follow ATAG, UAAG, and WAI-ARIA to create coherent, systematic support for accessibility.
- Many accessibility problems will be solved when authoring tools follow ATAG
- Browsers and assistive technologies can support accessibility progress by following UUAG
- WCAG applies to web apps, too
- WAI-ARIA helps accessibility keep pace with technology advances
- WAI guidelines cover mobile as well
- As you use particular application, such as new browsers, blogging and content management software,and learning management systems, advocacy from within that community is a powerful way to improve conformance with WAI Guidelines.
- (maybe do use cases to show which guidelines to use in different situations)
- blog posts by EOWG participants and encourage others
- Sharron - about search for accessible LMS and relation to ATAG
- (Wayne on Knowbility Nov 2011)
- video - all guidelines draft script
- newsletter blurbs
- A List Apart under "Build accessibility in, ftw" (ftw = for the win, afaik (afaik = as far as I know :-)) "I learned about accessibility support in video editing tools, and wished for more—it would have saved a lot of time and effort. Several designers and developers I talked to in 2011 are calling for better accessibility support in the tools they use to design the user experience of websites and apps. (See ATAG 2.0)"
Optional to add the hashtags #a11y #w3c_wai to any/all of these...
- Accessibility is not a solo act! WAI Guidelines include techniques for toolmakers, browsers and others http://bit.ly/MlN42U
- Developers don't do it alone, they do it with WCAG AND WAI-ARIA http://bit.ly/MlN42U
- Shopping for a CMS? Ask about ATAG for #accessibility http://www.w3.org/TR/ATAG20/
- Access to technology is a human right says the UN. We all have a part to play http://bit.ly/MlN42U
- Has anybody found a media player that meets the #accessibility requirements of UAAG? http://www.w3.org/TR/UAAG20/
- Designing with Progressive Enhancement? Brush up on components for #accessibility at W3C WAI http://bit.ly/MlN42U
- Schoolkids with disabilities need access! A smart vendor would use ATAG and help teachers include all kids. http://www.w3.org/TR/ATAG20/