1. Web Accessibility Initiative
2013 Update
Andrew Arch
@amja
Australian Government Information Management Office
Member, WAI Education & Outreach Working Group
4. Integrated Accessibility Standards
ATAG
WCAG
(authoring
Diagram of the relationship between
authoring and evaluation tools, Web (web content)
tools)
content, and user agent tools such as
browsers and assistive technologies. As
each component adheres to common
standards, accessibility and
interoperability are improved. At the
W3c, groups of experts work in
collaboration on the
ATAG – authoring tools accessibility group;
WCAG – web content accessibility group; and
UAAG – user agent accessibility
group, and others. UAAG
(user agent)
10. WCAG 2.0 internationalised
Authorised translations released
• Swedish – October 2012
• Russian – March 2013
• Estonian (last call) – October 2013
WCAG 2.0 Translations has a list of other
completed and planned translations
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
11. WCAG 2.0 for non-web ICT
Working Group Note (WCAG2ICT)
Guidance on Applying WCAG 2.0
to Non-Web ICT
• September 2013
• Informative only
• Guidance on the interpretation and application of
WCAG 2.0 to non-web documents and software
• Collaborative effort to support harmonised
accessibility solutions
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
12. WCAG 2.0 clarifications
Techniques for WCAG 2.0
Understanding WCAG 2.0
• Understanding Techniques for WCAG
Success Criteria
• September 2013
• Reinforcing that W3C’s techniques are
informative and are not intended to be
required
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
13. UAAG 2.0
Implementing UAAG 2.0
• Mobile Accessibility Examples
• Extending browser accessibility to mobile users
• June 2013
UAAG Last Call Working Draft - For Review
• November 2013 - Comments by 16 December
• Anyone interested in
• Browsers
• Media players
• Assistive technologies
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
14. W3C process
How WAI Develops Accessibility Guidelines
through the W3C Process
• Working Draft(s)
• Last Call Working Draft
• Candidate Recommendation
• Proposed Recommendation
• W3C Recommendation (Web Standard)
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
15. ATAG 2.0
ATAG 2.0 & Implementing ATAG 2.0
• Web page authoring tools / HTML editors
• CMSs/LMSs
• Convert/Save to HTML tools
• Multimedia authoring tools
• Blogs, Wikis, Social media, etc
Implementation testing – Candidate
Recommendation
• November 2013
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
16. HTML accessibility
HTML5 Description Extension
(HTML5 longdesc)
• Last Call Working Draft
• September 2013
• Provision for adding longer text description to
complex images in HTML5
Role Attribute 1.0
• W3C Recommendation – March 2013
• XML attribute – semantic info in documents
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
17. WAI-ARIA
Accessible Rich Internet Applications
WAI-ARIA Authoring Practices 1.0
• Implementation advice and examples
• Draft for review – March 2013
WAI-ARIA 1.1
• Working Draft for review – November 2013
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
18. WAI-ARIA continued
Using WAI-ARIA in HTML
• Working Draft for review – November 2013
WAI-ARIA User Agent Implementation Guide
• Exposing features to accessibility APIs
• Last Call Working Draft – November 2013
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
19. IndieUI
IndieUI Events (for mobile and more)
• Draft for review – July 2013
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
20. Web Accessibility Testing
Website Accessibility Conformance
Methodology (WCAG-EM)
• Draft for Review – February 2013
Easy Checks – A first review of web
accessibility
• Nine easy things for non-experts to check
• Call for review – June 2013
• Nearly final – please give feedback
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
21. WAI Task forces
Mobile Accessibility Task Force
• Develop specific mobile guidance related to
WCAG and UAAG
Cognitive Accessibility Task Force
• Develop specific guidance related to cognitive
and learning disabilities
Participants called for
• See Participating in WAI
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
22. Training resources
Developing Web Accessibility Presentations
and Training: Resources Material
• Updated February 2013
Tutorials for developers
• In preparation
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
23. Workshops
Referencing and Applying WCAG 2.0 in
Different Contexts
• May 2013
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
24. R&D Symposiums
Text Customisation for Readability
• 19 November 2012
Easy to Read on the Web
• 3 December 2012
User Modelling for Accessibility
• 15 July 2013
Accessible e-Learning
• 16 December 2013
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
25. Keeping up-to-date
WAI Interest Group
• A public group with a mailing list for
general discussion on Web accessibility
• WAI-IG mailing list archives
Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
Hinweis der Redaktion
Web developers should understand that they do not need to meet the requirements all alone. People from all over the world have been working collaboratively within the W3C (World Wide Web Consortium) for decades to make sure that all components work together and operate from common principles and API’s. This slide demonstrates that developers can use tools to create and test web sites. Many of those tools conform to W3C Authoring Tool (ATAG) Guidelines. Meanwhile, related Guidelines are developed for common web programming languages and issued as Web Content Accessibility Guidelines (WCAG). To bring those programs to the user, guidelines are in place for browsers and assistive technology devices and are called User Agent Accessibility Guidelines (UAAG). Working together, these practices ensure harmony among the many hardware and software devices involved in creating the Web as we know it.The Guidelines have been developed through a consensual process to work together:Web Content Accessibility Guidelines (WCAG)Others are responsible too:Authoring Tool Accessibility Guidelines (ATAG) are rules for companies that create software like Dreamweaver and FrontPage.User Agent Accessibility Guidelines (UAAG) are rules for people who create user agents, like browsers (for example, Firefox and Internet explorer) and assistive technology, like screenreaders.
ARIA = Accessible Rich Internet ApplicationsWAI-ARIA Overview:http://www.w3.org/WAI/intro/ariaIndieUI = Independent User InterfaceIndieUI Overview:http://www.w3.org/WAI/intro/indieui