- From: Wayne Dick <wayneedick@gmail.com>
- Date: Sat, 27 Jul 2019 15:20:29 -0700
- To: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Received on Saturday, 27 July 2019 22:21:30 UTC
The SC's for low vision (primarily) 1.4.10 Reflow, 1.4.11 Non Text Contrast, 1.4.12 Text Spacing and 1.4.13 Content on Hover or Focus have done a lot to close the accessibility gaps for low vision. More work is needed, but the progress made is significant. The LVTF needs to look at the new SCs (as is) and see how the needs identified in our requirements document have meet by including these SCs in 2.1. There are problems that have been identified, but we have not accumulated enough feedback to make normative changes. Developers need time to learn these SCs. They are not easy. I believe changing these SCs would have two negative effects that would overwhelm any benefits: (1) We may make premature choices may need further correction --spreading confusion, (2) We do not want to impede adoption. There will be plenty of time to change these criteria once we have a more significant population of adopters. The research on low vision is getting clearer and more useful for inclusion in standards every year. Many of the questions we raised in the requirements document are answered today -- just two years later. I think the 2.1 team did a good job on these SCs. We can let them sit a while before we make changes. Best, Wayne
Received on Saturday, 27 July 2019 22:21:30 UTC