Re: WCAG 2.2 status update

Hi Bruce,

 > I think we may have run out the clock on the opportunity to have such a discussion.
 If (IF!) we stay on target in January, there should be time in Feb to address some of these.

Prioritisation would help, I'm using the "WCAG 2.2" & "Normative" tags in github to collect them: 

These would fall into the category of normative updates that are not new SCs: Deprecating 4.1.1 Making reflow 'down to' instead of 'at' 320px. Phrasing used in 1.2.1, 1.2.2, and 1.2.3 is not consistent with similar SC in Guideline 1.2 Revisiting Transcripts and Audio Description (SC 1.2.3/5/8) Formatting of exceptions Contrast algorithm number update.

If I've missed any, please tag them with "WCAG 2.2" and "Normative". 

Oh, and in case it catches anyone else out: The Errata on a spec (e.g. WCAG 2.0) are *not* incorporated into that spec, but into the next one. E.g. WCAG 2.1 includes all the errata on WCAG 2.0, but not the errata *for* 2.1.

Apparently it is something to do with publication dates on the face of the spec, but I haven't got to the bottom of that, it seems like there should be more to it.

I just mention that in case anyone (else) was thinking about how updates/errata converge.



Received on Monday, 13 January 2020 11:20:43 UTC