- From: Wayne Dick <wayneedick@gmail.com>
- Date: Mon, 4 Jun 2018 17:41:54 -0700
- To: charles.adams@oracle.com
- Cc: Jake.Abma@ing.com, Jonathan Avila <jon.avila@levelaccess.com>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>
- Message-ID: <CAJeQ8SC2EQtqchjbxrdj_K40YzsNGhyGH9zyyAk1ApsrgDRp9A@mail.gmail.com>
Dear Charles, Originally the low vision task force recommended an ability to change color. This would enable personalized contrast because contrast is a function of color. Unfortunately the working group could not formulate this capability within the framework of WCAG. While we have included access to higher contrast for many people who are helped by this accommodation, we offer no way for users who need less light overall brightness to protect their eyes. Relief for people with photophobia is outside of the range of the WCAG framework. Wayne Dick This On Mon, Jun 4, 2018 at 4:56 PM Chuck Adams <charles.adams@oracle.com> wrote: > I want to chime in with some not necessarily productive information on > this topic. > > > > We interacted with an individual who needed to use high contrast mode. > This individual could not use black on white (where white was the dominant > color of the screen), as this mode would create migraines after 20 minutes > of use, and the individual would be unable to work for the remainder of the > day. > > > > This individual could, however, make use of white on black (where black > was the dominant color of the screen). > > > > The lesson I took from this experience is that it’s important to test both > high contrast themes, and that advocating one as a work-around over the > other (when the U/I behaves poorly in one but not the other) is not in fact > an adequate work-around. > > > > I’m interested as well in best practices if they exist, > > > > Thanks, > > Charles Adams > > > > *From:* Abma, J.D. (Jake) <Jake.Abma@ing.com> > *Sent:* Monday, June 4, 2018 11:19 AM > *To:* Wayne Dick <wayneedick@gmail.com>; Jonathan Avila < > jon.avila@levelaccess.com> > *Cc:* GLWAI Guidelines WG org <w3c-wai-gl@w3.org> > *Subject:* Too much contrast and guidelines > > > > Hi Wayne / Jon / all, > > > > Are there also guidelines / rules / best practices / research on “too much > contrast”? > > I know black/#000000 on white/#ffffff is often too much but how can I > substantiate this… > > > > Thanks! > > Jake > > > > > > > > > > Regards, > > Jake Abma > > > > Accessibility Lead ING > > Product owner at Team A11Y > > http://www.a11yportal.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.a11yportal.com_&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=b-9TIC95K-nLEKIDibNXAN_FKV-iXhLlAW2Zc3ebV_c&m=AlnapBg7sGE4TeibL3ncHLG9Tt-73uZCfCroYqt1q2I&s=2N0mCz25yVNtbGT_sxE8XGJjHpUfNhGu_BSMWMUCsj8&e=> > > > > ING Nederland / CIO / Omnichannel / Experience > > ACT C.02.406, Bijlmerdreef 24 > > Postbus 1800, 1000 BV Amsterdam > > 0031 (0)6 - 25 27 52 46 > > *jake.abma@ing.com <jake.abma@ing.com>* > > > > > > ----------------------------------------------------------------- > > > > ATTENTION: > > > > The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately. > > > > ----------------------------------------------------------------- > >
Received on Tuesday, 5 June 2018 00:42:57 UTC