- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 15 Nov 2017 16:24:45 +0000
- To: Jonathan Avila <jon.avila@levelaccess.com>, WCAG <w3c-wai-gl@w3.org>
Hi Jon, > if the author uses a border to communicate the role of something > then the aspect has to meet the contrast requirements. Agree. Also, I noticed we missed out the default-appearance exception, so I’ve updated that to say: “Visual information used to indicate state for active user interface components, except where the appearance of the component is determined by the user agent and not modified by the author.” > It doesn't require an author provide that affordance if they didn't. So if I choose to make a piece of text blue and have it function like a button nothing needs to be done other than the contrast of the blue text in the non-focused state or non-pressed state of that button. Agree. > If I use a solid background to make something look like a button then I have to make sure the edge of the background has sufficient contrast from the surrounding pixels outside of the focused or pressed state. Agree. > If I have multiple buttons with some in pressed and others in non-pressed states the difference between the colors used for the pressed states need to have a 3:1 ratio as well. Agree. It is also worth considering the ‘adjacent’ aspect, if buttons are not immediately adjacent, then they do not have to contrast with each other. > Focus indicators need to provide 3:1 contrast as well. Is that right? Yes, although with-what depends on what they are adjacent to. Cheers, -Alastair
Received on Wednesday, 15 November 2017 16:25:11 UTC