WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Title attribute for iframes


From: Mallory
Date: Sep 16, 2020 1:37AM

I've taken the "interactive thingies need a name" as far as when we're forced to make an overflow area scrollable with a tabindex (unfortunately, only Firefox does this automatically). An example I run across consistently are chat widget windows. A sighted keyboarder needs to be able to scroll those to read them, and they may have zero focusables inside.

Taking the spirit of the idea that "if I can Tab and land on it, it should have a name" I'll suggest naming those if it's not possible to get rid of the overflow (scrollable areas suck).

Note that, unless it's changed, JAWS for me has always ignored iframe titles, and announced the name of the document inside (in the actual <title>). I do need to get an upgrade though.

If a client wants to say "that's not specifically required by the WCAG" that's up to them and I move on. The world is burning anyways.


On Tue, Sep 15, 2020, at 8:51 AM, Patrick H. Lauke wrote:
> Related to this, there's been some back and forth here
> https://github.com/w3c/wcag/issues/929 (as part of a wider discussion on
> whether or not a "name" needs to be unique/descriptive)
> P
> --
> Patrick H. Lauke
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >