WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Frames differ by browser

for

From: Jonathan Avila
Date: Jan 11, 2017 8:30AM

> Fact is that, according to the accessible name calculation native HTML labeling comes before title (in this case I guess it would be the <title> element inside the frame).

For the purposes of the iFrame -- it is my understanding the title element of the content document is not taken into account.

According to the HTML Accessibility API Mappings 1.0
https://www.w3.org/TR/html-aam-1.0/

5.13.1 iframe Element Accessible Name Computation

If the element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings 1.1.
Otherwise use the title attribute
If none of the above yield a usable text string there is no accessible name
NOTE
The document referenced by the src of the iframe element gets its name from that document's title element, like any other document. If there is no title provided, there is no accessible name.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703.637.8957 (Office)
Vis Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
See you at CSUN in March!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.


-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R. Gunnarsson
Sent: Tuesday, January 10, 2017 4:50 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Frames differ by browser

The WCAG 2.4.1 text and techniques all refer to using the title element on the frame.
FAct is that, according to the accessible name calculation native HTML labeling comes before title (in this case I guess it would be the <title> element inside the frame).
I agree, use aria-label to be safe (it beats out the native HTmL labeling and you usually have control over it).
If the title still doesn't come through, you can place the frame in a <div> with role="region" and aria-label="whatever the title should be".
That way you have provided the label or the frame, albeit in a roundabout way.


On 1/10/17, JP Jamous < <EMAIL REMOVED> > wrote:
> Thank you Nick. That is very helpful.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Beranek, Nicholas
> Sent: Tuesday, January 10, 2017 2:09 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Frames differ by browser
>
> It's a little tricky to find as it's embedded within the Windows SDK
> as Inspect32.exe. If you can find it, then it is a very powerful tool.
> I have done some basic testing with JAWS and it appears to be a simple
> Tree View with adjacent panel containing the accessibility information
> for the focused element.
>
> You could try aViewer instead as it presents you the same information
> and is readily available:
>
> https://www.paciellogroup.com/resources/aviewer/
>
> Nick
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of JP Jamous
> Sent: Tuesday, January 10, 2017 1:29 PM
> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Frames differ by browser
>
> 1. I assumed that she has control over the page inside the frame. If
> not, then the only solution I have been able to come up with was
> aria-label rather than the Iframe title. I don't like it, but thanks
> to the SR manufacturers, it solves the issue.
> 2. I have not had the chance to mess with the MSAA viewer. That is one
> of the things on my list. Is it accessible with JAWS?
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Beranek, Nicholas
> Sent: Tuesday, January 10, 2017 12:15 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Frames differ by browser
>
> What if you don't have direct control over the contents of the
> <iframe>? I think it's prudent to maintain both the <title> of the
> framed content as well as the title attribute on the <iframe>. Thoughts?
>
> As for the discrepancies between each browser, it's a possibility that
> they're calculating the accessible name for the frame differently.
> Have you ever used the MSAA Object Inspect tool to verify what is
> being calculated by the accessibility API?
>
> Nick
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of JP Jamous
> Sent: Tuesday, January 10, 2017 11:45 AM
> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Frames differ by browser
>
> Sharon,
>
> Try to remove the page title inside the frame.
> <Title></title>
>
> Use the iframe title to set what you want it to state. That should
> work with JAWS and Internet Explorer.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Sharon M Trerise
> Sent: Tuesday, January 10, 2017 10:05 AM
> To: ' <EMAIL REMOVED> ' < <EMAIL REMOVED> >
> Subject: [WebAIM] Frames differ by browser
>
> Can someone help me understand why the frame names appear to be
> different for different browsers? I'm looking at DegreeWorks and when
> I list the frames in JAWS (Insert F9) I get 3 different lists
> depending on which browser I am using: IE, Firefox or Chrome. I
> believe I am listing the frames from the same entry point in each browser.
>
> Thanks.
>
> Sharon
>
> Sharon Trerise | IT Analyst - Accessibility Information Technology
> Services
> 1-205 CST
> Syracuse University
> Syracuse, New York 13244
> t 315.443.2143 e <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > w
> its.syr.edu<http://its.syr.edu>; SYRACUSE UNIVERSITY
> syr.edu<http://syr.edu>;
>
> > > archives at http://webaim.org/discussion/archives
> >
> > > archives at http://webaim.org/discussion/archives
> > >
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The
> information transmitted herewith is intended only for use by the
> individual or entity to which it is addressed. If the reader of this
> message is not the intended recipient, you are hereby notified that
> any review, retransmission, dissemination, distribution, copying or
> other use of, or taking of any action in reliance upon this
> information is strictly prohibited. If you have received this
> communication in error, please contact the sender and delete the material from your computer.
> > > archives at http://webaim.org/discussion/archives
> >
> > > archives at http://webaim.org/discussion/archives
> > >
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The
> information transmitted herewith is intended only for use by the
> individual or entity to which it is addressed. If the reader of this
> message is not the intended recipient, you are hereby notified that
> any review, retransmission, dissemination, distribution, copying or
> other use of, or taking of any action in reliance upon this
> information is strictly prohibited. If you have received this
> communication in error, please contact the sender and delete the material from your computer.
> > > archives at http://webaim.org/discussion/archives
> >
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.