- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 10 Oct 2023 16:28:33 +0100
- To: WCAG <w3c-wai-gl@w3.org>
Hey folx, I know this was discussed back and forth ad nauseam, but I've lost track of the final decisions... I'm wondering: * in WCAG 2.1 the note about 4.1.1 being effectively deprecated is included in the main spec, as a normative note for 4.1.1 https://www.w3.org/TR/WCAG21/#parsing * in WCAG 2.0 the main spec has not been changed https://www.w3.org/TR/WCAG20/#ensure-compat-parses - the fact that 4.1.1 is deprecated is only mentioned separately in the understanding https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-parses.html and the errata https://www.w3.org/WAI/WCAG20/errata/ Is there a particular reason why the main 2.0 spec itself doesn't have the note? Was it because we couldn't spin up an update/republication of 2.0. If so, does the mention in the errata supersede the main spec text (I assume so, since it says that it "may include normative corrections" at the start of the spec), and if so is that clear enough? If somebody's is filling in an ACR, should they simply mark 4.1.1 as "Supports" (keeping in mind that 508 still references WCAG 2.0)? Again, I assume so, but will likely need to add some info in the "Notes" column in the ACR to reiterate that this is based on the erratum for 4.1.1. P -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 10 October 2023 15:28:43 UTC