Category: wcag

WCAG 2.2 Is Now A W3C Recommendation

Post author By Dennis
Post date October 5, 2023
No Comments on WCAG 2.2 Is Now A W3C Recommendation

Announcing: WCAG 2.2 is now published as a web standard—a W3C Recommendation!

For an introduction to WCAG, see the WCAG 2 Overview. There are also a few updates in the WCAG 2 FAQ.

1 Success Criterion dropped in WCAG 2.2

Success Criterion 4.1.1 Parsing has been removed. More info on this highly debated decision from W3C WAI on why 4.1.1 was removed. Also, see the article The 411 on 4.1.1 by Adrian Roselli.

9 new Success Criteria in WCAG 2.2

2.4.11 Focus Not Obscured (Minimum) (AA)
2.4.12 Focus Not Obscured (Enhanced) (AAA)
2.4.13 Focus Appearance (AAA)
2.5.7 Dragging Movements (AA)
2.5.8 Target Size (Minimum) (AA)
3.2.6 Consistent Help (A)
3.3.7 Redundant Entry (A)
3.3.8 Accessible Authentication (Minimum) (AA)
3.3.9 Accessible Authentication (Enhanced) (AAA)

Web Content Accessibility Guidelines (WCAG) 2.2; W3C Recommendation 05 October 2023

roundup wcag wcag21

WCAG 2.1 Now A W3C Recommendation

Post author By Dennis
Post date June 19, 2018
No Comments on WCAG 2.1 Now A W3C Recommendation

On 5 June 2018, WCAG 2.1 was published with a Recommendation status, which means it’s stable and ready for implementation. The new guidelines help fill gaps in WCAG 2.0 particularly in the areas of mobile, low vision, and cognitive disabilities.

The new guidelines are backwards compatible with 2.0 as the official W3C announcement by Andrew Kirkpatrick and Michael Cooper explains:

All the criteria from WCAG 2.0 are included in WCAG 2.1, so web sites that conform to WCAG 2.1 will also conform to WCAG 2.0.

Learn more in an upcoming A11Y Talks What’s New with WCAG 2.1 with Carie Fisher and Andrew Macpherson, 27 June 2018.

Summary

Here is a quick list of the new criteria:

1.3.4 Orientation – Level AA
1.3.5 Identify Input Purpose – Level AA
1.3.6 Identify Purpose – Level AAA
1.4.10 Reflow – Level AA
1.4.11 Non-text Contrast – Level AA
1.4.12 Text Spacing– Level AA
1.4.13 Content on Hover or Focus – Level AA
2.1.4 Character Key Shortcuts – Level A
2.2.6 Timeouts – Level AAA
2.3.3 Animation from Interactions – Level AAA
2.5.1 Pointer Gestures – Level A
2.5.2 Pointer Cancellation – Level A
2.5.3 Label in Name – Level A
2.5.4 Motion Actuation – Level A
2.5.5 Target Size – Level AAA
2.5.6 Concurrent Input Mechanisms – Level AAA
4.1.3 Status Changes – Level AA

W3C page heading for WCAG 2.1

WCAG Improvements

It was such a relief when WCAG 2.0 became a W3C Recommendation back in December of 2008. But in the fast paced world of the web, nothing stays the same for very long. Even WCAG could use many improvements, especially after over three years. (Time sure flies!)

Jared Smith (@Jared_W_Smith) of WebAIM recently wrote an excellent article WCAG Next which explains some of the top issues and suggests how they can be improved. I pretty much agree with all. Here is a summary:

Remove the CAPTCHA Exception – should prohibit all CAPTCHA at Level AA.
Media Guidelines – a few suggestions here plus a recommendation for restructuring.
Contrast at Level A -minimal contrast requirement needed for Level A.
Decrease the 200% Text Resizing Requirement -biggest burden of Level AA.
Clarify Images of Text -this is subjective.
Specify Mechanisms to Bypass Blocks – add techniques such as skip-to, headings, landmark roles, and others.
“Can Be Programmatically Determined” -a confusing aspect of page conformance.
Require Keyboard Focus Indicators at Level A – “There is no reason why this should not be a Level A requirement.” Totally!
Remove Parsing Requirement – no direct benefit and difficult to test for accessibility; possibly move code validation requirement to Level AAA.

articles expert guidelines wcag wcag2

Perceivable, Operable, Understandable, and Robust

Post author By Dennis
Post date June 16, 2009
1 Comment on Perceivable, Operable, Understandable, and Robust

Joe Dolson recently completed an excellent four part series published on the Practical eCommerce web site. Another great read from Joe,highly recommended. The articles cover the following four fundamental principles of the Web Content Accessibility Guidelines 2.0 (WCAG 2):

Is it perceivable?
Is it operable?
Is it understandable?
Is it robust?

Here are the articles:

PS:
Joe was a guest back in 2007 in Podcast: #41: The Definition of Web Accessibility

adobe aria basic wcag

Five Layers, Questions, Adobe Encourages, Great Basics

Post author By Dennis
Post date May 7, 2009
No Comments on Five Layers, Questions, Adobe Encourages, Great Basics

The 5 Layers Of Web Accessibility
Great slide deck on Slideshare. In addition to HTML, CSS, and JavaScript, Dirk Ginader adds “CSS for JavaScript” and ARIA.

Is Your Web Site Accessible?
Great questions a web designer and developer should continually ask oneself.

Adobe encourages the European commission to use WCAG 2.0
Boring, but important.

Accessibility Basics
A great beginning-level article from Opera. Topics include:

What is accessibility?
Designing with accessibility in mind
Interoperability requirements
Features of an accessible web page
Standards for accessibility

1 Success Criterion dropped in WCAG 2.2

9 new Success Criteria in WCAG 2.2

Related Articles

Summary

Further Reading