WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Machine learning for accessibility tooling in Firefox

for

From: Mallory
Date: Jul 24, 2019 4:33AM

Unfortunately many of the bad patterns I see are sites I've audited and that can fall under an NDA. However they are very often using open libraries. For example I recently did a site using <hi-button> everywhere. Are links to libraries also useful for this survey?

Sometimes the libraries' own docs will explain how do to something in an accessible manner but clearly the developers using the library just copy and paste or feel they don't have time to read 300+ pages and so try to treat the docs like a cookbook. Would these libraries still be useful in the survey?

cheers,
Mallory

On Tue, Jul 23, 2019, at 9:50 PM, Léonie Watson via WebAIM-Forum wrote:
>
> On 23/07/2019 20:25, Asa Dotzler wrote:
> [...]
>
> > But identifying inaccessible custom elements is a challenge. The approach
> > we're investigating is to use machine learning, which requires many
> > examples. We would greatly appreciate your help in finding them, via this
> > survey
> >
> > https://docs.google.com/forms/d/e/1FAIpQLSfkZ_Hq4UKUtJDynbaZsSdfZEDx3Un9Z7M-MBN4ofy7vOvhlQ/viewform
>
> Has Mozilla considered grepping the web for class name "cow paths"? I'd
> wager that looking for things like "class="button", class="btn" and
> variants would turn up a huge amount of data to work with.
>
> If memory serves, this is one of the methods used to identify the cow
> paths that were later paved as the header, footer, navigation elements
> and such.
>
>
> Léonie.
>
>
>
> >
> > Thank you,
> > Asa Dotzler
> > > > > > > > > >
>
> --
> @TetraLogical TetraLogical.com
> > > > >