WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Title attribute for iframes

for

From: Steve Green
Date: Sep 16, 2020 2:10AM

It's not that the client doesn't care. This is a contractual dispute over whether a developer built a website that is WCAG conformant.

Some people on this list only work in one context i.e. achieving the best level of accessibility they can for their employer. Others of us work in a variety of contexts. Sometimes a client wants us to help them achieve the highest possible level of accessibility. Other times we might be assessing a third party website on behalf of a client before they buy a system, in which case no remedial work will be possible - they just want to understand its conformance level. In this case we are acting as independent technical assessors to resolve a disagreement.

In some of these contexts the user experience and assistive technology behaviours are completely irrelevant. All that matters is whether a website conforms with what WCAG actually says, not what anyone thinks it should say. We have to put our personal opinions aside and base our decision on the facts, even if we don't like them.

The discussion that Patrick's email links to (https://github.com/w3c/wcag/issues/929) is interesting. With one exception, everyone is of the opinion that an<iframe> is not a "user interface component", which is also my view. The one dissenting view (http://www.davidmacd.com/blog/is-title-attribute-on-iframe-required-by-wcag.html) is a very poorly argued opinion that starts with the result he wants and works backwards to justify it.

Mallory's argument starts with the statement that <iframe> elements receive focus in some browsers. This raises the obvious question of whether they should. Is there a specification somewhere that mandates this? If not, you can't use it as the basis of a justification for making the "title" element mandatory. I could equally say that it doesn't receive focus in some other browser, so the "title" attribute is not needed. We need to dig deeper, but I am not sure where to look.

Steve


-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Mallory
Sent: 16 September 2020 08:37
To: Patrick H. Lauke < <EMAIL REMOVED> >; WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Title attribute for iframes

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.

cheers,
_mallory

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
> > > archives at http://webaim.org/discussion/archives
> >