- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Mon, 13 Jan 2020 11:20:33 +0000
- To: Bruce Bailey <Bailey@Access-Board.gov>
- CC: 508 <508@Access-Board.gov>, WCAG list <w3c-wai-gl@w3.org>
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: https://github.com/w3c/wcag/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22WCAG+2.2%22+label%3A%22Normative%22 These would fall into the category of normative updates that are not new SCs: https://github.com/w3c/wcag/issues/770 Deprecating 4.1.1 https://github.com/w3c/wcag/issues/698 Making reflow 'down to' instead of 'at' 320px. https://github.com/w3c/wcag/issues/796 Phrasing used in 1.2.1, 1.2.2, and 1.2.3 is not consistent with similar SC in Guideline 1.2 https://github.com/w3c/wcag/issues/782 Revisiting Transcripts and Audio Description (SC 1.2.3/5/8) https://github.com/w3c/wcag/issues/895 Formatting of exceptions https://github.com/w3c/wcag/issues/695 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. Cheers, -Alastair
Received on Monday, 13 January 2020 11:20:43 UTC