Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Web Accessibility Initiative
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Guidelines and technical reports== ===Web Content Accessibility Guidelines (WCAG)=== {{further|Web Content Accessibility Guidelines}} The Web Content Accessibility Guidelines 1.0 (known as WCAG) were published as a W3C Recommendation on 5 May 1999. A supporting document, Techniques for Web Content Accessibility Guidelines 1.0<ref>{{cite web|url=http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/ |title=Techniques for Web Content Accessibility Guidelines 1.0 β W3C Note 6 November 2000 |publisher=W3.org |access-date=28 July 2013}}</ref> was published as a W3C Note on 6 November 2000. WCAG 1.0 is a set of guidelines for making web content more accessible to persons with disabilities. They also help make web content more usable for other devices, including mobile devices (PDAs and cell phones). The Web Content Accessibility Guidelines 1.0 are recognized as a de facto standard and have served as a basis for legislation and evaluation methodologies in many countries. The WCAG working group published WCAG 2.0 as a Recommendation on 11 December 2008. WCAG 2.0 is based on very different requirements from WCAG 1.0: * the guidelines needed to be technology-neutral, whereas WCAG 1.0 was strongly based on HTML and CSS; * the guidelines needed to be worded as testable statements instead of instructions to authors. The combination of more general applicability and higher precision proved very challenging. In 2018, the WCAG working group published WCAG 2.1. This remains fundamentally similar to the guidance in WCAG 2.0, with some additional recommendations made in particular areas:<ref name="torontouniversity">{{cite web|url=https://pressbooks.library.torontomu.ca/pwaa/chapter/the-evolution-of-web-accessibility/|title=The Evolution of Web Accessibility|publisher=[[Toronto Metropolitan University]]|access-date=8 June 2023}}</ref> * Mobile device accessibility * Low vision users ===Authoring Tool Accessibility Guidelines (ATAG)=== {{for|a coalition of aviation industry experts focusing on sustainable development issues|Air Transport Action Group}} Developed by the Authoring Tool Accessibility Guidelines Working Group, the ATAG 2.0 became a W3C Recommendation on 24 September 2015. ATAG is a set of guidelines for developers of any kind of authoring tool for Web content: simple [[HTML editor]]s, tools that export content for use on the Web (for example, word processors that can save as HTML), tools that produce multimedia, [[content management system]]s, learning management systems, social media, etc.. The goal is for developers to create tools that: * are accessible to authors regardless of disability; * produce accessible content by default; * support and encourage authors to create accessible content. Implementing ATAG 2.0 is a companion document that provides guidance on understanding and implementing ATAG 2.0. It gives an explanation of the intent of each success criterion, examples of the success criterion, and additional resources. Implementing ATAG 2.0 recommendations can reduce the costs for accessibility because authors are given the tools they need to create accessible content. List of authoring tools looking to implement ATAG 2.0: * [[CKEditor]] * [[Drupal]] Authoring Tool Accessibility Guidelines 1.0 was published in 2000 by the Authoring Tool Accessibility Guidelines Working Group. ===User Agent Accessibility Guidelines (UAAG)=== Developed by the User Agent Accessibility Guidelines Working Group, the UAAG 1.0 became a W3C Recommendation on 17 December 2002. The UAAG is a set of guidelines for user agent developers (such as [[web browser]]s and [[media player (application software)|media player]]s) aimed at making the user agent accessible to users with disabilities. Techniques for User Agent Accessibility Guidelines 1.0<ref>{{cite web|url=http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217/ |title=Techniques for User Agent Accessibility Guidelines 1.0 β W3C Note 17 December 2002 |publisher=W3.org |access-date=28 July 2013}}</ref> was published as a W3C Note on the same day; it provides techniques for satisfying the checkpoints defined in UAAG 1.0. Working group members also produced other supporting documents, including initial notes on How to evaluate a user agent for conformance to UAAG 1.0;<ref>{{cite web|url=http://www.w3.org/WAI/UA/2001/10/eval |title=How to evaluate a user agent for conformance to UAAG 1.0 |publisher=W3.org |date=2002-08-21 |access-date=28 July 2013}}</ref> this document was not formally approved by the working group. No user agents have been reported as fully conforming to UAAG 1.0. The working group is currently working on a new version of the guidelines. The first public draft of User Agent Accessibility Guidelines 2.0 was published on 12 March 2008.<ref>[http://www.w3.org/TR/2008/WD-UAAG20-20080312/ User Agent Accessibility Guidelines 2.0: W3C Working Draft 12 March 2008].</ref> ===XML Accessibility Guidelines (XAG)=== The XAG explains how to include features in XML applications (i.e. markup languages conforming to the XML specification) that promote accessibility. Work on these guidelines stopped in 2002; the guidelines are still a working draft. ===Accessible Rich Internet Applications (WAI-ARIA)=== {{further|WAI-ARIA}} '''WAI-ARIA''' (Web Accessibility Initiative β Accessible Rich Internet Applications) is a technical specification which became a [[World Wide Web Consortium|W3C]] [[W3C recommendation|Recommended Web Standard]] on 20 March 2014.<ref>{{cite web|url=http://www.w3.org/TR/wai-aria/ |title=Accessible Rich Internet Applications (WAI-ARIA) Version 1.0 |publisher=W3.org |access-date=22 April 2014}}</ref> It allows [[web page]]s (or portions of pages) to declare themselves as [[Application software|applications]] rather than as [[Static web page|static documents]], by adding role, property, and state information to dynamic web applications. ARIA is intended for use by developers of [[web application]]s, [[web browser]]s, [[Assistive technology|assistive technologies]], and accessibility evaluation tools.<ref>{{cite web|url=http://www.w3.org/WAI/intro/aria |title=WAI-ARIA Overview of WAI-ARIA |publisher=W3.org |date=2011-01-18 |access-date=28 July 2013}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)