Web Content Accessibility Guidelines

Last updated

WCAG
Web Content Accessibility Guidelines
W3C(r) Icon.svg
World Wide Web Consortium (W3C) logo
AbbreviationWCAG
Status W3C Recommendation
Year startedJanuary 1995 (1995-01)
First published9 May 1999 (1999-05-09)
Latest version2.2
October 5, 2023;5 months ago (2023-10-05) [1]
Preview version3.0
July 24, 2023;8 months ago (2023-07-24) [2]
Organization W3C, ISO, IEC [3]
CommitteeAccessibility Guidelines Working Group
Editors
  • Andrew Kirkpatrick
  • Joshue O Connor
  • Alastair Campbell
  • Ben Caldwell
  • Michael Cooper
  • Loretta Guarino Reid
  • Gregg Vanderheiden
  • Wendy Chisholm
  • John Slatin
  • Jason White
  • Rachael Bradley Montgomery
  • Jeanne Spellman
  • Shawn Lauriat
[1]
Domain Web accessibility
Copyright© 2020–2023 W3C® (MIT, ERCIM, Keio, Beihang).
Website

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. [3] WCAG 2.2 became a W3C Recommendation on 5 October 2023. [1]

Contents

History

Earlier guidelines (1995–1998)

The first web accessibility guideline was compiled by Gregg Vanderheiden and released in January 1995, just after the 1994 Second International Conference on the World-Wide Web (WWW II) in Chicago (where Tim Berners-Lee first mentioned disability access in a keynote speech after seeing a pre-conference workshop on accessibility led by Mike Paciello). [4]

Over 38 different Web access guidelines followed from various authors and organizations over the next few years. [5] These were brought together in the Unified Web Site Accessibility Guidelines compiled at the University of Wisconsin–Madison. [6] Version 8 of the Unified Web Site Accessibility Guidelines, published in 1998, served as the starting point for the W3C's WCAG 1.0. [7]

Version 1 (1999–2000)

The WCAG 1.0 were published and became a W3C recommendation on 5 May 1999. In February 2008, The WCAG Samurai, a group of developers independent of the W3C, and led by Joe Clark, published corrections for, and extensions to, the WCAG 1.0. [8]

Version 2 (2001–present)

The first concept proposal of WCAG 2.0 was published on 25 January 2001. In the following years new versions were published intended to solicit feedback from accessibility experts and members of the disability community. On 27 April 2006 a "Last Call Working Draft" was published. [9] Due to the many amendments that were necessary, WCAG 2.0 was published again as a concept proposal on 17 May 2007, followed by a second "Last Call Working Draft" on 11 December 2007. [10] [11] In April 2008 the guidelines became a "Candidate Recommendation". [12] On 3 November 2008 the guidelines became a "Proposed Recommendation". WCAG 2.0 was published as a W3C Recommendation on 11 December 2008. [13] [14] In October 2012, WCAG 2.0 were accepted by the International Organization for Standardization as an ISO International Standard, ISO/IEC 40500:2012. [15] [16] [17] [3] In early 2014, WCAG 2.0's Level A and Level AA success criteria were incorporated as references in clause 9.2 ("Web content requirements") of the European standard EN 301 549 published by ETSI. [18] EN 301 549 was produced in response to a mandate that the European Commission gave to the three official European standardisation bodies (CEN, CENELEC and ETSI) and is the first European standard for ICT products and services. [19] [20]

WCAG 2.2 became a W3C Recommendation on 5 October 2023. [1] Nine new criteria make their definitive debut in this new version of the WCAG standard. New sections have also been introduced that detail aspects of the specification which may impact privacy and security.

Version 3 (under development)

In early 2021, the Accessibility Guidelines Working Group presented the first public working draft (FPWD) of the future WCAG 3.0, intended to provide a range of recommendations for making web content more accessible. The 2021 FPWD introduced a new color contrast method as part of WCAG 3.0, as a candidate to replace the existing WCAG 2.x contrast specification, called the Accessible Perceptual Contrast Algorithm (APCA), which is currently being beta tested. [21] It should be made clear that no part of WCAG 3.0 is an official recommendation. WCAG 3.0 is a draft undergoing significant development efforts, and the expected release date as an official recommendation is not defined.

Versions

Version 1

