WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Titles for iframes

for

From: Sailesh Panchang
Date: Feb 19, 2015 1:35PM

Jon,
Sure that has been the behavior for several versions. My statement
was a response to the prior email that seemed to suggest otherwise.
Sailesh




On 2/19/15, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> I noticed JAWS does read the title for the iframe (recaptcha) both In FF
>> and IE.
>
> In my experience JAWS 16 will read the frame document's title element in IE
> if it exists. If it does not exist it will use the title attribute on the
> iFrame. In Firefox it will use the title attribute of the iFrame. This
> behavior has been like this for several versions.
>
> 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 Sailesh Panchang
> Sent: Wednesday, February 18, 2015 12:34 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Titles for iframes
>
> While looking at an example of no-CAPTCHA on
> https://wordpress.org/support/register.php
> I noticed JAWS does read the title for the iframe (recaptcha) both In FF
> and IE.
> NVDA also reads this title.
> In addition, JAWS detects the title as part of advanced element info for the
> Twitter and FB iframes as well and reads them:
> title=Twitter Follow Button
> title=Facebook
>
> Sailesh
>
>
> On 2/11/15, Paul Bohman < <EMAIL REMOVED> > wrote:
>> One thing also worth noting: JAWS does not read the iframe's title
>> attribute at all. Instead, it reads the <title> element of the
>> included page. That's not what screen readers are "supposed to" do,
>> but that's what JAWS does, and it sort of makes sense, but the problem
>> with that approach is that you have no control over the iframe title
>> when you're including third party content.
>>
>>
>> Paul Bohman, PhD
>> Director of Training
>> Deque Systems, Inc
>> www.deque.com
>> 703-225-0380, ext.121
>>
>> On Wed, Feb 11, 2015 at 2:07 PM, Brooks Newton
>> < <EMAIL REMOVED> >
>> wrote:
>>
>>> Hi All,
>>>
>>> For iframes with content that isn't intended for consumption by any
>>> user, such as iframes that hold third-party tracking tags, how about
>>> using the
>>> HTML5 hidden attribute and / or the CSS display:none declaration?
>>> Doesn't
>>> using aria-hidden="true" on the iframe element also make sense in
>>> this case? Seems to me that the semantic relevance of setting
>>> role="presentation" belies the page author's intended purpose -
>>> especially when you consider the specific context of the tracking tag
>>> iframe example I brought up... which is that no page user is supposed
>>> to know the hidden iframe content exists on the page. What are
>>> others thoughts?
>>>
>>> Credit to one of Steve's past posts for discussing the use of the
>>> three aforementioned techniques for hiding content from AT users
>>> -
>>> http://www.paciellogroup.com/blog/2012/05/html5-accessibility-chops-h
>>> idden-and-aria-hidden/
>>>
>>> Brooks Newton
>>>
>>> -----Original Message-----
>>> From: Steve Faulkner [mailto: <EMAIL REMOVED> ]
>>> Sent: Tuesday, February 10, 2015 12:43 PM
>>> To: WebAIM Discussion List
>>> Subject: Re: [WebAIM] Titles for iframes
>>>
>>> On 10 February 2015 at 17:41, Jared Smith < <EMAIL REMOVED> > wrote:
>>>
>>> > 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.
>>> >
>>>
>>> I this case role="presentation" could be used to remove the semantics
>>> of the frame, need to check AT support.
>>>
>>> I wrote an article about hidden iframes that may be helpful
>>> http://www.paciellogroup.com/blog/2010/04/making-sure-hidden-frames-a
>>> re-hidden/
>>> though probably needs an update :-)
>>>
>>> --
>>>
>>> Regards
>>>
>>> SteveF
>>> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;
>>>
>>>
>>> >>> >>> list messages to <EMAIL REMOVED>
>>>
>> >> >> list messages to <EMAIL REMOVED>
>>
> > > messages to <EMAIL REMOVED>
> > > >