getting off my windows dependency

[Janina Sajka]

I'm afraid I don't understand your answer.

You're saying that the Windows screen readers handle browsers
differently. That part I understand. But, I wasn't asking about that.

I do think I do understand that you have a preference for output that is
rendered the same way as it would be without a screen reader. Well and
good. That may, or may not, be a valuable thing, depending on personal
choice, I expect.

But, haven't you configured your browser to provide you navigation in
the rendered content? I'm unaware that sighted users would have such a
requirement. I would rather expect they woudln't.

And, that takes me back to my first question: Isn't reviewing content
line by line, or word by word, or char by char, our requirement for
assistive technology, and not the browser? Seems to me it belongs with
AT, not browsers.

Farhan writes:
> well, look at it this way. with window eyes and jaws they put each link on one line each. with supernova it doesn't do that. see, it differs even in windows. with lynx and elynx you look at it from a sorta sighted perspective, with out the websites beeing all processed.
> on 4/4/2005 janina at rednote.netJanina Sajka
> said
> Why would browsing by line, word, or char be a browser feature? It seems
> to me such functionality is the responsibility of the assistive
> technology, not the browser.
> 
> Also, when you say "tab browsing," what does that mean? Is there some
> unique definition of tab browsing in elinks?
> 
> 
> Sergei V. Fleytin writes:
> > Hello, listers,
> > 
> > >>>>> "m" == mikster4  <mikster4 at msn.com> writes:
> > 
> > m> I was maening more that it is not how the web browser works itself,
> > m> it is something inserted by the screen reader. Normally you can't
> > m> cursor around the page in a web browser, only jump between the
> > m> controls. Maybe it is my mistake, but I thought the person was
> > m> expecting this behaviour to be in the web browser.
> > 
> > I'd like to make some comment concerning this topic. Both links2 and
> > elinks allow users to navigate within a page like in an editor. Links2
> > provide what they call "braille terminal" wich, in my opinion is a
> > very cool and convenient feature. Elinks also can be customize to
> > behave in similar fashion though it would not be as blind friendly as
> > braille terminal in links2. But elinks has so many cool features,
> > including tab browsing, that it really worth our attention. Below is a
> > fragment from my elinks.conf wich allow to move by characters and
> > lines within elinks using vi-like keybindings.
> > 
> > 
> > bind "main" "k" = "move-cursor-up"
> > bind "main" "l" = "move-cursor-right"
> > bind "main" "h" = "move-cursor-left"
> > bind "main" "j" = "move-cursor-down"
> > 
> > set ui.show_status_bar = 0
> > 
> > I hope it would be useful for someone.
> > 
> > 
> > -- 
> > With best regards, Sergei.
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> -- 
> 
> Janina Sajka				Phone: +1.202.494.7040
> Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com
> 
> Chair, Accessibility Workgroup		Free Standards Group (FSG)
> janina at freestandards.org		http://a11y.org
> 
> If Linux can't solve your computing problem, you need a different problem.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC	http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina at freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different problem.