Re: Recent changes to the WCAG 2.2 SC 2.1.1 Understanding page

Hi Steve,

Just to answer some of your questions, I note Patrick has also responded to some.

> On 2 Aug 2024, at 04:49, Steve Green <steve.green@testpartners.co.uk> wrote:
> 
> Was this change discussed anywhere? On GitHub, the most recent discussion I could find petered out in 2021 without a conclusion.

The change is recorded in a GitHUb commit on the 14th February: Add two notes/clarifications to 2.1.1/2.1.3 understanding <https://github.com/w3c/wcag/commit/a52aac11e8ea6c430ef545015d0be383ad699a77>

That commit references the original issue and subsequent discussion: New SC for keyboard operation? <https://github.com/w3c/wcag/issues/872> 


> How are we supposed to find out about such changes? It wasn’t publicised anywhere that I am aware of. There doesn’t appear to be any way to subscribe to notification of changes.

Issues, public discussions and subsequent changes are all recorded in the w3c/wcag GitHUb repo <https://github.com/w3c/wcag/>. You can subscribe to notifications on that. There is also a public mailing list used by the WCAG 2.x Back Log Task Force <https://lists.w3.org/Archives/Public/public-wcag2-issues/> that you should be able to subscribe to. They update that list on proposed changes that have been agreed following on from the public discussion and task force review.

I would encourage contributions to any of these forums and would obviously be welcoming of any interest you might have to become a W3C member and more actively participate in the work 😁.

> Is there a changelog anywhere that’s discoverable from the Understanding page? I can’t find one and had to trawl through the Internet Archive to find what changed and when. It would be helpful if the “last changed” date was displayed more prominently, ideally at the top of the page where we might see it.

There are two points here:

* Change Log: Short answer, no. Interesting idea though. Obviously GitHub is our version control system so I guess we could link to the commit history for each file. For example, keyboard.html commits <https://github.com/w3c/wcag/commits/main/understanding/20/keyboard.html>. Then it would just be a matter of finding a sensible way to include it into the design. If you think this would have legs, would you be willing to raise an issue?
* Last Changed date: Couple of things with this. Firstly the current last changed is when I publish the file, which is monthly. This isn’t really that great so we are moving to using the GitHub last modified date. This will result in some dates changing to be prior to their current last published. However, longer term it should be more useful as it is accurate. Secondly, this is a standard footer across the WAI site so I am hesitant to change that. Again, if you are willing to raise an issue we can have a bit of an explore. It might be worth it in this case to present the last changed and change log links in two places on these pages. Not sure.

> Why have the changes not been applied to the WCAG 2.0 and 2.1 versions of the Understanding page? Both WCAG versions are still in use, with 2.0 being used by Section 508 and 2.1 being used by the European Standard EN 301 549.

We are working on being able to do this.

Thanks

Kevin
AG WG Team Contact