WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility training and scanning solutions providers

for

From: Birkir R. Gunnarsson
Date: Dec 17, 2016 1:51PM

I don´t like checkers that automatically flag use of ARIA as a failure
and stop checking. I see this in quite a few checkers.
The checkers need to understand ARIA and check if ARIA is being used
according to spec (because correctly used ARIA can imporve the user
experience, and it is a fully valid coding technique according to a
W3C standard).

I am fine with checkers flagging a warning that HTML has an element
that can do the same, but it shouldn´t be flagged as an error.


On 12/17/16, JP Jamous < <EMAIL REMOVED> > wrote:
> I second Birkir on this one. I deal on daily bases with old code dated back
> to 2005.
>
> I butt heads with UX teams because they get their analytics and they have
> zero information about people with ATs. That is why I trying to make changes
> to ensure we have the best user experience on our site.
>
> Being a software and web developer in the past, I don't rely much on
> automated checkers. I want to test drive that sucker myself and get the user
> experience. Even iOS and Android emulators I try to stay away from. I want
> the actual device and I want to be on a fully opened network rather behind a
> proxy firewall.
>
> All of the above, I learned that they can block what the customer
> experiences during a session. I want to be in that person's shoe despite the
> disability and get a feel for what is happening. I then do the automated
> checking.
>
> I know I am weird, but I want to achieve 2 things.
>
> 1. Is the site providing an accessible and positive user experience?
> 2. How can I prioritize my work and establish proper documentations for
> developers based on what I am experiencing so they can remedy the issues.
>
> If I am still getting some issues in the automated checker but the
> performance is excellent, then move on JP. That's how I like to approach
> those tasks. Relying on a program to make sense out of a pot of old, new and
> sloppy coding can frustrate the best decision maker. Of course, the checker
> will fail too many things.
>
>