E-mail List Archives
Re: Wave alert: Very small text
From: glen walker
Date: Aug 4, 2020 8:35AM
- Next message: Jim Homme: "Looking To Interview Blind Or Visually Impaired Python Developers"
- Previous message: Chikodinaka mr. Oguledo: "Re: Wave alert: Very small text"
- Next message in Thread: None
- Previous message in Thread: Chikodinaka mr. Oguledo: "Re: Wave alert: Very small text"
- View all messages in this Thread
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 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.
>
>
- Next message: Jim Homme: "Looking To Interview Blind Or Visually Impaired Python Developers"
- Previous message: Chikodinaka mr. Oguledo: "Re: Wave alert: Very small text"
- Next message in Thread: None
- Previous message in Thread: Chikodinaka mr. Oguledo: "Re: Wave alert: Very small text"
- View all messages in this Thread