WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: why is title attribute necessary on iframes?

for

From: Angela French
Date: Dec 15, 2016 11:52AM

Our site uses embedded content from our Trumba calendar (basically a filtered view of our main calendar data) and it is in an iframe.
Here is an example: http://www.sbctc.edu/colleges-staff/commissions-councils/wactc/default.aspx. The content has a heading of "Calendar"./

Angela French

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of JP Jamous
Sent: Thursday, December 15, 2016 10:33 AM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] why is title attribute necessary on iframes?

What Lucy is referring to, here, is that screen readers capture,

1. Page title inside the frame and that might be some weird combination of letters developers used to identify the page 2. Screen readers might capture the source URL of the page being called thinking that they are trying to help the blind user

You may not need to include a title attribute in certain iframes. If you just ensure that the loading page has a clear title element that will suffice. The screen reader would read this.

Where you encounter this is in a dynamic environment where pages in the iframe are constantly changing like Ads. You are better off eliminating the title attribute and using the page title element.

That is why I always stress manual evaluation. Remember evaluation tools are programs and programs only know what they know. Besides that they are dumb.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Angela French
Sent: Thursday, December 15, 2016 12:06 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] why is title attribute necessary on iframes?

Thanks; I was thinking that most screen readers users don't configure the reader to read out title attributes.

Angela French

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Lucy Greco
Sent: Thursday, December 15, 2016 10:01 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] why is title attribute necessary on iframes?

also if you don't include it the thing the screenreader says is gibrish

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Thu, Dec 15, 2016 at 9:54 AM, Angela French < <EMAIL REMOVED> > wrote:

> Thanks JP, that makes sense now. I wasn't thinking of the crappy 3rd
> party stuff that comes in that no one wants to read! ;-)
>
> Angela French
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of JP Jamous
> Sent: Thursday, December 15, 2016 8:58 AM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] why is title attribute necessary on iframes?
>
> It provides a summarized caption of what the iframe includes. Think of
> it as a Title element on a page. Without it would you know what this
> page talks about?
>
> Why is that important? What if the iframe is a 3rd party add that I
> want to skip? I can hear the title and press the navigation key that
> would make me skip that iframe and go to something meaningful on the page.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Angela French
> Sent: Thursday, December 15, 2016 10:53 AM
> To: WebAim Forum ( <EMAIL REMOVED> ) <
> <EMAIL REMOVED> >
> Subject: [WebAIM] why is title attribute necessary on iframes?
>
> Can someone explain to me, please, what the title attribute does in an
> iframe for screen reader users? (Success Criteria 4.1.2) What is its
> importance in making an iframe accessible?
>
> Thank you,
>
>
> Angela French
> Internet/Intranet Specialist
> Washington State Board for Community and Technical Colleges
> 360-704-4316
> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
> www.sbctc.edu<;http://www.sbctc.edu/>;
>
> > > archives at http://webaim.org/discussion/archives
> >
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >