What an interesting comment about authors of accessibility bides for
software developers.
May I see a reference supporting this stance from the w3c web access
initiative?
www.w3c.org
Keyboard function has been a basic requirement of web access guidelines
for decades.
and, no, this had nothing to do with a prior thread.
instead, the comment came from a Linux users group member who, while not
using adaptive technology at all, uses the CLI in Linux quite extensively.
Graphical clutter is not enjoyed, no idea if the article is swill on the
wired magazine website, but there was one with the title, "I turned off
JavaScript for a week, and it was glorious!"
that items work with the enter key and arrow keys, even with JavaScript is
basic.
progressive enhancement web design should be for developers too.
Kare
On Sat, 13 Jun 2026, Max Nikulin wrote:
On 11/06/2026 8:48 pm, Karen Lewellen wrote:
and again, I am not seeking an audio reader.
My impression is that those, who write accessibility guides for web
developers, are not aware of your trouble.
If this thread is indirectly related to
question about debian software development? Tue, 23 Sep 2025 17:46:12 -0400
(EDT)
<https://lists.debian.org/msgid-search/[email protected]>
the company removed direct access to google search for many lower
graphics and open source browsers. Tools like Links, and elinks, both of
which employ some JavaScript.
then you might ask some of your friends to evaluate reputation of
<https://chawan.net/> and to provide access to server where this browser is
installed.
In general, I believe that most of sites should be usable with text browsers.
However my expectation is that screen readers having access to full DOM tree
and a11y attributes should work better than text browsers even if terminal
supports escape sequences to mark some objects (e.g. as URLs).
