E-mail List Archives
Thread: Where does CSS issue fail WCAG2?
Number of posts in this thread: 9 (In chronological order)
From: Lynn Holdsworth
Date: Thu, Jun 11 2015 4:45AM
Subject: Where does CSS issue fail WCAG2?
No previous message | Next message →
Hi all,
Just doing an audit, and we have a styled focus indicator that's not
quite wide enough to fit around its "Next" button and starts halfway
through the N.
We feel like it should fail, but it's not a text resizing issue, and
we can't find anything else to fail it under.
Does this fail? If so how?
Thanks as always, Lynn
From: chaals
Date: Thu, Jun 11 2015 4:54AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
- lynn.holdsworth@
11.06.2015, 12:46, "Lynn Holdsworth" < = EMAIL ADDRESS REMOVED = >:
> Just doing an audit, and we have a styled focus indicator that's not
> quite wide enough to fit around its "Next" button and starts halfway
> through the N.
>
> We feel like it should fail, but it's not a text resizing issue, and
> we can't find anything else to fail it under.
>
> Does this fail? If so how?
It fails the unwritten rule "don't be ridiculous". It may also cause issues with comprehension and visual recognition, but it isn't clear that WCAG covers those well enough anyway.
just 2 cents worth
Chaals
--
Charles McCathie Nevile - web standards - CTO Office, Yandex
= EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com
From: Jonathan Avila
Date: Thu, Jun 11 2015 4:56AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
> Does this fail? If so how
The most likely place it could fail would be under contrast.
Jonathan
> On Jun 11, 2015, at 6:45 AM, Lynn Holdsworth < = EMAIL ADDRESS REMOVED = > wrote:
>
> Does this fail? If so how
From: Lynn Holdsworth
Date: Thu, Jun 11 2015 5:26AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
Thanks guys. Yes - there should be a "don't be ridiculous" clause in
WCAG. Can we fail them for not having one?
OK will check contrast, but if that passes then I suppose we'll just
have to add this one as a recommendation.
Cheers, Lynn
On 11/06/2015, Jonathan Avila < = EMAIL ADDRESS REMOVED = > wrote:
>> Does this fail? If so how
>
> The most likely place it could fail would be under contrast.
>
> Jonathan
>
>> On Jun 11, 2015, at 6:45 AM, Lynn Holdsworth < = EMAIL ADDRESS REMOVED = >
>> wrote:
>>
>> Does this fail? If so how
> > > > >
From: Moore,Michael (HHSC)
Date: Thu, Jun 11 2015 6:56AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
I would think that it would fail to meet the design specifications. I can't imagine that the designer meant for it to look like that.
Mike Moore
Accessibility Coordinator
Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
(512) 574-0091 (Cell)
From: Lynn Holdsworth
Date: Thu, Jun 11 2015 7:40AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
No Mike, I'm sure they didn't mean it to look like that. But
unfortunately my audit ccan only flag up WCAG2 failures.
Cheers, Lynn
On 11/06/2015, Moore,Michael (HHSC) < = EMAIL ADDRESS REMOVED = > wrote:
> I would think that it would fail to meet the design specifications. I can't
> imagine that the designer meant for it to look like that.
>
> Mike Moore
> Accessibility Coordinator
> Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
> (512) 574-0091 (Cell)
>
>
From: Moore,Michael (HHSC)
Date: Thu, Jun 11 2015 7:51AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
When I conduct audits, I usually add a section that covers any functional, organizational, usability, or design issues that I find problematic. I frequently find this to be a good place to mention things like button or form field placement that adversely impact people using screen magnification but do not fit neatly into the standards. I make it clear that these items are not required by the standards.
Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)
(512) 574-0091 (Cell)
From: Lynn Holdsworth
Date: Thu, Jun 11 2015 8:20AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | Next message →
Thanks Mike. I've got a recommendations list that's getting longer by
the hour. Ideally I'd have like to find ways to fail some of these
issues so they had to be foxed, but life's not like that.
Thanks again, Lynn
On 11/06/2015, Moore,Michael (HHSC) < = EMAIL ADDRESS REMOVED = > wrote:
> When I conduct audits, I usually add a section that covers any functional,
> organizational, usability, or design issues that I find problematic. I
> frequently find this to be a good place to mention things like button or
> form field placement that adversely impact people using screen magnification
> but do not fit neatly into the standards. I make it clear that these items
> are not required by the standards.
>
> Mike Moore
> Accessibility Coordinator
> Texas Health and Human Services Commission
> Civil Rights Office
> (512) 438-3431 (Office)
> (512) 574-0091 (Cell)
>
>
>
From: _mallory
Date: Thu, Jun 11 2015 9:13AM
Subject: Re: Where does CSS issue fail WCAG2?
← Previous message | No next message
On Thu, Jun 11, 2015 at 03:20:47PM +0100, Lynn Holdsworth wrote:
> Thanks Mike. I've got a recommendations list that's getting longer by
> the hour. Ideally I'd have like to find ways to fail some of these
> issues so they had to be foxed, but life's not like that.
Wheer I work, the only thing anyone cares about are the one-off
pixels, and they're always super-urgent-priority. Interesting to
see a place where that's not the case.
cheers,
_mallory