WCAG 1.0 consist of 14 guidelines—each of which describes a general principle of accessible design. Each guideline covers a basic theme of web accessibility and is associated with one or more checkpoints that describes how to apply that guideline to particular webpage features.

Each of the in total 65 WCAG 1.0 checkpoints has an assigned priority level based on the checkpoint's impact on accessibility:

Version 2

WCAG 2.0 consist of twelve guidelines organized under four principles (websites must be perceivable, operable, understandable, and robust). Each guideline has testable success criteria (61 in all). [22] The W3C's Techniques for WCAG 2.0 [23] is a list of techniques that help authors meet the guidelines and success criteria. The techniques are periodically updated whereas the principles, guidelines and success criteria are stable and do not change. [24] WCAG 2.0 uses the same three levels of conformance (A, AA, AAA) as WCAG 1.0, but has redefined them. The WCAG working group maintains an extensive list of web accessibility techniques and common failure cases for WCAG 2.0. [25]

WCAG 2.1 is backwards-compatible with WCAG 2.0, which it extends with a further 17 success criteria.

WCAG 2.2 is backwards-compatible with WCAG 2.1 extending it a further nine success criteria and with WCAG 2.0 extending it a further 26 success criteria (including the 17 success criteria introduced by WCAG 2.1). Additionally, WCAG 2.2 has deprecated and removed the 4.1.1 success criterion. [26]

WCAG referenced by law

This section only refers to specific instances where WCAG, or a closely related derivative thereof, is specifically codified into law. There are many laws relating to accessibility in general and which may apply to websites, though they do not necessarily refer to WCAG. It is nevertheless considered prudent to follow WCAG guidelines to help protect against potential lawsuits relating to accessibility. [27]

United States

In 2013, the US Department of Transportation amended the Air Carrier Access Act (ACAA) to require Airlines make their Websites accessible, requiring conformance to WCAG 2.0, meeting Level AA Success Criteria. [28]

In January 2017, the US Access Board approved a final rule to update Section 508 of the Rehabilitation Act of 1973. The new rule adopts seventeen WCAG 2.0 success criteria, but 22 of the 38 existing A-level and AA-level criteria were already covered by existing Section 508 guidelines. The rule requires adherence to the new standards twelve months from its date of publication in the federal register. [29] [30]

In December, 2021 the 11th circuit court vacated a sometimes-cited case from 2017, which had referred to the WCAG guidelines as "industry standard". The 11th circuit court's ruling rendered the 2017 case moot. [31] As such, the case is no longer citable as caselaw. On March 2, 2022, the 11th circuit court refused to rehear the case.

European Union

Directive 2016/2102 [32] requires websites and mobile applications of public sector (i.e. government) bodies to conform to WCAG 2.1 Level AA. [33] [34] As of June 2021, the directive covers websites and mobile apps. [35] The European Parliament approved the directive in October 2016, [32] the European Commission updated the WCAG reference from 2.0 to 2.1 in December 2018. [34]

The European Accessibility Act (EAA) will become legally applicable in EU member states on 28 June 2025. The EAA will require websites, apps, ebooks, ecommerce platforms, PDFs and others to conform to WCAG 2.1 AA criteria within the EU.

United Kingdom

In September 2018, website and mobile app accessibility regulations for the public sector came into force, titled the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which currently applies the WCAG 2.1 AA level to websites operated by the "public sector", which means government agencies or organizations funded by the government, with some exclusions. The UK government published Understanding accessibility requirements for public sector bodies [36] to guide compliance.

The UK government is yet to announce if it will confirm the European Accessibility Act (EAA) into local law, but companies in the UK and outside of the EU will need to comply with EAA if they sell products or services in any EU member state. [37]

Canada

Regulations under the Accessibility for Ontarians with Disabilities Act, 2005 require that public web content of certain Ontario organizations complies with WCAG 2.0 Level AA.

The 2010/2012 Jodhan decision [38] caused the Canadian federal government to require all online web pages, documents and videos available externally and internally to meet the accessibility requirements of WCAG 2.0. [39]

Australia

The Australian government has also mandated via the Disability Discrimination Act 1992 that all Australian government websites meet the WCAG 2.0 level A accessibility requirements. [40]

Israel

