Re: LYNX-DEV numbered linx: 2 suggestions

[Philip Webb]

> On Thu, 9 Jan 1997, Philip Webb wrote:
> > someone suggested it mt be a problem for the blind: wd it?
> 
> no, not in any wise (although it did take me a couple of listens to figure
> out exactly what it was you were asking--abbreviations, like emoticons, do
> not work well with speech synthesis)
-- heartfelt apologies: i will try to remember in future when posting here
   that blind participants will have a problem with my customary abbreviations
-- i'm interested -- and believe others on the list might like to know too --
   whether your synthesiser can handle the well-known difficulties
   of English spelling: does it put together 26 sounds or does it read words?
   does it say  quote unquote  when it sees quotation marks?
   does it know standard abbreviations like E T C for etcetera?  etcetera.
   i ask because i'm sure most of us are interested in such technology
   and it will certainly make it easier for everyone to discuss solutions.
> are you suggesting that individual form elements be numbered (i.e. each
> checkbox, radio button, submit/reset button) and that one would be able to
> move the cursor/activate the choice associated with that number by typing
> it in?  this might be a great aid to blind persons attempting to fill out
> visually oriented forms (i.e. those which contain several options on a
> single line)
-- i hadn't thought of radio buttons: ms eaves simply echoed my own thoughts.
   it certainly wouldn't hurt users of numbered links to have more of them,
   even if they didn't need the device themselves.  it might not be difficult
   to add it as a 3rd option, i e LINKS_AND_FORMS_ARE_NUMBERED , in  lynx.cfg .
> i still favor the idea of a compile-time switch and/or (but prefereably
> and) a lynx.cfg file option that allows the speech user to force lynx to
> display checkboxes, radio buttons, and the like on single lines, much like
> the multiple-select option to checkbox feature...
-- this would be covered by the 3rd option above. 
> > i suspect there is some idea out there that numbering links is for novices,
> > so that these small improvements have been overlooked.
> i don't think this is a common conception at all--i know a large number of
> sighted "power users" who use numbered links...
-- in that case, there might be quite strong support for these suggestions.
-- can we please have a response from the code-writers?
   they keep complaining that people don't become familiar with the source,
   so here's an opportunity to point those of us who know some C
   and would like to start to learn how Lynx works
   towards some simple bits of its workings. 
> gregory.
> ---------------------------------------------------------------------------
>                  half-assed access isn't equal access...
> ---------------------------------------------------------------------------
> 
-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;