Web Accessibility Initiative

Last updated

The World Wide Web Consortium (W3C)'s Web Accessibility Initiative (WAI) is an effort to improve the accessibility of the World Wide Web for people with disabilities. People with disabilities encounter difficulties when using computers generally, but also on the Web. Since they often require non-standard devices and browsers, making websites more accessible also benefits a wide range of user agents and devices, including mobile devices, which have limited resources. According to a US government study, 71% of website visitors with disabilities will leave a website that is not accessible. [1] [2] [3]

Contents

The W3C launched the Web Accessibility Initiative in 1997 with endorsement by The White House and W3C members. [4] [5] It has several working groups and interest groups that work on guidelines, technical reports, educational materials and other documents that relate to the several different components of web accessibility. These components include web content, web browsers and media players, authoring tools, and evaluation tools.

Organization

WAI develops guidelines and other technical reports through the same process as other parts of the W3C. [6] Like other W3C initiatives, the WAI consists of several working groups and Special interest groups, each with its own focus. Only working groups can produce technical reports that become W3C recommendations. A working group can sometimes delegate specific work to a task force, which then presents its results back to the working group for approval. Interest groups may produce reports (for example, as W3C Notes), but not recommendations. Each of these types of groups (working group, task force, interest group) can have one or more mailing lists. They meet through conference calls at regular intervals (typically every week or every other week) and sometimes use web-based surveys to collect input or comments from participants. They can also meet face to face (one to five times per year).

In 1997 Judy Brewer has been the director of the WAI. [7] In this role she has championed improving accessibility of the web for people with disabilities and older users.

Authoring Tool Accessibility Guidelines Working Group (ATAG WG)

The Authoring Tool Accessibility Guidelines Working Group develops guidelines, techniques and supporting resources for tools that create web content, ranging from desktop HTML editors to content management systems. The accessibility requirements apply to two types of things: the user interface on the one hand, and the content produced by the tool on the other. The working group consists of representatives from organizations that produce authoring tools, researchers, and other accessibility experts. The working group produced the Authoring Tool Accessibility Guidelines 1.0 in 2000 and completed Authoring Tool Accessibility Guidelines (ATAG) 2.0 in 2015. [8] A supporting document, Implementing ATAG 2.0, [9] provides additional explanation, examples and resources for ATAG 2.0. It also published a document on Selecting and Using Authoring Tools for Web Accessibility. [10]

Education and Outreach Working Group (EOWG)

The Education and Outreach Working Group develops materials for training and education on Web accessibility. This working group has produced documents on a wide range of subjects, including:

Currently, the working group has a task force to support the work done in the WAI-AGE project. This project published a document that reviews literature about the needs of older users and compares these needs with those of people with disabilities as already addressed in WAI guidelines. [17] [18]

The Education and Outreach Working Group can also review working drafts produced by other WAI working groups.

Evaluation and Repair Tools Working Group (ERT WG)

The Evaluation and Repair Tools Working Group develops technical specifications that support the accessibility evaluation and repair of Web sites. It also maintains a database of tools for evaluating Web sites and for making them more accessible ("repair", "retrofitting"). The working group consists mainly of developers of such tools and researchers. Current work focuses on

Protocols & Formats Working Group (PFWG)

The Protocols & Formats Working Group reviews all W3C technologies for accessibility before they are published as a recommendation. It has also published a note on accessibility issues of CAPTCHA, [24] a paper on natural language usage for people with cognitive disabilities, [25] and initial work on accessibility requirements for XML-based markup languages (XML Accessibility Guidelines).

In 2006, the working group started development of a set of document and specifications for accessible rich internet applications: WAI-ARIA. [26] [27] [28] [29]

Research and Development Interest Group (RDIG)

The goal of the Research and Development Interest Group is

This interest group has seen very little activity since 2004. Its current charter expired at the end of 2006. [30]

User Agent Accessibility Guidelines Working Group (UAWG)

The User Agent Accessibility Guideline Working Group develops guidelines, techniques and other documents to promote the accessibility of user agents: browsers and plug-ins. The working group consists mainly of organizations that develop user agents, researchers, and other accessibility experts. UAWG published User Agent Accessibility Guidelines (UAAG) 2.0 in December 2015. Supporting documentation includes: UAAG 2.0 Reference and UAAG Mobile Examples. The working group published User Agent Accessibility Guidelines 1.0 (UAAG 1.0) as a W3C Recommendation in 2002.

WAI Interest Group (WAI IG)

The WAI Interest Group is an open group with a mailing list to which anyone can subscribe. W3C staff post announcements of new WAI documents to this mailing list to invite reviews and comments. Members of the list also post announcements of relevant events and publications, and ask advice on issues related to web accessibility. The language of the mailing list is English; there are no parallel mailing lists in other languages.