The Israeli Ministry of Justice published regulations in early 2014, requiring Internet websites to comply with Israeli Standard 5568, which is based on the W3C Web Content Accessibility Guidelines 2.0.

The main differences between the Israeli standard and the W3C standard concern the requirements to provide captions and texts for audio and video media. The Israeli standards are somewhat more lenient, reflecting the current technical difficulties in providing such captions and texts in Hebrew. [41] [42]

Related Research Articles

<span class="mw-page-title-main">HTML</span> HyperText Markup Language

HyperText Markup Language or HTML is the standard markup language for documents designed to be displayed in a web browser. It defines the content and structure of web content. It is often assisted by technologies such as Cascading Style Sheets (CSS) and scripting languages such as JavaScript.

<span class="mw-page-title-main">Section 508 Amendment to the Rehabilitation Act of 1973</span>

In 1998, the U.S. Congress amended the Rehabilitation Act to require federal agencies to make their electronic and information technology accessible to people with disabilities. Section 508 was enacted to eliminate barriers in information technology, to make available new opportunities for people with disabilities and to encourage the development of technologies that will help achieve these goals. The law applies to all federal agencies when they develop, procure, maintain, or use electronic and information technology. Under Section 508, agencies must give employees with disabilities and members of the public access to information that is comparable to the access available to others.

<span class="mw-page-title-main">World Wide Web Consortium</span> Main international standards organization for the World Wide Web

The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web. Founded in 1994 and led by Tim Berners-Lee, the consortium is made up of member organizations that maintain full-time staff working together in the development of standards for the World Wide Web. As of 5 March 2023, W3C had 462 members. W3C also engages in education and outreach, develops software and serves as an open forum for discussion about the Web.

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.

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.

An open standard is a standard that is openly accessible and usable by anyone. It is also a common prerequisite that open standards use an open license that provides for extensibility. Typically, anybody can participate in their development due to their inherently open nature. There is no single definition, and interpretations vary with usage. Examples of open standards include the GSM, 4G, and 5G standards that allow most modern mobile phones to work world-wide.

<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.

Computer Graphics Metafile (CGM) is a free and open international standard file format for 2D vector graphics, raster graphics, and text, and is defined by ISO/IEC 8632.

<span class="mw-page-title-main">Computer accessibility</span> Ability of a computer system to be used by all people

Computer accessibility refers to the accessibility of a computer system to all people, regardless of disability type or severity of impairment. The term accessibility is most often used in reference to specialized hardware or software, or a combination of both, designed to enable the use of a computer by a person with a disability or impairment.

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.

PDF/UA, formally ISO 14289, is an International Organization for Standardization (ISO) standard for accessible PDF technology. A technical specification intended for developers implementing PDF writing and processing software, PDF/UA provides definitive terms and requirements for accessibility in PDF documents and applications. For those equipped with appropriate software, conformance with PDF/UA ensures accessibility for people with disabilities who use assistive technology such as screen readers, screen magnifiers, joysticks and other technologies to navigate and read electronic content.

The Government of Canada's Common Look and Feel (CLF) Standards for the Internet governed the branding, usability & accessibility standards for its websites and web applications from 2000 - 2010. It comprised the following four parts, now rescinded:

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

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.

AnySurfer is a Belgian organisation that promotes the accessibility of websites, apps, and digital documents for disabled individuals. It is also the name of a quality label which websites can obtain if they are fully accessible. AnySurfer is a national project run by Blindenzorg Licht en Liefde, a Belgian non-profit organisation that provides aid to the blind and the visually impaired.

EN 301 549 is a European standard for digital accessibility. It specifies requirements for information and communications technology to be accessible for people with disabilities.

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

