E-mail List Archives

Re: iframes


From: L Snider
Date: Apr 24, 2017 7:53AM

I was doing some research on this a while back and found this source. It
looks like older versions of NVDA may have issues?



On Mon, Apr 24, 2017 at 8:43 AM, JP Jamous < <EMAIL REMOVED> > wrote:

> Just be careful with the page title of the loading page inside the iframe.
> The page is best having <title></title> and <html lang="en-us"> to avoid
> issues with screen readers and automated tools such as WAVE and Axe.
> The iframe should always have <iframe title="Google Ad"> so screen readers
> announce the type of iframe. If the title attribute is missing the screen
> reader would read the page title that is loaded in the iframe.
> Those simple tricks and proper semantic will keep the flow proper with a
> great UX.
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Corrine Schoeb
> Sent: Monday, April 24, 2017 8:21 AM
> Subject: [WebAIM] iframes
> We may need to use iframes for calendar data coming from a third party and
> wondering about the accessibility of iframes and their content.
> http://davidmacd.com/blog/is-title-attribute-on-iframe-
> required-by-wcag.html
> seems indicates there may be issues with iframes generally and especially
> when they don't have titles, particularly for VoiceOver
> http://webaim.org/techniques/frames/#iframe seems to indicate adding a
> title is all one needs to do to make them friendly for screen readers.
> Seems clear adding a title attribute is going to help, but is there more
> that we should be aware of and plan on doing?
> --
> Corrine Schoeb
> Technology Accessibility Coordinator, ITS
> 610-957-6208
> *** Swarthmore College ITS will never ask you for your password, including
> by email. Please keep your passwords private to protect yourself and the
> security of our network.
> > > at http://webaim.org/discussion/archives
> >
> > > > >