Accessibility Guidelines Working Group (AGWG)

The Accessibility Guidelines Working Group (formerly the Web Content Accessibility Guidelines Working Group) [31] produces guidelines, techniques and other supporting documents relating to the accessibility of Web content. Web content refers to any information you may find on a Web site: text, images, forms, sound, video, etcetera, regardless whether these were produced on the server side or on the client side (with a client-side scripting language such as JavaScript). Thus, the guidelines also apply to rich internet applications.

The working group consists of representatives from industry, accessibility consultancies, universities, organizations that represent end users, and other accessibility experts.

The working group published the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) as W3C Recommendation in 1999, followed by techniques documents in 2000. [32] In 2001, the working group started work on WCAG 2.0, which became a W3C Recommendation on 11 December 2008. [33] [34]

WAI Coordination Group

The WAI Coordination Group co-ordinates that activities of the WAI working groups (and interest groups). Its activities are not public.

Guidelines and technical reports

Web Content Accessibility Guidelines (WCAG)

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 [35] 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 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: [36]

Authoring Tool Accessibility Guidelines (ATAG)

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 editors, tools that export content for use on the Web (for example, word processors that can save as HTML), tools that produce multimedia, content management systems, learning management systems, social media, etc..

The goal is for developers to create tools that:

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:

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 browsers and media players) aimed at making the user agent accessible to users with disabilities. Techniques for User Agent Accessibility Guidelines 1.0 [37] 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; [38] 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. [39]

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)

WAI-ARIA (Web Accessibility Initiative – Accessible Rich Internet Applications) is a technical specification which became a W3C Recommended Web Standard on 20 March 2014. [40] It allows web pages (or portions of pages) to declare themselves as applications rather than as static documents, by adding role, property, and state information to dynamic web applications. ARIA is intended for use by developers of web applications, web browsers, assistive technologies, and accessibility evaluation tools. [41]

See also

Related Research Articles

<span class="mw-page-title-main">Semantic Web</span> Extension of the Web to facilitate data exchange

The Semantic Web, sometimes known as Web 3.0, is an extension of the World Wide Web through standards set by the World Wide Web Consortium (W3C). The goal of the Semantic Web is to make Internet data machine-readable.

The Resource Description Framework (RDF) is a World Wide Web Consortium (W3C) standard originally designed as a data model for metadata. It has come to be used as a general method for description and exchange of graph data. RDF provides a variety of syntax notations and data serialization formats, with Turtle currently being the most widely used notation.

A HTML editor is a program used for editing HTML, the markup of a web page. Although the HTML markup in a web page can be controlled with any text editor, specialized HTML editors can offer convenience, added functionality, and organisation. For example, many HTML editors handle not only HTML, but also related technologies such as CSS, XML and JavaScript or ECMAScript. In some cases they also manage communication with remote web servers via FTP and WebDAV, and version control systems such as Subversion or Git. Many word processing, graphic design and page layout programs that are not dedicated to web design, such as Microsoft Word or Quark XPress, also have the ability to function as HTML editors.

<span class="mw-page-title-main">Accessibility</span> Modes of usability for people with disabilities

Accessibility is the design of products, devices, services, vehicles, or environments so as to be usable by people with disabilities. The concept of accessible design and practice of accessible development ensures both "direct access" and "indirect access" meaning compatibility with a person's assistive technology.

Web annotation can refer to online annotations of web resources such as web pages or parts of them, or a set of W3C standards developed for this purpose. The term can also refer to the creations of annotations on the World Wide Web and it has been used in this sense for the annotation tool INCEpTION, formerly WebAnno. This is a general feature of several tools for annotation in natural language processing or in the philologies.

Web standards are the formal, non-proprietary standards and other technical specifications that define and describe aspects of the World Wide Web. In recent years, the term has been more frequently associated with the trend of endorsing a set of standardized best practices for building web sites, and a philosophy of web design and development that includes those methods.

Web accessibility, or eAccessibility, is the inclusive practice of ensuring there are no barriers that prevent interaction with, or access to, websites on the World Wide Web by people with physical disabilities, situational disabilities, and socio-economic restrictions on bandwidth and speed. When sites are correctly designed, developed and edited, more users have equal access to information and functionality.

Web usability of a website consists of broad goals of usability, presentation of information, choices made in a clear and concise way, a lack of ambiguity and the placement of important items in appropriate areas as well as ensuring that the content works on various devices and browsers.

