- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Wed, 30 Mar 2016 10:42:12 -0500
- To: Andrew Kirkpatrick <akirkpat@adobe.com>
- Cc: "jon.avila@ssbbartgroup.com" <jon.avila@ssbbartgroup.com>, Alastair Campbell <acampbell@nomensa.com>, Katie Haritos-Shea <ryladog@gmail.com>, Scott McCormack <scott.mccormack@ssbbartgroup.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>, "Rochford, John" <john.rochford@umassmed.edu>
+1 Very nice, Andrew. Thank you. Kindest Regards, Laura On 3/30/16, Andrew Kirkpatrick <akirkpat@adobe.com> wrote: > Proposed recommendation to share with WCAG: > > It is recommended that the text of links and controls which changes in > response to focus and hover events meets the appropriate contrast > requirement in WCAG 2.0 Success Criteria 1.4.3. Both hover and focus states > impact low-vision users: > > * Focus: Low-vision keyboard users may be unable to read low-contrast > text on a focused control and due to page magnification may be unable to > simply tab away from a focused control and keep that control in view on the > screen. > * Hover: Many low vision users use the mouse pointer to follow along > when reading text (with or without magnification) like people do with a > finger or pen when reading printed materials. This is very common for > magnification users who will use the mouse pointer to control the > magnification view area. In such a case a hover with bad contrast prevents > users from being able to read effectively. > > > Thanks, > AWK > > Andrew Kirkpatrick > Group Product Manager, Accessibility > Adobe > > akirkpat@adobe.com > http://twitter.com/awkawk > http://blogs.adobe.com/accessibility > > From: Jonathan Avila > <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>> > Date: Tuesday, March 29, 2016 at 10:54 > To: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>, > Katie GMAIL <ryladog@gmail.com<mailto:ryladog@gmail.com>>, Scott McCormack > <scott.mccormack@ssbbartgroup.com<mailto:scott.mccormack@ssbbartgroup.com>> > Cc: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>, > public-low-vision-a11y-tf > <public-low-vision-a11y-tf@w3.org<mailto:public-low-vision-a11y-tf@w3.org>>, > "Rochford, John" > <john.rochford@umassmed.edu<mailto:john.rochford@umassmed.edu>> > Subject: RE: LVTF position on contrast requirements for interactive control > states > > It is recommended that text of links and controls that changes at any time > meets the appropriate contrast requirement in WCAG 2.0 Success Criteria > 1.4.3. Given that it can be difficult to find enough color combinations to > address the design needs and meet the contrast requirement, it is sufficient > to meet the SC 1.4.3 contrast requirement for text that changes upon > keyboard focus and allowable that text that changes when the link or control > is in the active or hover states to not meet the SC 1.4.3 contrast > requirement. > -- Laura L. Carlson
Received on Wednesday, 30 March 2016 15:42:41 UTC