Web Content 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, were published in December 2008 and became an ISO standard, ISO/IEC 40500:2012 in October 2012.[3] WCAG 2.1 became a W3C Recommendation in June 2018.[1]

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]

The WCAG 1.0 were published and became a W3C recommendation on 5 May 1999. They have since been superseded by WCAG 2.0.

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:

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]

WCAG 2.0 were published as a W3C Recommendation on 11 December 2008.[9][10] They consist of twelve untestable guidelines organized under four principles (websites must be perceivable, operable, understandable, and robust). Each guideline has testable success criteria (61 in all).[11] The W3C's Techniques for WCAG 2.0[12] 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.[13]

Information and user interface components must be presentable to users in ways they can perceive.

Information and the operation of user interface must be understandable.

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

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.[14]

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.[15] Due to the many amendments that were necessary, WCAG 2.0 were published again as a concept proposal on 17 May 2007, followed by a second "Last Call Working Draft" on 11 December 2007.[16][17] In April 2008 the guidelines became a "Candidate Recommendation".[18] On 3 November 2008 the guidelines became a "Proposed Recommendation". WCAG 2.0 were published as a W3C Recommendation on 11 December 2008.

A comparison of WCAG 1.0 checkpoints and WCAG 2.0 success criteria is available.[19]

In October 2012, WCAG 2.0 were accepted by the International Organization for Standardization as an ISO International Standard, ISO/IEC 40500:2012.[20][21][22][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.[23] 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.[24][25]

WCAG 2.1 became a W3C Recommendation on 5 June 2018.[1] According to the W3C, it was:[1]

...initiated with the goal to improve accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices

and is backwards-compatible with WCAG 2.0, which it extends with a further 17 success criteria.[1]

As of May 2021, WCAG 2.2 is a W3C working draft,[2] and is scheduled to be finalized within 2021.[26]

In some countries and jurisdictions, there are also legal reasons, aside from ethical and commercial justifications[27] for implementing Web Content Accessibility Guidelines. Under UK law, if a business's website is not accessible, then the website owner could be sued for discrimination.[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 2017, a Federal Court in Florida identified the WCAG guidelines as the "industry standard" for website accessibility and found that Winn Dixie Store, Inc., violated the Americans with Disabilities Act by failing to render its website accessible to the sight impaired.[31]

Directive 2016/2102[32] requires websites and mobile applications of public sector bodies to conform with WCAG 2.1 Level AA.[33][34] New websites must comply from 23 September 2019 on, old websites from 23 September 2020 on and mobile applications from 23 June 2021 on.[35] The European Parliament has approved the directive in October 2016,[32] the European Commission updated the WCAG reference from 2.0 to 2.1 in December 2018.[34]

In January 2012, the Royal National Institute for the Blind (RNIB) in the United Kingdom issued a press release stating that it had served legal proceedings against low-cost airline Bmibaby[36] over their "failure to ensure web access for blind and partially sighted customers". As of October 2011, at least two actions against websites had been initiated by the RNIB, and settled without the cases being heard by a court.[28]

An employment tribunal finding against the Project Management Institute (PMI), was decided in October 2006, and the company was ordered to pay compensation of £3,000 for discrimination.[37]

Regulations under the 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]

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

At a state level, in response to the , the South Australian Government in partnership with Vision Australia and Royal Society for the Blind (SA) created an . Applying to all new or significantly upgraded applications, the toolkit is designed to help South Australian Government agencies, private business and community groups meet WCAG 2.0 and 2.1 AA.[41]

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.[42]