- From: Bruce Bailey <Bailey@Access-Board.gov>
- Date: Thu, 3 Oct 2024 11:04:52 +0000
- To: "public-wcag2ict-tf@w3.org" <public-wcag2ict-tf@w3.org>
- CC: AGWG Chairs <group-ag-chairs@w3.org>
- Message-ID: <MW5PR22MB3511C8FE9829324C41C7A41FE3712@MW5PR22MB3511.namprd22.prod.outlook.com>
+1, but I am quite okay with deferring the issue to WAI staff, TF, TF leads, and AG chairs. FWIW, it might not be “sealed and shipped” unit the date changes on the public-facing WG note. * W3C Working Group <https://www.w3.org/TR/wcag2ict/> Note 5 September 2013 (same as previously) * W3C Editor's <https://w3c.github.io/wcag2ict/> Draft 03 October 2024 (today) From: Gregg Vanderheiden <gregg@vanderheiden.us> Sent: Thursday, October 3, 2024 2:09 AM To: public-wcag2ict-tf@w3.org Subject: Too Late now but.... I think we misnamed our Closed Functionality Section * It does indeed talk about closed functionality issues / items * But it also includes things that have nothing to do with closed functionality (i.e.,. do not relate to the ability to work with assistive technologies) Some examples 1. orientation — this has to do with hardware like kiosks or wall-mounted ICT where there is no opportunity to “reorient” the screen, and so there is no reason to require that the content be reorientable. This has nothing to do with AT 2. Contrast - this again has to do with the contrast of hardware — but not AT compatibility and there between half-a-dozen and a dozen more like that. The section I think should have been titled something like * Other considerations when applying WCAG to non-web content * Closed Functionality and other issues that ICT must deal with that Web Content does not We could included Closed functionality as a sub category along with “other things that need to be handled differently when applying to non-web ICT.” as a second….. Not sure exactly how or what we should have called it and this is a week to late to be “already too late” since we just sealed and shipped it. But this is just a heads up — that our the name of our section is misleading and confusing until you realize it covers other things as well. It might be useful when talking about this or encountering confusion by others with this important section. NO ACTION ITEM. (just a heads up) g PS This all came out of the application of WCAG2ICT in the EN 301 549 task force.
Received on Thursday, 3 October 2024 11:05:07 UTC