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.
> >
> >