WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: iframes

for

From: L Snider
Date: Apr 24, 2017 8:36AM

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 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 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.
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of L Snider
>> Sent: Monday, April 24, 2017 8:54 AM
>> To: WebAIM Discussion List < <EMAIL REMOVED> >
>> Subject: Re: [WebAIM] iframes
>>
>> 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 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
>> > To: <EMAIL REMOVED>
>> > 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.
>> > >> > >> > archives at http://webaim.org/discussion/archives
>> > >> >
>> > >> > >> > archives at http://webaim.org/discussion/archives
>> > >> >
>> >> >> at http://webaim.org/discussion/archives
>> >>
>> >> >> >> >>
>
>