References

  1. 1 2 3 4 Campbell, Alastair; Adams, Chuck; Montgomery, Rachel Bradley; Cooper, Michael; Kirkpatrick, Andrew, eds. (5 October 2023). "Web Content Accessibility Guidelines (WCAG) 2.2". 2.2. W3C. Archived from the original on 5 October 2023. Retrieved 5 October 2023.
  2. ↑ Spellman, Jeanne; Montgomery, Rachael Bradley; Cooper, Michael; Lauriat, Shawn; Adams, Chuck; Campbell, Alastair, eds. (24 July 2023). "Web Content Accessibility Guidelines (WCAG) 3.0". 3.0. W3C. Archived from the original on 27 September 2023. Retrieved 5 October 2023.
  3. 1 2 3 "ISO - ISO/IEC 40500:2012 - Information technology — W3C Web Content Accessibility Guidelines (WCAG) 2.0". ISO. ISO, IEC. 2012. Archived from the original on 7 December 2017. Retrieved 6 April 2021.
  4. ↑ Vanderheiden, Gregg C. (31 January 1995). "Design of HTML (Mosaic) Pages to Increase their Accessibility to Users with Disabilities; Strategies for Today and Tomorrow". Trace Center, University of Wisconsin–Madison. Archived from the original on 15 July 2012. Retrieved 22 September 2012.
  5. ↑ "References: Designing Accessible HTML Pages -- guidelines and overview documents". World Wide Web Consortium. Archived from the original on 2 March 2012. Retrieved 22 September 2012.
  6. ↑ "Trace Center". Trace Center, University of Wisconsin–Madison. Archived from the original on 19 September 2012. Retrieved 22 September 2012.
  7. ↑ Vanderheiden, Gregg C.; Chisholm, Wendy A., eds. (20 January 1998). "Unified Web Site Accessibility Guidelines". Trace Center, University of Wisconsin–Madison. Archived from the original on 2 March 2012. Retrieved 22 September 2012.
  8. ↑ "Home Page". WCAG Samurai. Archived from the original on 13 January 2013.
  9. ↑ Caldwell, Ben; Chisholm, Wendy; Slatin, John; Vanderheiden, Gregg, eds. (27 April 2006). "Web Content Accessibility Guidelines 2.0 – W3C Working Draft 27 April 2006". W3C. Archived from the original on 25 April 2014. Retrieved 6 April 2021.
  10. ↑ Caldwell, Ben; Cooper, Michael; Guarino Reid, Loretta; Vanderheiden, Gregg; Chisholm, Wendy; Slatin, John; White, Jason, eds. (17 May 2007). "Web Content Accessibility Guidelines 2.0 – W3C Working Draft 17 May 2007". W3C. Archived from the original on 23 June 2014. Retrieved 6 April 2021.
  11. ↑ Caldwell, Ben; Cooper, Michael; Guarino Reid, Loretta; Vanderheiden, Gregg; Chisholm, Wendy; Slatin, John; White, Jason, eds. (11 December 2017). "Web Content Accessibility Guidelines 2.0 – W3C Working Draft 11 December 2007". W3C. Archived from the original on 28 April 2014. Retrieved 6 April 2021.
  12. ↑ "WCAG 2.0 Candidate Recommendation Implementation Information". W3C. Archived from the original on 9 August 2022. Retrieved 21 April 2014.
  13. ↑ "Web Content Accessibility Guidelines (WCAG) 2.0 – W3C Recommendation 11 December 2008". W3.org. Archived from the original on 28 June 2018. Retrieved 27 July 2013.
  14. ↑ W3C: W3C Web Standard Defines Accessibility for Next Generation Web Archived 12 December 2008 at the Wayback Machine (press release, 11 December 2008).
  15. ↑ Henry, Shawn (15 October 2012). "WCAG 2.0 is now also ISO/IEC 40500!". World Wide Web Consortium. Archived from the original on 9 September 2013. Retrieved 23 October 2012.
  16. ↑ "W3C Web Content Accessibility Guidelines 2.0 approved as an ISO/IEC International Standard". World Wide Web Consortium. 15 October 2012. Archived from the original on 18 October 2012. Retrieved 23 October 2012.
  17. ↑ "ISO/IEC 40500:2012 - Information technology -- W3C Web Content Accessibility Guidelines (WCAG) 2.0". ISO. Archived from the original on 8 March 2013. Retrieved 23 October 2012.
  18. ↑ ETSI: EN 301 549 V1.1.1 (2014-02): Accessibility requirements suitable for public procurement of ICT products and services in Europe Archived 31 October 2015 at the Wayback Machine . Accessed 27 November 2015.
  19. ↑ CEN-CENELEC: New European Standard will help to make ICT products and services accessible for all Archived 8 December 2015 at the Wayback Machine . 19 February 2014. Accessed 27 November 2015.
  20. ↑ CEN-CENELEC: Mandate 376 Archived 10 March 2016 at the Wayback Machine . (No date). Accessed 27 November 2015.
  21. ↑ "Improving accessibility with the new APCA". Lightflows. 28 January 2022. Archived from the original on 4 August 2022. Retrieved 9 May 2022.
  22. ↑ "Web Content Accessibility Guidelines (WCAG) 2.0". W3C. Archived from the original on 18 February 2011. Retrieved 17 December 2014.
  23. ↑ "Techniques for WCAG 2.0". W3C. Archived from the original on 20 December 2014. Retrieved 17 December 2014.
  24. ↑ "Understanding Techniques for WCAG Success Criteria". W3C. Archived from the original on 18 December 2014. Retrieved 17 December 2014.
  25. ↑ "Techniques for WCAG 2.0". W3.org. Archived from the original on 27 July 2013. Retrieved 27 July 2013.
  26. 1 2 "Web Content Accessibility Guidelines (WCAG) 2.2". W3.org. Archived from the original on 4 February 2024. Retrieved 6 February 2024.
  27. ↑ "Disabled access to websites under UK law". Out-Law.com. October 2011. Archived from the original on 28 December 2014. Retrieved 15 January 2015.
  28. ↑ "Nondiscrimination on the Basis of Disability in Air Travel: Accessibility of Web Sites and Automated Kiosks at U.S. Airports" (PDF). transportation.gov. US Department of Transportation. Retrieved 21 December 2022.
  29. ↑ "Information and Communication Technology (ICT) Final Standards and Guidelines" (PDF). United States Access Board. 9 January 2017. Archived (PDF) from the original on 23 October 2020. Retrieved 10 January 2017.
  30. ↑ "Final Regulatory Impact Analysis: Final Rule to Update the Section 508 Standards and Section 255 Guidelines". United States Access Board. 5 January 2017. Archived from the original on 15 March 2020. Retrieved 10 January 2017.
  31. ↑ "Eleventh Circuit Vacates Gil v. Winn-Dixie Opinion Due to Mootness" . Retrieved 7 December 2022.
  32. 1 2 "Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies (Text with EEA relevance)". Publications Office of the European Union. 26 October 2016. Archived from the original on 30 April 2019. Retrieved 30 April 2019.
  33. ↑ "COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT pursuant to Article 294(6) of the Treaty on the Functioning of the European Union concerning the position of the Council on the adoption of a Proposal for a Directive of the European Parliament and of the Council on the accessibility of the websites and mobile applications of public sector bodies". Publications Office of the European Union. 18 July 2016. Archived from the original on 9 June 2020. Retrieved 10 February 2017.
  34. 1 2 "Commission Implementing Decision (EU) 2018/2048 of 20 December 2018 on the harmonised standard for websites and mobile applications drafted in support of Directive (EU) 2016/2102 of the European Parliament and of the Council". Publications Office of the European Union. 20 December 2018. Archived from the original on 12 April 2019. Retrieved 30 April 2019.
  35. ↑ "DIRECTIVE (EU) 2016/2102 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies, Article 12". Publications Office of the European Union. 26 October 2016. Archived from the original on 11 February 2017. Retrieved 10 February 2017.
  36. ↑ "Understanding accessibility requirements for public sector bodies". Central Digital & Data Office. 22 August 2022. Retrieved 20 December 2022.
  37. ↑ "How The European Accessibility Act may Impact UK Websites". www.ronins.co.uk. 7 September 2023. Retrieved 11 September 2023.
  38. ↑ "Jodhan decision". Ccdonline.ca. 30 May 2012. Archived from the original on 28 July 2013. Retrieved 27 July 2013.
  39. ↑ "Canadian Treasury Board Secretariat Standard on Web Accessibility". Tbs-sct.gc.ca. 1 August 2011. Archived from the original on 23 July 2013. Retrieved 27 July 2013.
  40. ↑ "Accessibility". Web Guide. Retrieved 20 December 2022.
  41. ↑ "Making the web accessible". Gov.il. State of Israel. Archived from the original on 22 June 2022. Retrieved 22 June 2022.
  42. ↑ "Website Accessibility Requirements". Israel Technology Law Blog. Archived from the original on 28 September 2014. Retrieved 22 June 2022.
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.