Does WCAG 2.1 checklist Replace WCAG 2.0?

Question

Accepted Answer

WCAG 2.0 was released nearly 10 years ago with 12 guidelines for digital accessibility, divided among four principles Perceivable, Operable, Understandable and Robust. Each guideline of the WCAG checklist has a list of success criteria. After 4 years of work, the Accessibility Guidelines Working Group (AGWG) of the W3C released its latest recommendations. Still, WCAG 2.1 doesn’t replace or canceled. WCAG 2.1 only adds few new success criteria to the existing WCAG checklist 2.0. Authorities that enforce major accessibility laws, including the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and the Accessibility for Ontarians with Disabilities Act (AODA), continue to require complying with WCAG 2.0 level AA. But W3C encourages organizations to use the most recent version of WCAG when developing or updating their content or digital accessibility policy.

Success Criteria	Recommendations
1.2.4 Captions (Live)	Synchronized captions require for all live videos
1.2.5 Audio Description	audio description require for all video content
1.3.4 – Orientation	Requires authors not to rely on a screen orientation
1.3.5 – Identify Input Purpose	Ensure common names are provided using the HTML autocomplete list
1.4.3 – Contrast (Minimum)	Contrast ratio between text and background is at least 4.5:1 & Large text (over 18 point or 14 point bold) has a contrast ratio of at least 3:1
1.4.4 – Resize Text	Text can be resized to 200% without loss of content or function
1.4.5 – Images of Text	If the same visual presentation can be made using text alone, an image is not used to present that text
1.4.10 – Reflow	Your website requires Responsive design (or a few tricks to get zoom to work
1.4.11 – Non-Text Contrast	High contrast between pieces of text and their backgrounds of atleast 3:1
1.4.12 – Text Spacing	Text spacing can be overridden to improve the reading experience. But it requires author not to interfere with user style sheets and other CSS based client side interventions
1.4.13 – Content on Hover Focus	Ensuring content visible on hover or keyboard focus does not lead to accessibility issues
2.4.5 – Multiple Ways	Offer several ways to find pages ‐ at least two of a list of related pages, table of contents, site map, site search, or list of all available web pages
2.4.7 Focus Visible	Keyboard focus should be visible and clear. It is visually apparent which page element has the current keyboard focus
3.1.2 Language of Parts	When appropriate, users when the language on a page changes by ‘lang’ attribute
3.2.3 Consistent Navigation	Use menus consistently & do not change order when navigating through the site
3.2.4 Consistent Identification	Use icons and buttons consistently. For example, a search box at the top of the site should always be labeled the same way
3.3.3 Error Suggestion	Suggest fixes when users make errors in a timely and accessible manner
3.3.4 Error Prevention (Legal, Financial, Data)	Reduce the risk of input errors for sensitive data. If the user can change or delete legal, financial, or test data, the changes/deletions are reversible, verified, or confirmed.
4.1.3 – Status Changes	Distances between paragraphs, rows, words and characters must be able to be increased to a certain value

Web content accessibility Guideline 2.1 AA - WCAG Checklist

Follow the Web Content Accessibility Guideline(WCAG) 2.1AA checklist & improve your web content accessibility for people with a wide range of disabilities.

WCAG Checklist – 2.1 AA

Does WCAG 2.1 checklist Replace WCAG 2.0?

Category :

Tags :

About Guna Nadar