- From: James Nurthen <james.nurthen@oracle.com>
- Date: Thu, 16 Nov 2017 09:13:16 -0800
- To: w3c-wai-gl@w3.org
- Message-ID: <9c2a1cc6-132b-f1bd-c8e7-a1a5dc0b8d1a@oracle.com>
Jon, I agree with you on this. However the difference in contrast between the non-hover state and the hover state does not need to meet a 3:1 ratio. regards, James On 11/16/2017 9:00 AM, Jonathan Avila wrote: > > Hover on contrast of text is already covered under SC 1.4.3 per this > group. A user with magnification may be using a pointing device and > needs to be able to see the content under the pointing device in > sufficient contrast. > > The minimum contrast success criterion (1.4.3) applies to text in the > page, including placeholder text and text that is shown when a pointer > is hovering over an object or when an object has keyboard focus. If > any of these are used in a page, the text needs to provide sufficient > contrast. > (https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html) > > Jonathan. > > Jonathan Avila > > Chief Accessibility Officer > > *Level Access, inc.*(formerly SSB BART Group, inc.) > > jon.avila@levelaccess.com <mailto:jon.avila@levelaccess.com> > > 703.637.8957 (Office) > > Visit us online: Website > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.levelaccess.com_&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=PZWbhq8_m5MIPsw5NiJMCINRFboumhwD9AUFvsmEcyg&e=>| > Twitter > <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_LevelAccessA11y&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=WzaWaNvHZviE5y4qtHKssDMocqgJ2I1LUu-81NiTgRE&e=>| > Facebook > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_LevelAccessA11y&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=TQpRMRkW0JFTO3iu3ksszd-4G7JKnv3xHMgbkfmuw-c&e=>| > LinkedIn > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_level-2Daccess&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=b_dxgZcMJfT_2YKo8nd5mh1uFmwOuzkNn5komJNzPyg&e=>| > Blog > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.levelaccess.com_blog_&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=rVzwoeqxoju77xMMdhn95Vj8PctlJ8W-TtYybJjntK4&e=> > > /Looking to boost your accessibility knowledge? Check out our free > webinars!/ > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ssbbartgroup.com_webinars_&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=tR6M_7BLAhr4xH-gNDQm1z0-2129nLeKF2_sK9SHgi4&e=>// > > The information contained in this transmission may be attorney > privileged and/or confidential information intended for the use of the > individual or entity named above. If the reader of this message is not > the intended recipient, you are hereby notified that any use, > dissemination, distribution or copying of this communication is > strictly prohibited. > > *From:*James Nurthen [mailto:james.nurthen@oracle.com] > *Sent:* Thursday, November 16, 2017 11:32 AM > *To:* w3c-wai-gl@w3.org > *Subject:* Re: CFC - Graphics Contrast > > No it would not. 1.4.1 does not mention the word state and include a > definition which includes hover. Hover does not fit into the things > which fail 1.4.1 > > Take for example the page > https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-without-color.html > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_TR_UNDERSTANDING-2DWCAG20_visual-2Daudio-2Dcontrast-2Dwithout-2Dcolor.html&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=azTSzRxVPTS09ZTpHYZ8tYh83UMk-5FTgeehLv0ldMQ&s=jreCk1vz8JLIIkxHL-l2uH6Lbf2F7USEOJeGlFz9RR4&e=> > > There are contents, intro, Previous and Next buttons at the top of the > page. The only difference when they are hovered is the background color. > > The background color is #dde and the hover background color is #aae > > The ratio between these is 1.6:1 > > I would not fail this page and I object to any SC which would fail > this. My current reading of this new SC along with the definition of > state proposed would and hence I object. > > On 11/16/2017 7:54 AM, Repsher, Stephen J wrote: > > Adding to what Alastair is saying, I’m confused by the objection > because, as you pointed out, using color alone to differentiate > between hover and non-hover would be a violation of 1.4.1. Only > when the 2 states are adjacent and touching would this SC come > into play, but the 3:1 ratio requirement is the same. > > Steve > > *From:*Alastair Campbell [mailto:acampbell@nomensa.com] > *Sent:* Thursday, November 16, 2017 3:03 AM > *To:* James Nurthen <james.nurthen@oracle.com> > <mailto:james.nurthen@oracle.com> > *Cc:* WCAG <w3c-wai-gl@w3.org> <mailto:w3c-wai-gl@w3.org> > *Subject:* RE: CFC - Graphics Contrast > > > Requiring hover to have sufficient contrast ratio to non-hover states has no accessibility > requirements behind it as far as I know and would unnecessarily > limit color choices in an already limited palette. > > Hi James, > > I don’t think that was discussed directly, but in order for that > to be an issue the controls in different states would have to be > adjacent, i.e. touching. Even without a mention of states, I think > that would be an issue in current WCAG conformance. > > There was some discussion about whether ‘existing’ was a state, > and people thought that wasn’t clear so ‘boundaries’ was added: > > “Visual information used to indicate states and boundaries of > active user interface components” > > (Still with the intent that if it isn’t there, you don’t have to > add something.) > > Does that help? > > -Alastair > > -- > Regards, James > > James Nurthen | Principal Engineer, Accessibility > Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 > 987 1918 <tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com > <sip:james.nurthen@oracle.com> > OracleCorporate Architecture > 500 Oracle Parkway | Redwood City, CA 94065 > Oracle is committed to developing practices and products that help > protect the environment > -- Regards, James <http://www.oracle.com> James Nurthen | Principal Engineer, Accessibility Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 987 1918 <tel:+1%20415%20987%201918> | Video: james.nurthen@oracle.com <sip:james.nurthen@oracle.com> Oracle Corporate Architecture 500 Oracle Parkway | Redwood City, CA 94065 <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
Received on Thursday, 16 November 2017 17:12:55 UTC