Re: Proposed amendment to 1.4.11 for WCAG 2.2

+1

** katie **

*Katie Haritos-Shea*

*Principal ICT Accessibility Architect, **Board Member and W3C Advisory
Committee Rep for Knowbility *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.




On Wed, Oct 16, 2019 at 12:12 PM Chuck Adams <charles.adams@oracle.com>
wrote:

> +1, and it can be another test to our “amendment” process.
>
>
>
> Chuck
>
>
>
> *From:* David MacDonald <david100@sympatico.ca>
> *Sent:* Wednesday, October 16, 2019 10:04 AM
> *To:* Andrew Kirkpatrick <akirkpat@adobe.com>; AGWG Chairs <
> group-ag-chairs@w3.org>; Alastair Campbell <acampbell@nomensa.com>
> *Cc:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* Proposed amendment to 1.4.11 for WCAG 2.2
>
>
>
> Hi All
>
>
>
> In discussions regarding the new proposed success criterion for WCAG
> 2.2 around focus indicators, I had a discussion with Alastair about what
> the requirements of 1.4.11. When Alastair was explaining his perspective on
> it I believe he said that user interface components should have contrast
> ***in all of their states***. He said that the focus indicator could
> basically be ignored for 1.4.11 because it becomes part of the control as
> soon as the control has focus.
>
> I think the current language could be clarified in 2.2 without changing
> its meaning. Here's a suggestion based on our conversation. This might help
> clarify some of the confusion that people reading the document have. And I
> think it'll give us a little bit more to hang onto in the understanding
> document.
>
>
>
> CURRENT
> "Visual information required to identify user interface components
> ***and*** states...
>
>
> SUGGESTED
> Visual information required to identify user interface components ***in
> all their*** states
>
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613-806-9005
>
> LinkedIn
>
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_davidmacdonald100&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=b-9TIC95K-nLEKIDibNXAN_FKV-iXhLlAW2Zc3ebV_c&m=f6s28HJIOdqUMpLq29AMkUNCsmoFJICS98HWz4P428M&s=cf44tTpqnviQdABy84QJR68DB3ch2pKR5goratLJ2sg&e=>
>
> twitter.com/davidmacd
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_davidmacd&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=b-9TIC95K-nLEKIDibNXAN_FKV-iXhLlAW2Zc3ebV_c&m=f6s28HJIOdqUMpLq29AMkUNCsmoFJICS98HWz4P428M&s=4QaH53ZC7E6ApIctAdDBX1etwU1GaKDceEbBJDg77uQ&e=>
>
> GitHub
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DavidMacDonald&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=b-9TIC95K-nLEKIDibNXAN_FKV-iXhLlAW2Zc3ebV_c&m=f6s28HJIOdqUMpLq29AMkUNCsmoFJICS98HWz4P428M&s=D4YRsOsayN3bXrcbPfeZ8DEcivcyFOWJTdOKb6c_3Pw&e=>
>
> www.Can-Adapt.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.can-2Dadapt.com_&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=b-9TIC95K-nLEKIDibNXAN_FKV-iXhLlAW2Zc3ebV_c&m=f6s28HJIOdqUMpLq29AMkUNCsmoFJICS98HWz4P428M&s=-Pk1Ja40ru2jeIOYdrNyAN_5KIdHJcnKqj3nVuVLI74&e=>
>
>
>
> *  Adapting the web to all users*
>
> *            Including those with disabilities*
>
>
>
> If you are not the intended recipient, please review our privacy policy
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.davidmacd.com_disclaimer.html&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=b-9TIC95K-nLEKIDibNXAN_FKV-iXhLlAW2Zc3ebV_c&m=f6s28HJIOdqUMpLq29AMkUNCsmoFJICS98HWz4P428M&s=eF0KLkeykuXD7L09D2RHgialtYXK1Jp_vpN76Cwv4yc&e=>
>
>
>
>