SPARQL is an RDF query language—that is, a semantic query language for databases—able to retrieve and manipulate data stored in Resource Description Framework (RDF) format. It was made a standard by the RDF Data Access Working Group (DAWG) of the World Wide Web Consortium, and is recognized as one of the key technologies of the semantic web. On 15 January 2008, SPARQL 1.0 was acknowledged by W3C as an official recommendation, and SPARQL 1.1 in March, 2013.

GRDDL is a markup format for Gleaning Resource Descriptions from Dialects of Languages. It is a W3C Recommendation, and enables users to obtain RDF triples out of XML documents, including XHTML. The GRDDL specification shows examples using XSLT, however it was intended to be abstract enough to allow for other implementations as well. It became a Recommendation on September 11, 2007.

RDFa or Resource Description Framework in Attributes is a W3C Recommendation that adds a set of attribute-level extensions to HTML, XHTML and various XML-based document types for embedding rich metadata within Web documents. The Resource Description Framework (RDF) data-model mapping enables its use for embedding RDF subject-predicate-object expressions within XHTML documents. It also enables the extraction of RDF model triples by compliant user agents.

Simple Knowledge Organization System (SKOS) is a W3C recommendation designed for representation of thesauri, classification schemes, taxonomies, subject-heading systems, or any other type of structured controlled vocabulary. SKOS is part of the Semantic Web family of standards built upon RDF and RDFS, and its main objective is to enable easy publication and use of such vocabularies as linked data.

<span class="mw-page-title-main">Web Content Accessibility Guidelines</span> Web accessibility guidelines

The Web Content Accessibility Guidelines (WCAG) are part of a series of web accessibility guidelines published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), the main international standards organization for the Internet. They are a set of recommendations for making Web content more accessible, primarily for people with disabilities—but also for all user agents, including highly limited devices, such as mobile phones. WCAG 2.0 was published in December 2008 and became an ISO standard, ISO/IEC 40500:2012 in October 2012. WCAG 2.2 became a W3C Recommendation on 5 October 2023.

In computing, Terse RDF Triple Language (Turtle) is a syntax and file format for expressing data in the Resource Description Framework (RDF) data model. Turtle syntax is similar to that of SPARQL, an RDF query language. It is a common data format for storing RDF data, along with N-Triples, JSON-LD and RDF/XML.

Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA) is a technical specification published by the World Wide Web Consortium (W3C) that specifies how to increase the accessibility of web pages, in particular, dynamic content, and user interface components developed with Ajax, HTML, JavaScript, and related technologies.

Extensible HyperText Markup Language (XHTML) is part of the family of XML markup languages which mirrors or extends versions of the widely used HyperText Markup Language (HTML), the language in which Web pages are formulated.

Lisa Seeman is an inventor and an entrepreneur and has been instrumental in creating standards for interoperability and accessibility.

XHTML+RDFa is an extended version of the XHTML markup language for supporting RDF through a collection of attributes and processing rules in the form of well-formed XML documents. XHTML+RDFa is one of the techniques used to develop Semantic Web content by embedding rich semantic markup. Version 1.1 of the language is a superset of XHTML 1.1, integrating the attributes according to RDFa Core 1.1. In other words, it is an RDFa support through XHTML Modularization.

A Voluntary Product Accessibility Template (VPAT) is a template containing information regarding how an Information and communications technology product or service conforms with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. § 794 (d)). Section 508 provides guidelines for rendering ICT accessible to, and therefore usable by, people with disabilities. The VPAT was originally designed as a tool for vendors to document product compliance to Section 508 and facilitate government market research on ICT with accessible features. Many people started to call the completed document a "VPAT" but the wider procurement community would prefer to call it a product Accessibility Conformance Report, or ACR. The distinction is that the VPAT is the incomplete form, and the ACR is the completed report using the VPAT template.

The Guidelines for Indian Government Websites (GIGW) are a set of guidelines developed by the National Informatics Centre (NIC) in

