WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Iframes: minimum spec

for

From: Isabel Holdsworth
Date: May 29, 2019 8:54AM

Hi Birkir,

Great suggestion. I tried this one myself a while back but it didn't
work. The iframe was still exposed to JAWS, possibly due to security
considerations.

Thanks, Isabel

On 29/05/2019, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
> You could put role="presentation" on the <iframe> element (to
> basically hide it from the user). If the user is not supposed to
> perceive the iframe as a section of content that is separate from the
> page this is probably the best strategy. You should remove the title
> attribute from the <iframe> element if you do this, probably also the
> <title> element as well. The heading is good enough if the user is not
> supposed to perceive the iframe as a separate section.
>
>
>
> On 5/29/19, Isabel Holdsworth < <EMAIL REMOVED> > wrote:
>> Hi all,
>>
>> We're required to deliver some of our content within an iframe - this
>> is unfortunately not negotiable.
>>
>> The iframe has a title attribute, and its document has a <title> tag
>> and an h1 heading that all have the same (sometimes long) text, and
>> it's very laborious for screenreader users to keep listening to.
>> Younger users also find it very confusing.
>>
>> If the iframe didn't have a title attribute, or if its document didn't
>> have a <title> attribute, would it fail WCAG? The content delivered
>> inside the iframe is never displayed as a stand-alone page.
>>
>> Thanks as always, Isabel
>> >> >> >> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > > >