W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2004

Re: How to move the cursor from one Frame to another

From: Jesper Tverskov <jesper.tverskov@mail.tele.dk>
Date: Thu, 1 Apr 2004 08:50:13 +0200
To: <w3c-wai-ig@w3.org>
Message-ID: <000001c417b5$95ccc180$440bc650@tversdata>

Chaals wrote:

Actually, lots of things about frames are good - unfortunately there 
are a few architectural problems with them.


Let us not forget that frames are a disaster for ordinary keyboard
users. The pane you want to scroll gets out of focus all the time you
activate a menu item, and PageUp, PageDown, Home, End, and the arrow
keys are not working before you get focus back. Very confusing for most
keyboard users.

Let us not forget that frames make it almost impossible to make flexible
design that works well in many resolutions of the screen and sizes of
the browser window.

Let us not forget that frames has given us very many websites where all
pages have the same page title causing problems for bookmarking, and
when listed as links by search engines, etc., etc.

Let us not forget that frames are the main culprit for so many websites
printing garbage.

Let us not forget problems with broken frames, other web pages being
framed by frames of other web sites, etc.

Yes, frames have some advantages for blind users, making it possible to
identify sections of web pages consisting of many web pages. That is
exactly the reason why W3C has always regarded frames as undermining the
whole concept of hypertext and www being a web of pages with the page as
the basic unit. With frames we get a web of websites and pages and
fragments of pages also being pages. There are probably reasons why
frames have never obtained status as anything but deprecated.

WCAG 11.2 tells us to avoid deprecated features of W3C.

Best regards,
Jesper Tverskov
Received on Thursday, 1 April 2004 01:42:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:28 UTC