WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: iframes

for

From: Birkir R. Gunnarsson
Date: Apr 25, 2017 7:05AM

A title attribute on the iframe is all you should need (plus, of
course, ensuring that the content of the iframe is accessible).
Jaws prefers to use the <title> element inside the iframe to derive
its accessible name. I am not sure why, as WCAG 2.4.2 recommend use of
the title attribute.

Yes, there were issues with NVDA and navigation in and out of iframes
using the tab key (users could get around it by navigating into the
iframe with the arrow keys).
I think it is this issue which appears to be solved in NVDA version 2015.3
https://github.com/nvaccess/nvda/issues/5227

And, yes, we need to settle on a combination of browser/screen reader
to test with, we can't test for them all (nor should we).
See http://whoseline.a11yideas.com for more thoughts and examples.
There are reasons for upgrading that go beyond accessibility, e.g.
functionality and security.



On 4/25/17, JP Jamous < <EMAIL REMOVED> > wrote:
> Glad you do Thomas. That makes us a great team. Thumbs up. *Smiles*
>
>