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

Re: Site Review Request: MIT OpenCourseWare

From: B.K. DeLong <bkdelong@pobox.com>
Date: Wed, 27 Aug 2003 15:15:16 -0400
Message-Id: <5.1.0.14.2.20030827151201.0302eeb0@PO11.MIT.EDU>
To: Charles McCathieNevile <charles@sidar.org>
Cc: w3c-wai-ig@w3.org

At 04:42 AM 8/28/2003 +1000, Charles McCathieNevile wrote:
>1. Yes, look at accesskey but don't worry about tabindex unless you use 
>some weird and complex positioning stuff.

Great, thanks.

>2. Yes, you should group blocks of navigation links. Until browsers figure 
>out how to do this better (IE is the standout on the very useful link 
>element, and skipping navigation links without a nice structure and a 
>"skip to main content" link are still not mainstream unfortunately).

I meant in HTML....currently they're all "together" in that they're 
positioned in the same section. Is there anything other than a <div> that I 
should be using to designate them as a group?

>3. Yes, let people know. Add "pop-up", or "new window" or something to the 
>link text is my preference, but there is an argument to be made that 
>putting this in the title is "informing the user".

Well, if it was done in the title of a link, JAWS will read that title when 
it becomes active - right? That's the only user to whom notification of a 
new window would be quite important, in my opinion.

>Chaals (who hasn't had time to do a review yet :(

I appreciate you taking the time to at least answer my questions.

Thanks.



--
B.K. DeLong
Web Production Specialist
MIT OpenCourseWare

9-225

+1.617.324.6044
+1.617.797.2472 (cell)
bkdelong@mit.edu
http://ocw.mit.edu
Received on Wednesday, 27 August 2003 15:17:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:10 GMT