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

RE: accessible forms

From: Chris O'Kennon <chris@vipnet.org>
Date: Fri, 21 Jun 2002 15:12:06 -0400
Message-ID: <BCECCA7B3D37D611ABC5009027D6228A0403C4@iexch1.vipnet.org>
To: "'jonathan chetwynd'" <j.chetwynd@btinternet.com>, "Chris O'Kennon" <chris@vipnet.org>, w3c-wai-gl@w3.org

Is the problem, then, one of available technology?  Is there no way to code
for an "escape" from a menu?  And, if someone uses a 200 item menu, will
they still conform to the guidelines, or is there a "You did something too
annoying to conform" clause?

Chris O'Kennon
Commonwealth of Virginia Webmaster/
VIPNet Portal Architect
www.myvirginia.org  
______________________________________
"Until you have the courage to lose sight of the shore,
you will never know the terror of being forever lost at sea."


> -----Original Message-----
> From: jonathan chetwynd [mailto:j.chetwynd@btinternet.com]
> Sent: Friday, June 21, 2002 2:46 PM
> To: Chris O'Kennon; w3c-wai-gl@w3.org
> Subject: Re: accessible forms
> 
> 
> i've already suggested on many occassions that ~10 links is enough per
> page(or form in this case) if one is going to run to 
> hundreds, then one
> certainly needs to design a way to break them up.
> 
> w3 uses something in the navigation at the start of a page 
> that allows one
> to jump across links, perhaps it could include a warning, ie 
> 200 links.
> also one really wants an escape key.
> 
> visual navigation needs a different design criterion to auditory.
> for instance at http://www.peepo.com i've arranged for the 
> 'frame' content
> which is on every page (ie the alphabet) to frame the pages 
> visually, but to
> be read last.
> 
> in the interim, i'd recommend arranging for these long lists 
> to be at the
> end of the page
> 
> 
> ----- Original Message -----
> From: "Chris O'Kennon" <chris@vipnet.org>
> To: <w3c-wai-gl@w3.org>
> Cc: <j.chetwynd@btinternet.com>
> Sent: Friday, June 21, 2002 7:15 PM
> Subject: accessible forms
> 
> 
> >
> > I read the client-side scripting draft [1] and the html 
> techniques for
> wcag
> > 1.0 [2].  I don't see anything about coding drop-down menus 
> so a user can
> > move from the menu to the next form field without having to 
> tab through
> > everything else in the menu.  For example, the Virginia Commonwealth
> > Calendar [3] has several drop-down menus needed to access 
> the government
> > meetings.  In order to select an agency, a screen reader 
> would then have
> to
> > go through the rest of the options before the user could go 
> to the next
> form
> > field.  Although this allows the application to be 
> technically used, the
> > difficulty in going through 200 agencies makes it effectively
> inaccessible.
> >
> > Could this be addressed in a future draft of the 
> client-side scripting
> > techniques?  Or is it already there and I just missed it?
> >
> > [1] http://www.learningdifficulty.org/develop/w3c-scripts.html
> > [2] http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20000920/
> > [3] http://www.vipnet.org/portal/cgi-bin/calendar.cgi
> >
> > Chris O'Kennon
> > Commonwealth of Virginia Webmaster/
> > VIPNet Portal Architect
> > www.myvirginia.org
> >
> > ______________________________________
> > "Until you have the courage to lose sight of the shore,
> > you will never know the terror of being forever lost at sea."
> >
> >
> >
> >
> >
> 
> 
Received on Friday, 21 June 2002 15:12:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:19 GMT