WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: IFRAME attribute question

for

Number of posts in this thread: 3 (In chronological order)

From: Weissenberger, Todd M
Date: Thu, Oct 16 2014 2:17PM
Subject: IFRAME attribute question
No previous message | Next message →

What's the word on using the same value for NAME and TITLE in an IFRAME element? Do the values need to be different?

Todd

T.M. Weissenberger
Web Accessibility Coordinator
University of Iowa
= EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
319-384-3323

From: Jukka K. Korpela
Date: Thu, Oct 16 2014 2:31PM
Subject: Re: IFRAME attribute question
← Previous message | Next message →

2014-10-16 23:17, Weissenberger, Todd M wrote:

> What's the word on using the same value for NAME and TITLE in an IFRAME element? Do the values need to be different?

There is no need for them to be different, and no need for them to be
the same. They have entirely different purposes and effects. The TITLE
attribute specifies an advisory title, which may be presented to the
user on request (e.g. on mouseover). The NAME attribute assigns a name
to the element, meant to be used in client-side scripting for accessing
a specific IFRAME element (not needed, since the ID attribute is more
adequate for that purpose) and for naming the "browsing context". In
practice, the NAME attribute mostly matters only in the role of naming
the inline frame so that TARGET attributes in links can use that name.

Thus, the TITLE attribute, if used, should contain some useful text for
the user, whereas the NAME attribute is an identifier and can be just
about anything as long as it is used consistently - it only matters to
people reading and editing the HTML code.

Yucca

From: Weissenberger, Todd M
Date: Fri, Oct 17 2014 12:11PM
Subject: Re: IFRAME attribute question
← Previous message | No next message

Thanks, Yucca.

This is what we thought--our CMS uses the same value for both fields, and we wanted to make double sure this didn't constitute an a11y deficit. We'll be sure to document the importance of this value for advisory purposes.

Best regards,
Todd