WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Titles for iframes

for

From: Jonathan Avila
Date: Feb 19, 2015 9:11AM


> If a non-functional iFrame were given a role of "presentation" would that hide its existence from screenreaders?

The role of presentation is meant to hide the semantics of the element and any required descendant elements not hide the contents of the frame. So, while this might work for frames with no visible content aria-hidden might be a more appropriate attribute. Also iframes may be placed in the focus order by the browser so non-interactive frames may use tabindex=-1. However, be careful about applying tabindex=-1 to frames -- when a frame does contain interactive content applying this will prevent keyboard access into the interactive controls within the frame.

Jonathan

-- 
Jonathan Avila 
Chief Accessibility Officer
SSB BART Group 
<EMAIL REMOVED>
Phone 703.637.8957  
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Lynn Holdsworth
Sent: Wednesday, February 18, 2015 4:50 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Titles for iframes

If a non-functional iFrame were given a role of "presentation" would that hide its existence from screenreaders?



> On 10 Feb 2015, at 17:41, Jared Smith < <EMAIL REMOVED> > wrote:
>
> The purpose of the frame title is to convey the content or function of
> the frame as would be available to sighted users. It is required in
> WCAG under the alternative text for non-text elements success criteria
> - the idea being that the iframe is a non-text element.
>
> If the iframe has distinct content or a function, it should be
> conveyed via title. Examples might be that the iframe is an
> advertisement or the title of the movie for an embedded video player
> or, as in Paul's case, that it's a LinkedIn widget.
>
> However, sometimes iframes don't have a distinct visual purpose or
> function. Sometimes the fact an iframe is used in the markup is
> entirely transparent to sighted users. In these cases, adding a title
> to the iframe should not be required. Certainly WCAG doesn't require
> adding alternative text for something that is not a non-text element.
> Doing so would provide unnecessary and extraneous information just for
> screen reader users.
>
> Unfortunately, as Paul has described, many screen readers read extra
> stuff for iframes that do not have titles. This behavior is (I
> believe) incorrect, but is the reality. As such, a very concise
> descriptor of the iframe is likely the best alternative.
>
> Jared
> > > list messages to <EMAIL REMOVED>