The Web Content Accessibility Guidelines ( WCAG ) is part of a series of web accessibility guidelines published by the World Wide Web Consortium (W3C) Web Accessibility Initiative (W3C), the major international standards organization for internet. They are a set of guidelines that define how to make content accessible, especially for people with disabilities - but also for all user agents, including very limited devices, such as mobile phones. The current version, WCAG 2.0, was published in December 2008 and became the ISO, ISO/IEC 40500: 2012 standard in October 2012. WCAG 2.1 is "Proposed Recommendation" in April 2018.
Video Web Content Accessibility Guidelines
Previous guide
The first web accessibility guidelines were compiled by Gregg Vanderheiden and released in January 1995, right after the Second International Conference 1994 on the World Wide Web (WWW II) in Chicago (where Tim Berners-Lee first mentions disabled access in the keynote address after seeing the workshop pre-conference on accessibility led by Mike Paciello).
Over 38 different web access guidelines were followed from various authors and organizations over the next few years. These are integrated into the Integrated Website Access Guidelines that are compiled at the University of Wisconsin-Madison. Version 8 of the Integrated Website Access Guide , published in 1998, serves as a starting point for WCAG 1.0 W3C.
Maps Web Content Accessibility Guidelines
WCAG 1.0
WCAG 1.0 was published and became a W3C recommendation on May 5, 1999. Since then, they have been replaced by WCAG 2.0.
WCAG 1.0 consists of 14 guidelines - each of which illustrates the general principle of accessible design. Each of the guidelines covers the basic theme of web accessibility and is associated with one or more checkpoints that explain how to apply the guidelines to certain webpage features.
- Guideline 1: Provide an equivalent alternative to auditory and visual content
- Guideline 2: Do not rely on color alone
- Guideline 3: Use markup and style sheets, and do it correctly
- Guideline 4: Clarify the use of natural language
- Guide 5: Create a table that changes gracefully
- Guideline 6: Make sure the page displaying the new technology is well transformed
- Guideline 7: Ensure user control of time-sensitive content changes
- Guide 8: Ensure direct access of embedded user interface
- Guideline 9: Design for the freedom of the device
- Guide 10: Temporary user solutions
- Guide 11: Use W3C technology and guidelines
- Guide 12: Provide context and orientation information
- Guide 13: Provides a clear navigation mechanism
- Guideline 14: Make sure the documents are clear and simple
Each of a total of 65 WCAG 1.0 checkpoints has a defined priority level based on the impact of checkpoints on accessibility:
- Priority 1: Web developers must comply with these requirements, otherwise it is not possible for one or more groups to access Web content. Compatibility with this level is described as A.
- Priority 2: Web developers must comply with these requirements, otherwise some groups may find it difficult to access Web content. Compatibility with this level is described as AA or Double-A.
- Priority 3: Web developers may comply with these requirements to make it easier for multiple groups to access Web content. Compatibility with this level is described as AAA or Triple-A.
WCAG Samurai
In February 2008, The WCAG Samurai, a group of independent developers from the W3C, and led by Joe Clark, published corrections for, and extensions to, WCAG 1.0.
WCAG 2.0
WCAG 2.0 was published as a W3C Recommendation on December 11, 2008. It consists of twelve (non-testable) guidelines organized under four principles (websites must be viewable , operable , understandable , and strong ). Each of the guidelines has criteria of success that can be tested (all 61). The W3C technique for WCAG 2.0 is a list of techniques that support authors to meet the guidelines and success criteria. The techniques are updated regularly while the principles, guidelines and criteria for success are stable and unchanged.
Principles
Perceivable
The information component and user interface must be displayed to the user in a way that they can feel.
- Guideline 1.1: Provide text alternatives for any non-text content so that it can be transformed into other forms that people need, such as a big print, braille, greeting, symbol or simpler language.
- Guideline 1.2: Time-based media: Provide an alternative to time-based media.
- Guideline 1.3: Create content that can be presented in various ways (eg simpler layout) without loss of information or structure.
- Guidance 1.4: Make it easy for users to view and hear content including separating the foreground from the background.
Operable
Components and user interface navigation should be operable.
- Guidance 2.1: Make all functions available from the keyboard.
- Guideline 2.2: Give users enough time to read and use the content.
- Guideline 2.3: Do not design content in ways that are known to cause seizures.
- Guidance 2.4: Provide a way to help users navigate, find content, and determine where they are.
Understandable
The information and operation of the user interface must be understandable.
- Guideline 3.1: Make text content readable and understandable.
- Guideline 3.2: Create a web page that appears and operates in a predictable manner.
- Guideline 3.3: Help users avoid and correct errors.
Strong
Content must be strong enough to be interpreted reliably by a variety of user agents, including assistive technologies.
- Guidelines 4.1: Maximize compatibility with current and future user agents, including auxiliary 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 a common failure case for WCAG 2.0.
Document history
The first draft proposal of WCAG 2.0 was published on January 25, 2001. In the following years a new version was published that was intended to collect feedback from accessibility experts and members of the disability community. On April 27, 2006 a "Last Call Working Draft" was published. Due to the many changes required, WCAG 2.0 was re-published as a draft proposal on May 17, 2007, followed by the second "Last Call of Calls" on December 11, 2007. In April 2008, the guidelines became "Candidate Candidates." On 3 November 2008 the guidelines become "Proposed Recommendation". WCAG 2.0 was published as a W3C Recommendation on December 11, 2008.
A WCAG 1.0 checkpoint comparison and WCAG 2.0 success criteria are available.
In October 2012, WCAG 2.0 was accepted by the International Organization for Standardization as an International Standard ISO, ISO/IEC 40500: 2012.
At the beginning of 2014, the AA and AA Level A success criteria from WCAG 2.0 are included as references in clause 9.2 ("Web content requirements") of the European standard EN 301 549 issued by ETSI. EN 301 549 was produced in response to the European Commission's mandate to three official European standardization bodies (CEN, CENELEC and ETSI) and was the first European standard for ICT products and services.
Legal duty
Businesses that have an online presence must provide accessibility to disabled users. Not only are there ethical and commercial reasons for implementing the Web Content Accessibility Guidelines, in some countries and jurisdictions, there are also legal reasons. According to English law, if a business website is inaccessible, then the website owner may be prosecuted for discrimination.
United States
In January 2017, the US Access Board approved the final rule to update Section 508 of the Rehabilitation Act of 1973. This new regulation adopted seventeen WCAG 2.0 success criteria, but 22 of the 38 existing AA and AA level criteria were covered by the guidelines Section 508 is there. The rule requires compliance with the new standard twelve months from the date of publication in the federal list.
In 2017, the Federal Court in Florida identified the WCAG guidelines as an "industry standard" for website accessibility and found that Winn Dixie Store, Inc., violated the Americans with Disabilities Act for failing to make its website accessible to defective sight.
European Union
In October 2016, the European Parliament approved a 2016/2102 directive that requires mobile sector agency websites and apps to adapt to WCAG 2.0 Level AA. The new website must comply with September 23, 2019, the old website from September 23, 2020 and the mobile app starting June 23, 2021 at.
United Kingdom
In January 2012, the Royal National Institute for the Blind (RNIB) in the United Kingdom issued a press release stating that they have undergone legal proceedings against low-cost carriers Bmibaby for "failure to ensure web access for blind and partial customers". As of October 2011, at least two actions against the website had been initiated by RNIB, and resolved without court cases.
A trial of a court action against the Project Management Institute (PMI), was decided in October 2006, and the company was ordered to pay a compensation of £ 3,000 for discrimination.
Canada
The 2010/2012 Jodhan Decision causes the Canadian federal government to require all online web pages, documents and videos available externally and internally to meet WCAG 2.0 accessibility requirements.
Australia
The Australian Government has also mandated through the 1992 Disability Discrimination Act that all Australian government websites meet WCAG accessibility requirements.
Israel
The Israeli Ministry of Justice issued a regulation in early 2014, which requires an Internet website to comply with Israeli Standard 5568, which is based on the W3C 2.0 Web Content Accessibility Guidelines.
The main difference between the Israeli standard and the W3C standard concerns the requirement to provide text and text for audio and video media. Israeli standards are somewhat more lenient, reflecting the current technical difficulties of providing texts and texts in Hebrew.
References
External links
- W3C - Web Content Accessibility Guidelines (WCAG) 2.0
- W3C - Introduction to Web Accessibility (WAI) to WCAG
- Mauve, the accessibility validator developed by HIIS Lab - ISTI CNR Pisa (Italy).
- WAVE - Online accessibility validity
- WCAG 2.0 checklist
- Reach WCAG 2.0 with PDF/UA - Document published by Image and Image Management Association (AIIM)
- WCAG for eLearning - Accessibility Handbook Training
- Digital Access Checklist WCAG AA: 10 Important Elements to Evaluate for Website Accessibility
Historic
- W3C - Web Content Accessibility Guidelines (WCAG) 1.0
- "Introduction". WCAG Samurai . Archived from the original in 2013-01-13.
Source of the article : Wikipedia
0 Comments