- From: Fernanda Bonnin <ferbonn@microsoft.com>
- Date: Tue, 4 Oct 2022 17:15:58 +0000
- To: Gregg Vanderheiden RTF <gregg@raisingthefloor.org>, Mary Jo Mueller <maryjom@us.ibm.com>
- CC: "public-wcag2ict-tf@w3.org" <public-wcag2ict-tf@w3.org>
- Message-ID: <MN0PR21MB31237D8E10D4C7D2A8F50E66BD5A9@MN0PR21MB3123.namprd21.prod.outlook.com>
Beyond the original WCAG2ICT TF not getting to AAA due to time, the survey on the approach for AAA from the previous WCAG2ICT TF<https://www.w3.org/2002/09/wbs/55145/20130406/results> also outlines various arguments for not including AAA. I think those arguments are still valid, and including AAA could be taken as a signal that the criteria ought to be applied. Best, Fernanda From: Gregg Vanderheiden RTF <gregg@raisingthefloor.org> Sent: Monday, October 3, 2022 9:19 PM To: Mary Jo Mueller <maryjom@us.ibm.com> Cc: public-wcag2ict-tf@w3.org Subject: [EXTERNAL] Re: Whether or not to include Level AAA criteria in WCAG2ICT I also wondered about whether including AAA items in WCAG2ICT would lead to their adoption in regulation. My conclusion was that - it didnt in WCAG - so I don't think it will here either. It MIGHT lead to their inclusion in an appendix of EN 301 549 (as was suggested already for WCAG AAA) But the warning against I think is good enough. And we HAVE been trying to get them more air time - more visibility. So I think we should include them. Last weekend I went through and examined each one - and they all seem to apply (except perhaps "sets of software" one) (which also was problematic at other levels). So I think the workload would be minimal I even posted a version of each in our template form so we can (relatively) quickly review and add if desired. So after looking at them I think we should - and include the warning. Gregg On Oct 3, 2022, at 6:39 PM, Mary Jo Mueller <maryjom@us.ibm.com<mailto:maryjom@us.ibm.com>> wrote: 1. Whether or not to include Level AAA criteria in WCAG2ICT The original WCAG2ICT work statement had AAA, but the task force didn't get to it. Once the Note published, there was other pressing work and so the group didn't return to analyze AAA since regulations didn't require it. In the initial review of the work statement by the Accessibility Guidelines Working Group (AG WG), there was some feedback that there would need to be a good reason not to incorporate Level AAA. Within our group, there seems to be general concern that if we included AAA in WCAG2ICT, that might encourage regulations to start requiring those criteria. Would like to know if there are objections to including in the scope as it was before, potentially not covering it in Phase 1 as noted in the edits in the timeline section in PR 2682<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag%2Fpull%2F2682%2Ffiles&data=05%7C01%7Cferbonn%40microsoft.com%7C21d7193f770d4591e5d108daa5bf8b87%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638004539355010724%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4xNgaegyr9v%2FFpBr12xk%2F7t4IDMkXb83BZ1cz62rpq4%3D&reserved=0>. The WCAG2ICT document itself could include WCAG's conformance note: It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content. Would this be sufficient? Please weigh in and offer alternatives, if needed..
Received on Tuesday, 4 October 2022 21:26:41 UTC