W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

Re: Updates to Understanding 1.4.11 part 2

From: John Foliot <john.foliot@deque.com>
Date: Wed, 13 Jun 2018 14:03:20 -0500
Message-ID: <CAKdCpxwHjyaTZdwryW-Gg5hxxe-DTRh=AEwa0xxdzjxcTuVrPg@mail.gmail.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: David MacDonald <david100@sympatico.ca>, Alastair Campbell <acampbell@nomensa.com>, WCAG group <w3c-wai-gl@w3.org>, LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org>
Hi Laura,

> But the big question is: Is it an author's responsibility to solve a user
agent issue?

I suspect that very much depends on how you define "responsibility". If you
are talking about "legal" responsibility, I'll side with the exception
language, as I agree it truly is the user-agent at "fault" here.

That said, in our Understanding documents we should be
sufficiently transparent to note that while this *is* a currently known UA
problem in some browsers (which may or may-not linger), it's a simple
problem to fix, and for maximum "usability" and adherence to the spirit of
WCAG content designers *should* address this known issue. My reasoning is
that once designers "Understand" the problem, they can adjust to it quickly
and easily, as the fix is quite simple: when you change one aspect of the
design (background color) you are responsible for all of the other contrast
changes that the initial change necessitates - that color choices are
"paired" with contrast and visible state changes as well. In practice and
observation during my multiple training activities, this does not appear to
be a hard idea to grasp by the designers (in fact, on more than one
occasion when discussing focus contrast, designers have brought this up to
me first, as they begin to grok the issues related to visual design.)



On Wed, Jun 13, 2018 at 12:23 PM, Laura Carlson <laura.lee.carlson@gmail.com
> wrote:

> Hi John and all,
> On 6/13/18, John Foliot <john.foliot@deque.com> wrote:
> > Any Mac users familiar with this: https://www.focusingly.net ?
> >
> > I wonder aloud if it addresses the problem we're discussing (Mac's
> > inaccessible native focus ring).
> I think it could.
> But the big question is: Is it an author's responsibility to solve a
> user agent issue?
> In the Hover SC discussions, I was told that it isn't an author's
> responsibility. Rather, it is a Silver issue.
> With Marla Runyan's techniques [2], we had author title attribute
> fixes for 1.4.13 too. But that didn't stop the User Agent exception
> from going into 1.4.13. [1]
> Let's be consistent with how we handle the User Agent problem in  SC
> 1.4.13 and 1.4.11. If it is a Silver issue in one SC, it should be
> Silver issue in both.
> Kindest Regards,
> Laura
> [1] https://lists.w3.org/Archives/Public/w3c-wai-gl/2018AprJun/0712.html
> [2] https://jsfiddle.net/obsqynyp/4/
> --
> Laura L. Carlson

John Foliot
Principal Accessibility Strategist
Deque Systems Inc.

Advancing the mission of digital accessibility and inclusion
Received on Wednesday, 13 June 2018 19:03:47 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:26 UTC