WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: most important ARIA

for

From: Bryan Garaventa
Date: Jan 4, 2019 1:22PM

Hi,
It's important to keep in mind that Visual ARIA is a teaching tool, not a testing tool. So if you try to break it, you will likely succeed.

When building it, I had to balance many different concepts, and ARIA not being simple is one of them. There are many rules and criteria, and including which ones had to be balanced by applying flexible low-overhead messages that would try to show up as well as possible within reason, and 100% success is an impossible goal post if this is what you expect to see on all pages.

The best environment for using Visual ARIA is within the development process, where people can experiment with ARIA usage in a controlled environment and then use the feedback from Visual ARIA while interacting with it to positively shape accessible widget construction in practice.

As an example, when building the accessible React integration project at
https://github.com/whatsock/bootstrap-react
I included Visual ARIA as an offline import that loads in a dormant state so it can be toggled on and off during development by those wishing to do exactly that.

The AccName computation is a work in progress, and this will be changing in the future as I edit the AccName spec to address issues raised in the 1.2 update for
http://www.w3.org/TR/accname-1.1/
So Visual ARIA will be updated accordingly as I do that, but even so, this is meant only as an approximation since the critical aspects of AccName are meant for the browser venders to implement at an algorithm level, and the act of rendering anything within a webpage changes the accessible names of those controls.

It's not possible to expect perfect tooltip rendering on all sites with Visual ARIA, because as part of balancing rules versus UI in creating it, it must borrow from the parent site to display using certain visual rules. Otherwise, individual class overrides would have to be created on everything to account for all possible CSS rule varients and that would inflate the code so much that it wouldn't be usable publically. At present there are over 150 thousand lines of code already. You are welcome to download the source code and check this out to see what I mean.

So even so, I still recommend that all sighted developers use Visual ARIA because it will significantly improve the output of those building interactive ARIA widgets for public consumption.

All the best,
Bryan



Bryan Garaventa
Principle Accessibility Architect
Level Access, Inc.
<EMAIL REMOVED>
415.624.2709 (o)
www.LevelAccess.com

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Steve Green
Sent: Wednesday, January 02, 2019 8:54 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] most important ARIA

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


I have just tried it with Chrome on a few websites and whilst it is useful, you can't always take the results at face value. For instance, one website contained a div element that contained two others that had aria-label attributes. No matter where I hovered the mouse, the Visual ARIA tooltip showed the accessible name as being the concatenation of the two aria-label attributes. Maybe this is the expected behaviour, but I expected to be able to see the accessible names for each div separately.

Another issue is that the tooltip for the accessible name is often very narrow so the accessible name wraps onto multiple lines and is mostly hidden behind the tooltip for the accessible description. It seems that the tooltip is constrained to the width of the container that the target element is in.

I have also just seen the accessible name wrap without going onto a new line, so it overwrites itself and is almost entirely unreadable. It looks like the text in the tooltips is using some of the styles from the target page, which does not seem to be a good idea.

Also, there are no tooltips when I hover over a native combobox, even if it has an accessible name. Is this expected?

All these issues and more can be seen if you use Visual ARIA on https://www.jackwills.com/sale-and-offers/ladies/sale-hoodies/. The accessibility of the entire website is terrible so it's a good one to use for evaluating accessibility testing tools.

Steve Green
Managing Director
Test Partners Ltd


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of greg jellin
Sent: 03 January 2019 04:11
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] most important ARIA

Radical, Bryan! This is the first I've heard of your tool. Excited to play with it tomorrow.

Greg

On Wed, Jan 2, 2019, 6:03 PM Bryan Garaventa < <EMAIL REMOVED> wrote:

> Hi,
> For sighted developers, I strongly recommend everybody use Visual
> ARIA, which is designed to help teach the use of ARIA to people of all
> experience levels during standard usage, education, development, and
> testing with hands on experience.
>
> https://www.linkedin.com/pulse/visual-aria-now-allows-anyone-sight-see
> -how-works-from-garaventa/
>
> This is also downloadable at
> https://github.com/accdc/visual-aria
>
> Included within the download is an ARIA 101 roadmap document for
> learning ARIA as comprehensively as possible starting with no experience in ARIA.
>
> Best wishes,
> Bryan
>
>
>
> Bryan Garaventa
> Principle Accessibility Architect
> Level Access, Inc.
> <EMAIL REMOVED>
> 415.624.2709 (o)
> www.LevelAccess.com
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> David Engebretson Jr
> Sent: Tuesday, January 01, 2019 2:13 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [WebAIM] most important ARIA
>
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you recognize the sender
> and know the content is safe.
>
>
> Happy new year all!
>
> I'm curious what you consider the most important ARIA to learn. Also,
> do you have reccomendations for novices to ARIA to learn effective
> techniques with those most important elements of ARIA?
>
> Personally, I am a novice with ARIA, but I enjoy its benefits everyday
> as a screen reader user. I use multiple screen readers (JAWS, NVDA,
> Voiceover) and would like to be able to teach my community of web
> developers how to best use ARIA.
>
> Where would you suggest I go to learn how to explain ARIA to
> developers who don't benefit from it everyday? Not all of the
> developers in my community experience the benefits and I want to be
> able to explain why it is important to implement it into their web page designs.
>
> Thanks so much,
> David
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >