- From: Wayne Dick <wayneedick@gmail.com>
- Date: Sat, 11 Jun 2016 13:20:55 -0700
- To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Received on Saturday, 11 June 2016 20:22:04 UTC
Technology must enable the following access to accommodate users with low vision: Users must be capable of adjusting the visual interface to meet their exact visual needs [issue 74]. When an implementation for the web denies this level of flexibility to its users, it is inaccessible to some large population of people with low vision. Depending on the aspects of the visual interface that are impossible to change, the groups of people low vision that will be left out will differ . When no implementation of a technology can meet this need, then the entire technology is inaccessible. We know that HTML/CSS/JavaScript can produce rich implementations that meet this need. Thus, the set of accessible technology is not empty. What do we do with technologies that cannot meet the visual flexibility requirement? In the case of non-text content regarding blindness, we simply require a text alternative. In the case where a technology cannot meet visual flexibility do we just require an accessible technology alternative?
Received on Saturday, 11 June 2016 20:22:04 UTC