E-mail List Archives
Thread: Wave alert: Very small text
Number of posts in this thread: 6 (In chronological order)
From: Vaibhav Saraf
Date: Tue, Aug 04 2020 7:17AM
Subject: Wave alert: Very small text
No previous message | Next message →
Hi Everyone,
I encountered a new alert today, 'Very small text', the text is smaller
than 10 px.
Will one need to actually correct this as there is always an option to zoom
in, though I personally don't like doing that.
Also Wave didn't map it to a success criteria failure and I can't do it
too. How can we pursue developers to fix this as they will only take up
things related to SC failure?
Thanks,
Vaibhav
From: Steve Green
Date: Tue, Aug 04 2020 7:24AM
Subject: Re: Wave alert: Very small text
← Previous message | Next message →
If that's their attitude you can't, because it's not a WCAG non-conformance. However, it should not be the developer's decision (nor yours), so take it up with the product owner of some other stakeholder who might care about it. If you can't get support at that level, leave it and fight the battles you can win.
Steve Green
Managing Director
Test Partners Ltd
From: glen walker
Date: Tue, Aug 04 2020 7:43AM
Subject: Re: Wave alert: Very small text
← Previous message | Next message →
Sounds like you might need a refresher on WCAG and how accessibility tools
work. There are a lot of tools out there. Some try to report only WCAG
failures, some report "suspicious" code that requires a manual inspection,
and others include "best practices" failures. For those that only report
WCAG failures, the tool often misses a lot of failures because oftentimes
there's not a programmatic way to guarantee it's a failure. There are CSS
and JS and HTML tricks you can do that might fool a scanning tool so rather
than risk reporting a false positive, it doesn't report the problem. For
tools that report suspicious code or best practice failures, if you inspect
the code and it's ok, the tool is still going to report it.
The main point is that you're trying to create an experience that is as
inclusive to everyone as possible. You're not trying to get a perfect
score from a tool.
As Steve said, fight the battles you can win.
From: Vaibhav Saraf
Date: Tue, Aug 04 2020 7:55AM
Subject: Re: Wave alert: Very small text
← Previous message | Next message →
Thanks Steve, your quick and to-the-point replies are always of great help!
On Tue, 4 Aug 2020 at 18:54, Steve Green < = EMAIL ADDRESS REMOVED = >
wrote:
> If that's their attitude you can't, because it's not a WCAG
> non-conformance. However, it should not be the developer's decision (nor
> yours), so take it up with the product owner of some other stakeholder who
> might care about it. If you can't get support at that level, leave it and
> fight the battles you can win.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>
From: Chikodinaka mr. Oguledo
Date: Tue, Aug 04 2020 8:00AM
Subject: Re: Wave alert: Very small text
← Previous message | Next message →
wava
On 8/4/20, Vaibhav Saraf < = EMAIL ADDRESS REMOVED = > wrote:
> Thanks Steve, your quick and to-the-point replies are always of great help!
>
>
> On Tue, 4 Aug 2020 at 18:54, Steve Green < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> If that's their attitude you can't, because it's not a WCAG
>> non-conformance. However, it should not be the developer's decision (nor
>> yours), so take it up with the product owner of some other stakeholder
>> who
>> might care about it. If you can't get support at that level, leave it and
>> fight the battles you can win.
>>
>> Steve Green
>> Managing Director
>> Test Partners Ltd
>>
>>
>>
From: glen walker
Date: Tue, Aug 04 2020 8:35AM
Subject: Re: Wave alert: Very small text
← Previous message | No next message
Here's a rather timely article on the same subject:
https://equalentry.com/equal-entry-website-called-out-as-inaccessible/
On Tue, Aug 4, 2020 at 7:43 AM glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> Sounds like you might need a refresher on WCAG and how accessibility tools
> work. There are a lot of tools out there. Some try to report only WCAG
> failures, some report "suspicious" code that requires a manual inspection,
> and others include "best practices" failures. For those that only report
> WCAG failures, the tool often misses a lot of failures because oftentimes
> there's not a programmatic way to guarantee it's a failure. There are CSS
> and JS and HTML tricks you can do that might fool a scanning tool so rather
> than risk reporting a false positive, it doesn't report the problem. For
> tools that report suspicious code or best practice failures, if you inspect
> the code and it's ok, the tool is still going to report it.
>
> The main point is that you're trying to create an experience that is as
> inclusive to everyone as possible. You're not trying to get a perfect
> score from a tool.
>
> As Steve said, fight the battles you can win.
>
>