Web Accessibility Initiative
2014 Update
Andrew Arch - @amja

Member, WAI Education & Outreach Working Group

Canberra Web...
Integrated Accessibility Guidelines
WCAG
(web content)
Integrated Accessibility Guidelines
WCAG
(web content)

UAAG
(user agent)
Integrated Accessibility Standards
ATAG
WCAG
(authoring
Diagram of the relationship between
authoring and evaluation tools...
Raise your hand if you’re aware of:
 WCAG 2.0?
 UAAG 2.0?
 ATAG 2.0?
 HTML 5.0?
 CSS 3.0?
 WAI-ARIA?
 Indie UI?
Raise your hand if you’re aware of:
 WCAG 2.0?
 UAAG 2.0?
 ATAG 2.0?
 HTML 5.0?
 CSS 3.0?
 WAI-ARIA?
 Indie UI?
IndieUI
 Independent User
Interface (IndieUI)
• A way for user
actions to be
communicated to
web applications
independent...
2013 activity
What has WAI done this past year?
WCAG 2.0 becomes an ISO Standard
 WCAG 2.0 became ISO/IEC 40500:2012 in
October 2012
 Expected to increase international...
WCAG 2.0 internationalised
 Authorised translations released
• Swedish – October 2012
• Russian – March 2013
• Estonian –...
WCAG 2.0 for non-web ICT
 Working Group Note (WCAG2ICT)
 Guidance on Applying WCAG 2.0
to Non-Web ICT
• September 2013
•...
WCAG 2.0 clarifications
 Techniques for WCAG 2.0
 Understanding WCAG 2.0
• Understanding Techniques for WCAG
Success Cri...
UAAG 2.0
 Implementing UAAG 2.0
• Mobile Accessibility Examples
• Extending browser accessibility to mobile users
• June ...
W3C process
 How WAI Develops Accessibility Guidelines
through the W3C Process
• Working Draft(s)
• Last Call Working Dra...
ATAG 2.0
 ATAG 2.0 & Implementing ATAG 2.0
• Web page authoring tools / HTML editors
• CMSs/LMSs

• Convert/Save to HTML ...
HTML accessibility
 HTML5 Description Extension
(HTML5 longdesc)
• Last Call Working Draft
• September 2013
• Provision f...
WAI-ARIA
 Accessible Rich Internet Applications
 WAI-ARIA Authoring Practices 1.0
• Implementation advice and examples

...
WAI-ARIA continued
 Using WAI-ARIA in HTML
• Working Draft for review – November 2013

 WAI-ARIA User Agent Implementati...
IndieUI
 IndieUI Events (for mobile and more)
• Draft for review – July 2013

Developed with material from W3C Web Access...
Web Accessibility Testing
 Website Accessibility Conformance
Methodology (WCAG-EM)
• Draft for Review – February 2013

• ...
WAI Task forces
 Mobile Accessibility Task Force
• Develop specific mobile guidance related to
WCAG and UAAG

 Cognitive...
Training resources
 Developing Web Accessibility Presentations
and Training: Resources Material
• Updated February 2013
...
Workshops
 Referencing and Applying WCAG 2.0 in
Different Contexts
• May 2013

Developed with material from W3C Web Acces...
R&D Symposiums
 Text Customisation for Readability
• 19 November 2012

 Easy to Read on the Web
• 3 December 2012

 Use...
Keeping up-to-date
 Participation opportunities
• Participate in Working Groups or Task Forces
• Review Guidelines and Do...
WAI activity update presented at Canberra accessibility meetup 2014.02
Upcoming SlideShare
Loading in …5
×

WAI activity update presented at Canberra accessibility meetup 2014.02

704 views

Published on

Outline of W3C WAI accessibility activities and releases during 2013 present at the Canberra Canberra Web Accessibility & Inclusive Design meetup. Feb 2014.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
704
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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
  • Hands source: http://sci-bc.ca/news-and-blog/advocacy-how-to-get-your-voice-heard/http://sci-bc.ca/wp-content/uploads/2013/06/hands-up.jpg
  • Hands source: http://sci-bc.ca/news-and-blog/advocacy-how-to-get-your-voice-heard/http://sci-bc.ca/wp-content/uploads/2013/06/hands-up.jpg
  • Source: https://www.usfca.edu/uploadedImages/Destinations/Offices_and_Services/Business_and_Finance/Purchasing_Services/ISO%20Logo.jpg
  • WAI activity update presented at Canberra accessibility meetup 2014.02

    1. 1. Web Accessibility Initiative 2014 Update Andrew Arch - @amja Member, WAI Education & Outreach Working Group Canberra Web Accessibility & Inclusive Design #cwaid
    2. 2. Integrated Accessibility Guidelines WCAG (web content)
    3. 3. Integrated Accessibility Guidelines WCAG (web content) UAAG (user agent)
    4. 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, UAAG and others. (user agent)
    5. 5. Raise your hand if you’re aware of:  WCAG 2.0?  UAAG 2.0?  ATAG 2.0?  HTML 5.0?  CSS 3.0?  WAI-ARIA?  Indie UI?
    6. 6. Raise your hand if you’re aware of:  WCAG 2.0?  UAAG 2.0?  ATAG 2.0?  HTML 5.0?  CSS 3.0?  WAI-ARIA?  Indie UI?
    7. 7. IndieUI  Independent User Interface (IndieUI) • A way for user actions to be communicated to web applications independently of the device Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
    8. 8. 2013 activity What has WAI done this past year?
    9. 9. WCAG 2.0 becomes an ISO Standard  WCAG 2.0 became ISO/IEC 40500:2012 in October 2012  Expected to increase internationally harmonised uptake of WCAG 2.0
    10. 10. WCAG 2.0 internationalised  Authorised translations released • Swedish – October 2012 • Russian – March 2013 • Estonian – 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. 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. 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. 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. 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. 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. 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. 17. WAI-ARIA  Accessible Rich Internet Applications  WAI-ARIA Authoring Practices 1.0 • Implementation advice and examples • Draft for review – March 2013 • Proposed Recommendation – Feb 2014  WAI-ARIA 1.1 • Working Draft for review – November 2013 Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
    18. 18. WAI-ARIA continued  Using WAI-ARIA in HTML • Working Draft for review – November 2013  WAI-ARIA User Agent Implementation Guide • For developers of web browsers and other user agents • Exposing features to accessibility APIs • Last Call Working Draft – November 2013 • Proposed Recommendation – Feb 2014 Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
    19. 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. 20. Web Accessibility Testing  Website Accessibility Conformance Methodology (WCAG-EM) • Draft for Review – February 2013 • Final working draft for review – February 2014  Easy Checks – A first review of web accessibility • Nine easy things for non-experts to check • Call for review – December 2013 • Nearly final – please give feedback  Developed with material from W3C Web Accessibility Initiative (WAI) www.w3.org/WAI/
    21. 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. 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. 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. 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. 25. Keeping up-to-date  Participation opportunities • Participate in Working Groups or Task Forces • Review Guidelines and Documents • Submit Techniques for Implementing Guidelines • Monitor mailing lists  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/

    ×