- From: Mark Weiler <mweiler@alumni.sfu.ca>
- Date: Tue, 26 Jul 2022 17:19:32 +0000 (UTC)
- To: Silver Task Force <public-silver@w3.org>, WCAG <w3c-wai-gl@w3.org>, Makoto Ueki <makoto.ueki@gmail.com>
Received on Tuesday, 26 July 2022 17:19:48 UTC
I added comments about accessibility supported to the google doc, so that might have been me. I also provided the example from www.powermapper.com, which shows a group determining which web content techniques actually are compatible with browser and AT combinations. Mark Weiler On Tuesday, July 26, 2022 at 10:43:03 a.m. EDT, Makoto Ueki <makoto.ueki@gmail.com> wrote: - Present: AWK, Makoto Regrets: Bruce, Poornima Summary * Partipnats were just two this week. We might need more participants. * Two of us discussed our goal and steps and agreed with the following: - Our goal is to present pros and cons on 1) Keeping "Accessibility Supported" and 2) NOT keeping "Accessibility Supported" for WCAG 3. - STEP 1. Gather and document use cases on "Accessibility Supported", including Japan, Adobe, Section 508, and other cases if any. - STEP 2. Document pros and cons on 1) and 2) above and consider which we'll recommend. - STEP 3. Present "What form it will take if we'll take option 1) ("Keeping"). * We've got some comments from "Anonymous" for our starting document. We'd like to know who they are if possbile. - https://docs.google.com/document/d/1XxzwsgWZSDh2EDqTag-nYfrqAT3b6Glpu8DGbVpTd9M/ Minutes: https://www.w3.org/2022/07/26-wcag3-supported-minutes.html Cheers, Makoto
Received on Tuesday, 26 July 2022 17:19:48 UTC