WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Frames differ by browser

for

From: Beranek, Nicholas
Date: Jan 10, 2017 10:27PM

The framed content should inherit the language of the parent page. Partial conformance can be claimed since the content is served by a third party. See the following link for more details:

https://www.w3.org/TR/WCAG20/#conformance-partial

Nick



Sent with Good (www.good.com)
From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Rakesh P < <EMAIL REMOVED> >
Sent: Tuesday, January 10, 2017 8:18:20 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Frames differ by browser

That's an interesting observation and great solutions to resolve. Another
common problem I observed with iFrames when used <title></title> is the
language attribute. Considering iFrames as a separate page within the
parent page automation tools throw 3.1.1 Missing language attribute . I
really doubt how can the developers fix this when the iFrame content is
controlled by third party.

On Wed, Jan 11, 2017 at 3:20 AM, Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:

> 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
> > > >
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >
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.