- From: Charles McCathieNevile <charles@w3.org>
- Date: Fri, 16 Jul 1999 13:51:56 -0400 (EDT)
- To: Wendy A Chisholm <chisholm@trace.wisc.edu>
- cc: Harvey Bingham <hbingham@acm.org>, w3c-wai-eo@w3.org
NOFRAMES is a fundamental requirement of the frameset DTD. It is not legacy, it is the correct way to provide access to the content of frames for non spatially based browsers, in the same way the the correct way to provide a full description of an image using the IMG element is to add a URI as a longdesc. It just so happens that there are emergency repair strategies for framesets, although in most cases they provide a poor form of access at best. This means that Noframes is not necessarily a P1 requirement for accessibility on desktop machines (it probably is on mobile machines at the moment), but does not mean it it is unnecssary. Second-class access is appropriate for second-class people, but there are none of those. Charles McCN On Fri, 16 Jul 1999, Wendy A Chisholm wrote: >>>PROPOSAL: "Frames. Label with the _title_ or _name_ attribute." >>>OR PROPOSAL: "Frames. Use _noframe_, and _title_ or _name_ attribute. (NB: >>>"noframe" would be in small caps) >>> >>WC:: I like the second proposal. This technique is included in checkpoint >>6.5, which is P2. > >HB: Even if it is only in the transitional DTD. Are we continuing that >legacy? > there are several things in the WCAG that are "legacy" caused by the widespread use of older user agents or lack of support for newer features. therefore, "until user agents" seems to apply here. --wendy wendy chisholm human factors engineer trace research and development center university of wisconsin - madison, USA --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://www.w3.org/People/Charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Friday, 16 July 1999 13:52:00 UTC