W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2010

Re: one HTML WG chair's opinion on bug requiring @title for FRAME & IFRAME

From: Gregory J. Rosmaita <oedipus@hicom.net>
Date: Fri, 24 Sep 2010 18:19:08 +0100
To: w3c-wai-ua@w3.org
Message-Id: <20100924171654.M80692@hicom.net>
aloha!

i just wanted to remind y'all that as long as you create an account at 
the w3c bugzilla

http://www.w3.org/Bugs/Public/

and as long as the bugs you want to track are publicly tracked bugs
(which HTML5 is), you can comment on bugs logged there, such as that 
which i submitted on behalf of this WG requiring @title for FRAME 
and IFRAME -- so far, HTMLWG bug 10709 has received only negative 
feedback, building on the comment quoted in my original post...

gregory.

---- Original Emessage ------
From: Gregory J. Rosmaita <oedipus@hicom.net>
Date: Thu, 23 Sep 2010 20:13:54 +0100
To: w3c-wai-ua@w3.org
Message-Id: <20100923191215.M30579@hicom.net>

taken from http://www.w3.org/Bugs/Public/show_bug.cgi?id=10709

--- Comment #1 from Maciej Stachowiak <mjs@apple.com>  2010-09-23 19:07:14 ---

I'm not sure this is such a good idea. iframes in particular are often 
used as part of the UI of a page in a "transparent" way - there's some 
controls in it that are part of the tab cycle, but the user is generally 
not made aware of the fact that there even is a subframe. In such a case, 
it seems like there is no specific need to give a description of the 
iframe. As for the <frame> element (as opposed to <iframe>), it is not 
conforming in HTML5, so it doesn't make sense to have authoring 
Received on Friday, 24 September 2010 17:19:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:39 UTC