Re: Most common new WCAG 2.1 issues found

I'm seeing content on hover and focus a fair amount on little ? icons.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613-806-9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>


On Wed, Aug 22, 2018 at 6:36 AM Aparna Pasi <aparna.pasi@deque.com> wrote:

> +1, in all our experience with WCAG 2.1 , non text color contrast is the
> most used SC..
>
> On Mon, Aug 20, 2018 at 6:30 PM John Foliot <john.foliot@deque.com> wrote:
>
>> +1, and I'll add that contrary to the perspective of some, native tab
>> focus on a customized backgrounds should be failing as well when the
>> contrast is insufficient.
>>
>> http://john.foliot.ca/demos/focuscolor.html
>>
>> JF
>>
>> On Mon, Aug 20, 2018 at 7:37 AM, Denis Boudreau <denis.boudreau@deque.com
>> > wrote:
>>
>>> While that may be true Patrick, based on my own experience assessing
>>> websites, I would have guess that insufficient non-text color contrast
>>> would be the most frequent kind of 2.1 issue as well. This stuff has been
>>> everywhere for as long as I can remember.
>>>
>>> /Denis
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Aug 20, 2018 at 08:29 Patrick H. Lauke <redux@splintered.co.uk>
>>> wrote:
>>>
>>>> I'd caution as well that there's likely still a high degree of
>>>> uncertainty around how to test, what actually counts as a pass/fail,
>>>> what something does/doesn't apply to. Something that will even out over
>>>> time, no doubt...but for many auditors, this is uncharted territory
>>>> until they get more familiar with spotting common patterns of failure
>>>> etc.
>>>>
>>>> P
>>>>
>>>> On 20/08/2018 12:01, Alastair Campbell wrote:
>>>> > Hi everyone,
>>>> >
>>>> > A little aneq-data-point, I asked on Twitter what people were finding
>>>> > came up most in WCAG 2.1 audits from the new criteria:
>>>> >
>>>> > https://twitter.com/alastc/status/1030455692853952512
>>>> >
>>>> > Non-text contrast (on inputs / focus styles) came up the most for
>>>> most
>>>> > people. On a per-instance basis that isn’t too surprising, search
>>>> boxes
>>>> > are often on every page.
>>>> >
>>>> > I’m not sure there is anything to conclude from this, but if we start
>>>> > seeing people act on that more often, perhaps it is moving the needle.
>>>> >
>>>> > Kind regards,
>>>> >
>>>> > -Alastair
>>>> >
>>>> > --
>>>> >
>>>> > www.nomensa.com <http://www.nomensa.com/>
>>>> > tel: +44 (0)117 929 7333 / 07970 879 653
>>>> > follow us: @we_are_nomensa or me: @alastc
>>>> > Nomensa Ltd. King William House, 13 Queen Square, Bristol BS1 4NT
>>>> <https://maps.google.com/?q=13+Queen+Square,+Bristol+BS1+4NT&entry=gmail&source=g>
>>>> >
>>>> > Company number: 4214477 | UK VAT registration: GB 771727411
>>>> >
>>>>
>>>> --
>>>> Patrick H. Lauke
>>>>
>>>> www.splintered.co.uk | https://github.com/patrickhlauke
>>>> http://flickr.com/photos/redux/ | http://redux.deviantart.com
>>>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>>>
>>>> --
>>> /Denis
>>>
>>> --
>>> Denis Boudreau
>>> Principal SME & trainer
>>> Web accessibility, inclusive design and UX
>>> Deque Systems inc.
>>> 514-730-9168
>>>
>>> Keep in touch: @dboudreau
>>>
>>
>>
>>
>> --
>> *John Foliot* | Principal Accessibility Strategist
>>
>> Deque Systems - Accessibility for Good
>>
>> deque.com
>>
>>
>
> --
> Satya Jaya Aparna Pasi
> CPACC Professional | Team Accessibility Lead
> Deque Software
> aparna.pasi@deque.com | +91-7093400949
> "Accessibility is a feature not an option"
>
>
>