References

  1. ↑ Robinson, Ryan (25 September 2019). "How Website Accessibility Affects Online Businesses In 2019 And How To Respond". Forbes . Retrieved 8 June 2023.
  2. ↑ Gevorkian, David (23 May 2022). "Who Benefits from Web Accessibility". Be Accessible. Retrieved 8 June 2023.
  3. ↑ "Excluded web visitors often don't complain, they just leave". Media Access Australia . 18 September 2017. Retrieved 8 June 2023.
  4. ↑ "World Wide Web Consortium (W3C) Launches International Web Accessibility Initiative". 7 April 1997. Retrieved 8 June 2023.
  5. ↑ "Daniel Dardailler's account of the origin of WAI". W3.org. Retrieved 28 July 2013.
  6. ↑ "How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute". W3.org. Retrieved 28 July 2013.
  7. ↑ "Judy Brewer". W3C. Retrieved 8 June 2023.
  8. ↑ Richards, Jan; Spellman, Jeanne; Treviranus, Jutta. "Authoring Tool Accessibility Guidelines (ATAG) 2.0". World Wide Web Consortium (W3C). Retrieved 16 February 2016.
  9. ↑ Richards, Jan; Spellman, Jeanne; Treviranus, Jutta. "Implementing ATAG 2.0". World Wide Web Consortium (W3C). Retrieved 16 February 2016.
  10. ↑ "Selecting and Using Authoring Tools for Web Accessibility". W3.org. Retrieved 28 July 2013.
  11. ↑ "Accessibility Features of CSS – W3C NOTE 4 August 1999". W3.org. Retrieved 28 July 2013.
  12. ↑ "Curriculum for Web Content Accessibility Guidelines 1.0". W3.org. Retrieved 28 July 2013.
  13. ↑ "Evaluating Web Sites for Accessibility". W3.org. Retrieved 28 July 2013.
  14. ↑ "Planning Web Accessibility Training". W3.org. 21 February 2013. Retrieved 28 July 2013.
  15. ↑ "Developing a Web Accessibility Business Case for Your Organization : overview". W3.org. 7 September 2012. Retrieved 28 July 2013.
  16. ↑ "How People with Disabilities Use the Web". W3.org. Retrieved 28 July 2013.
  17. ↑ WAI-AGE Project (IST 035015)
  18. ↑ "Web Accessibility for Older Users: A Literature Review – W3C Working Draft 14 May 2008". W3.org. Retrieved 28 July 2013.
  19. ↑ "Evaluation and Report Language 1.0 Schema". W3.org. Retrieved 28 July 2013.
  20. ↑ Evaluation and Report Language 1.0 Guide
  21. ↑ "HTTP Vocabulary in RDF". W3.org. Retrieved 28 July 2013.
  22. ↑ Representing Content in RDF
  23. ↑ "Pointer Methods in RDF". W3.org. Retrieved 28 July 2013.
  24. ↑ Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web – W3C Working Group Note 23 November 2005
  25. ↑ "Natural Language Usage – Issues and Strategies for Universal Access to Information". W3.org. Retrieved 28 July 2013.
  26. ↑ Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap) – W3C Working Draft 26 September 2006. This is the first public working draft; the most recent version can always be found at www.w3.org/TR/wai-aria-roadmap/ w3.org
  27. ↑ "Accessible Rich Internet Applications (WAI-ARIA) Version 1.0 – W3C Last Call Working Draft 24 February 2009". W3.org. Retrieved 8 June 2023.
  28. ↑ "WAI-ARIA Best Practices – W3C Working Draft 24 February 2009". W3.org. Retrieved 28 July 2013.
  29. ↑ WAI-ARIA Implementation Guide – W3C Working Draft 24 February 2009
  30. 1 2 Judy Brewer. "Research and Development Interest Group (RDIG) Charter". W3.org. Retrieved 28 July 2013.
  31. ↑ Initiative (WAI), W3C Web Accessibility (13 May 2024). "WAI Working Groups and Interest Groups". Web Accessibility Initiative (WAI). Retrieved 14 May 2024.{{cite web}}: CS1 maint: numeric names: authors list (link)
  32. ↑ Kingman, Abby (21 May 2018). "A brief history of WCAG". Last Call Media. Retrieved 8 June 2023.
  33. ↑ Web Content Accessibility Guidelines (WCAG) 2.0 – W3C Recommendation 11 December 2008
  34. ↑ W3C: W3C Web Standard Defines Accessibility for Next Generation Web (press release, 11 December 2008).
  35. ↑ "Techniques for Web Content Accessibility Guidelines 1.0 – W3C Note 6 November 2000". W3.org. Retrieved 28 July 2013.
  36. ↑ "The Evolution of Web Accessibility". Toronto Metropolitan University . Retrieved 8 June 2023.
  37. ↑ "Techniques for User Agent Accessibility Guidelines 1.0 – W3C Note 17 December 2002". W3.org. Retrieved 28 July 2013.
  38. ↑ "How to evaluate a user agent for conformance to UAAG 1.0". W3.org. 21 August 2002. Retrieved 28 July 2013.
  39. ↑ User Agent Accessibility Guidelines 2.0: W3C Working Draft 12 March 2008.
  40. ↑ "Accessible Rich Internet Applications (WAI-ARIA) Version 1.0". W3.org. Retrieved 22 April 2014.
  41. ↑ "WAI-ARIA Overview of WAI-ARIA". W3.org. 18 January 2011. Retrieved 28 July 2013.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.