- From: Wayne Dick <wayneedick@gmail.com>
- Date: Wed, 18 Jan 2017 10:18:41 -0800
- To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CAJeQ8SAL5je+HOJrej=Z6MTVbuAKGbvfEaJE7u7eJHn3ELNR3Q@mail.gmail.com>
I think Alastair's Adaptive should be first on the agenda. 1. Adaptation that works under the author-controlled styling/scripting in a default browser, such as Resize content. 2. Adapta tion that subtly over-rides author styles, such as text-color. 3. Adaptation that will likely break layouts, such as linearisation, spacing, font-family. Also several from COGA that I’ve seen, such as adding icons to the text. 4 . Personalisation where the website provides options for the user, or in some way works with the user’s settings. We need to look at Text-Color, Resize Content, Linearize, Spacing, and Font Family. The discussion has unveiled some confusion in how our proposals are going to be interpreted. How do we make it clear that a mechanism exists does not mean that the author needs to program an accommodation? How do we address the claim that if we cannot come up with an HTMLi failure then we don't need an SC. For me, element level adaptation seems more like a necessity. Finally, for many on WCAG WG there is a serious hostility to requesting visual adaptations. It is like they look for any excuse to deny them. Can we discuss this, and come up with consistent language? Wayne
Received on Wednesday, 18 January 2017 18:19:54 UTC