#811: Web Content Accessibility Guidelines (WCAG) 2.2 2023-01-30 > 2023-02-24
Discussions
2023-03-13
Dan: changes since previous CR
Dan: suggest we close and give a positive review based on these 5 items .. I don't see any issues here.
Hadley: 3 of them are editorial. 5th one is renaming a session to "enhanced"
Dan: on 2.5.8 I don't see anything worrying ..
Hadley: only one that seems consequential is the parsing... Says "This criterion was originally adopted to address problems that Assistive Technology had directly parsing HTML. Assistive Technology no longer has any need to directly parse HTML and, consequently, these problems no longer exists." I presume that is the case...
Dan: this is in their wheelhouse...
Hadley: slightly architectural... But I think it's fine.
Lea: nothing seems worrying to me.
Hi @michael-n-cooper - thanks again for bringing this to our attention as part of wide review. We've reviewed and we're happy to see this go forward. Can you clarify regarding the parsing issue (4.1.1) - just for our benefit so we understand why AT is no longer parsing HTML? Are you confident that there aren't any remaining edge cases where that would still be needed?
Dan: comment left let's close at the plenary.
2023-03-27
Lea: can we rubberstamp.
Rossen: no substantive changes.
Dan: AT parsing removed https://www.w3.org/TR/2023/CR-WCAG22-20230124/#parsing
Rossen: this is good news.
Peter: data comes directly from
Yves: i would say OK to close:
Tess: yes.
Dan: closes and leaves comment
OpenedJan 30, 2023
Name of your specification
Web Content Accessibility Guidelines (WCAG) 2.2
URL of your specification
https://www.w3.org/TR/2023/CRD-WCAG22-20230125/
When does the review need to be finished?
2023-02-24
What has changed since any previous review?
https://www.w3.org/TR/WCAG22/#substantive-changes-since-the-6-september-2022-candidate-recommendation
Please point to the results of your own self-review
No response
Where and how should the i18n WG raise issues?
https://github.com/w3c/wcag/issues/
Pointer to any explainer for the spec
No response
Other comments
No response