RE: Focus visible (enh) update

Hello,

My apologies, I believe I need to clarify my position in this Focus Visible (enh) update thread.  I agree with Sailesh and think that it is better to approach this as a user agent issue  and it is not best handled as a content author issue, when the content author has not provided custom focus indication.

So -1 to Focus visible (enh) as it is written and +1 to Sailesh’s statements.

Brooks

From: David MacDonald <david100@sympatico.ca>
Sent: Friday, October 18, 2019 1:28 PM
To: Newton, Brooks (TR Product) <Brooks.Newton@thomsonreuters.com>
Cc: Sailesh Panchang <sailesh.panchang@deque.com>; Alastair Campbell <acampbell@nomensa.com>; Detlev Fischer <detlev.fischer@testkreis.de>; w3c-wai-gl@w3.org
Subject: Re: Focus visible (enh) update

+1

Although it feels a bit awkward to require hundreds of thousands of developers and designers to tweak websites, when a plugin like stylus on the user side seems to do quite well. But I can live with the SC understanding that lots of people aren't technical enough to use that type of AT yet, and there are some limits to plugins.


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613-806-9005

LinkedIn
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_davidmacdonald100&d=DwMFaQ&c=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY&r=W3VUihr49D2x8upR4FtjMIsy0FSGEnqb4ghTiQJMtRw&m=AV-qZXeb0BEgfUinGXkd46Q1-m0JWDkreV4aL6_kNyw&s=EbcJepmCIM0IsgppWVyvPGCfLgzLkKSnxi3wKDvDUWg&e=>

twitter.com/davidmacd<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_davidmacd&d=DwMFaQ&c=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY&r=W3VUihr49D2x8upR4FtjMIsy0FSGEnqb4ghTiQJMtRw&m=AV-qZXeb0BEgfUinGXkd46Q1-m0JWDkreV4aL6_kNyw&s=3pNWDMV31DFaSzfraJ6aenlUu4Kf3RJFwZ_G5gvialQ&e=>

GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DavidMacDonald&d=DwMFaQ&c=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY&r=W3VUihr49D2x8upR4FtjMIsy0FSGEnqb4ghTiQJMtRw&m=AV-qZXeb0BEgfUinGXkd46Q1-m0JWDkreV4aL6_kNyw&s=nAn-FoRIz1ptKshPbOR-MPaBAkrVONI-TO9t-vFp4q4&e=>

www.Can-Adapt.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.can-2Dadapt.com_&d=DwMFaQ&c=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY&r=W3VUihr49D2x8upR4FtjMIsy0FSGEnqb4ghTiQJMtRw&m=AV-qZXeb0BEgfUinGXkd46Q1-m0JWDkreV4aL6_kNyw&s=4VfnsDRzBNYF8w5a5u4qkO2WRKeUVAJoJLiyVqUwXfY&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=4ZIZThykDLcoWk-GVjSLmy8-1Cr1I4FWIvbLFebwKgY&r=W3VUihr49D2x8upR4FtjMIsy0FSGEnqb4ghTiQJMtRw&m=AV-qZXeb0BEgfUinGXkd46Q1-m0JWDkreV4aL6_kNyw&s=6ve6H-BsXpNy71W6yZHMGPQVQcpDQ7Cwd82OxpLmfVM&e=>


On Fri, Oct 18, 2019 at 2:02 PM Newton, Brooks (TR Product) <Brooks.Newton@thomsonreuters.com<mailto:Brooks.Newton@thomsonreuters.com>> wrote:
+1

-----Original Message-----
From: Sailesh Panchang <sailesh.panchang@deque.com<mailto:sailesh.panchang@deque.com>>
Sent: Friday, October 18, 2019 12:47 PM
To: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Cc: Detlev Fischer <detlev.fischer@testkreis.de<mailto:detlev.fischer@testkreis.de>>; w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>
Subject: Re: Focus visible (enh) update

Alastair,
Reference your statements this morning:
<start>
In most cases if you are using a complete outline around the component it makes no difference at all, and you’d automatically fulfil it.
The one area I found that might surprise people is that the default (in Firefox) 1px dotted outline would not pass in most cases.
It is not a new thing that browser default indicators would fail, on the Mac the default indicators for some browsers fail the contrast requirement already.
</end>
Given this, is it reasonable to  ask designers and developers around
the world to  include markup / styling that will   correct issues that
should really be addressed by the browser?
Maybe browser makers should be urged to  improve the default focus indicator area and contrast issues that are noted as accessibility concerns.
And then if developers  override those  introducing accessibility barriers, those should be flagged to their attention as content-accessibility problems: much like when developers suppress default focus indicators.
Another example: the HTML5 placeholder attribute when first implemented posed contrast problems. True, developers were urged to remedy this but it was taken up with browser makers who fixed it at their end.
Best wishes,
--
Sailesh Panchang
Principal Accessibility Consultant
Deque Systems Inc
381 Elden Street, Suite 2000, Herndon, VA 20170
Mobile: 571-344-1765