E-mail List Archives
Thread: iframes
Number of posts in this thread: 9 (In chronological order)
From: Corrine Schoeb
Date: Mon, Apr 24 2017 7:20AM
Subject: iframes
No previous message | Next message →
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.
From: JP Jamous
Date: Mon, Apr 24 2017 7:43AM
Subject: Re: iframes
← Previous message | Next message →
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.
From: L Snider
Date: Mon, Apr 24 2017 7:53AM
Subject: Re: iframes
← Previous message | Next message →
I was doing some research on this a while back and found this source. It
looks like older versions of NVDA may have issues?
https://www.powermapper.com/tests/screen-readers/labelling/iframe-title/
Cheers
Lisa
On Mon, Apr 24, 2017 at 8:43 AM, JP Jamous < = EMAIL ADDRESS 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.
>
>
From: JP Jamous
Date: Mon, Apr 24 2017 8:30AM
Subject: Re: iframes
← Previous message | Next message →
1. Why worry about older versions of NVDA since it is an open source?
2. Analytical tests are good, but each version of a SR and BR introduce new functionalities and deprecate other ones. It is always advisable to test in your target BR/SR to ensure the combination works for your audience.
I hear people always talking about trends and best practices. While those help. I always test the version of SR again the version of BR to ensure the 2 provide a smoother user experience. I like to look at this concept like the human body concept. While female bodies function alike, each body is different. The same apply to men. Too many factors impact the categorization such as DNA, age, medical history, etc.
Keep an overall eye on the big picture, but never lose focus of the detailed picture. That is each agent alongside its counter-part.
From: Thomas Lee McKeithan II
Date: Mon, Apr 24 2017 8:34AM
Subject: Re: iframes
← Previous message | Next message →
I concur JP.
Respectfully,
Thomas Lee McKeithan II | Optum Technology Solutions
Electronic Accessibility Engineer, UX Design Studio (UXDS)
MD018, 6220 Old Dobbin Lane, Columbia, MD, 21045, USA
T +1 443-896-0432
M +1 202-276-6437
= EMAIL ADDRESS REMOVED =
www.optum.com
ÂÂ
From: L Snider
Date: Mon, Apr 24 2017 8:35AM
Subject: Re: iframes
← Previous message | Next message →
I find many people use the older versions, even though they could easily
update (JAWS is even worse that way due to cost). In my experience, they
usually don't update due to the computer issues, computer knowledge or they
just like that version. Like any other software, not all are using the
latest.
I wish we could code for every single version, boy wouldn't that be nice
and make our lives so much easier!
Cheers
Lisa
On Mon, Apr 24, 2017 at 9:30 AM, JP Jamous < = EMAIL ADDRESS REMOVED = > wrote:
> 1. Why worry about older versions of NVDA since it is an open source?
> 2. Analytical tests are good, but each version of a SR and BR introduce
> new functionalities and deprecate other ones. It is always advisable to
> test in your target BR/SR to ensure the combination works for your audience.
>
>
> I hear people always talking about trends and best practices. While those
> help. I always test the version of SR again the version of BR to ensure the
> 2 provide a smoother user experience. I like to look at this concept like
> the human body concept. While female bodies function alike, each body is
> different. The same apply to men. Too many factors impact the
> categorization such as DNA, age, medical history, etc.
>
> Keep an overall eye on the big picture, but never lose focus of the
> detailed picture. That is each agent alongside its counter-part.
>
From: L Snider
Date: Mon, Apr 24 2017 8:36AM
Subject: Re: iframes
← Previous message | Next message →
Oh and I know exactly what you are saying in terms of the general versus
the specific. However, when I have locals using older versions for the most
part, then I have to know these things.
Cheers
Lisa
On Mon, Apr 24, 2017 at 9:35 AM, L Snider < = EMAIL ADDRESS REMOVED = > wrote:
> I find many people use the older versions, even though they could easily
> update (JAWS is even worse that way due to cost). In my experience, they
> usually don't update due to the computer issues, computer knowledge or they
> just like that version. Like any other software, not all are using the
> latest.
>
> I wish we could code for every single version, boy wouldn't that be nice
> and make our lives so much easier!
>
> Cheers
>
> Lisa
>
> On Mon, Apr 24, 2017 at 9:30 AM, JP Jamous < = EMAIL ADDRESS REMOVED = > wrote:
>
>> 1. Why worry about older versions of NVDA since it is an open source?
>> 2. Analytical tests are good, but each version of a SR and BR introduce
>> new functionalities and deprecate other ones. It is always advisable to
>> test in your target BR/SR to ensure the combination works for your audience.
>>
>>
>> I hear people always talking about trends and best practices. While those
>> help. I always test the version of SR again the version of BR to ensure the
>> 2 provide a smoother user experience. I like to look at this concept like
>> the human body concept. While female bodies function alike, each body is
>> different. The same apply to men. Too many factors impact the
>> categorization such as DNA, age, medical history, etc.
>>
>> Keep an overall eye on the big picture, but never lose focus of the
>> detailed picture. That is each agent alongside its counter-part.
>>
From: JP Jamous
Date: Tue, Apr 25 2017 6:26AM
Subject: Re: iframes
← Previous message | Next message →
Glad you do Thomas. That makes us a great team. Thumbs up. *Smiles*
From: Birkir R. Gunnarsson
Date: Tue, Apr 25 2017 7:05AM
Subject: Re: iframes
← Previous message | No next message
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 ADDRESS REMOVED = > wrote:
> Glad you do Thomas. That makes us a great team. Thumbs up. *Smiles*
>
>