RE: Removing 4.1.1

This is true for Clause 10 on Non-Web Documents and Clause 11 on Software, but not for Clause 9 on Web. Fortunately, EN 301 549 is scheduled for updating in Q1 2023 anyway, including the intent to adopt WCAG 2.2 (when completed). This change to 4.1.1 can be considered in this upcoming update of EN 301 549.

Best,
  Shadi

---
Shadi Abou-Zahra
Amazon Devices and Services
Principal Accessibility Standards and Policy Manager
---


From: Andrew Kirkpatrick <akirkpat@adobe.com>
Sent: Thursday, 22 December, 2022 5:04 PM
To: Jon Avila <jon.avila@levelaccess.com>; w3c-wai-gl@w3.org
Subject: RE: [EXTERNAL]Removing 4.1.1


CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.


Good point Jon - I think that you are probably right. I was just looking at the link and ignoring the text that was right in front of me!

Thanks,
AWK

Andrew Kirkpatrick
Director, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk



From: Jon Avila <jon.avila@levelaccess.com<mailto:jon.avila@levelaccess.com>>
Date: Thursday, December 22, 2022 at 10:54 AM
To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: RE: Removing 4.1.1
Resent-From: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Resent-Date: Thursday, December 22, 2022 at 10:53 AM


EXTERNAL: Use caution when clicking on links or opening attachments.


702.10..1 says this

Web Content Accessibility Guidelines (WCAG) 2.0<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FTR%2FWCAG20&data=05%7C01%7Cakirkpat%40adobe.com%7C830fbae42d7c4b2b160d08dae434b936%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638073212473117988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=QdZduRnp51ryWMuEjLEXeiATyIqi2DPtaAhCy1Jt600%3D&reserved=0>, W3C Recommendation, December 11, 2008.

So, it is in my opinion it’s locked into the 2008 version – unless some errata would change that.

Jonathan

From: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
Sent: Thursday, December 22, 2022 10:32 AM
To: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>; Wilco Fiers <wilco.fiers@deque.com<mailto:wilco.fiers@deque.com>>; Abou-Zahra, Shadi <sabouzah@amazon.at<mailto:sabouzah@amazon.at>>; Bruce Bailey <Bailey@Access-Board.gov<mailto:Bailey@Access-Board.gov>>
Cc: w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>
Subject: Re: Removing 4.1.1

> What we do know is how these type of regs typically update.

> Section 508 is still on 2.0. If you are meeting 508, you have to meet what they have written down, which is from that dated version of 2.0.
> They could go through an internal process to update based on WCAG changing, but it is up to them. (How long did people complain about section 508 being on version 1.0?)

Bruce can hopefully correct me if I’m wrong, but Section 508 uses https:/www.w3.org/TR/WCAG20 as the normative reference, see https://www.access-board.gov/ict/#702.10.1<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.access-board.gov%2Fict%2F%23702.10.1&data=05%7C01%7Cakirkpat%40adobe.com%7C830fbae42d7c4b2b160d08dae434b936%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638073212473117988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=xVy1Qf3smU4YlJrtd8Bvvj4gz5yi2HH9o4xkH14CTns%3D&reserved=0>
So, if WCAG 2.0 was updated via an “Edited Specification” it seems that this would impact Section 508 immediately.
AWK


Amazon Development Center Austria GmbH
Brueckenkopfgasse 1
8020 Graz
Oesterreich
Sitz in Graz
Firmenbuchnummer: FN 439453 f
Firmenbuchgericht: Landesgericht fuer Zivilrechtssachen Graz