On 1/30/24 06:22, Christian Schoepplein wrote:
On Mon, Jan 29, 2024 at 08:40:07AM -0700, Sam Hartman wrote:
Neils, I think what you are about to find is that individual preference
generally dominates accessibility concerns here.
Yes.
All what I wrote is the prefered way I like to work
On Mon, Jan 29, 2024 at 08:40:07AM -0700, Sam Hartman wrote:
>Neils, I think what you are about to find is that individual preference
>generally dominates accessibility concerns here.
Yes.
All what I wrote is the prefered way I like to work because it is the most
simplest way for me. This does
Niels Thykier (2024/01/29 14:50 +0100):
> Christian Schoepplein:
> > Hi Nils,
> >
> > [...]
> >
> > Piping output into a pager is very uncomfortable for screen reader users
> > IMHO. [...]
I'd like to say I do not have the same feeling on that one.
Seb.
Neils, I think what you are about to find is that individual preference
generally dominates accessibility concerns here.
> "Christian" == Christian Schoepplein writes:
Christian> Hi Nils,
Christian> On Sun, Jan 28, 2024 at 11:54:24AM +0100, Niels Thykier wrote:
>> In my case,
On 1/29/24 14:50, Niels Thykier wrote:
Christian Schoepplein:
Hi Nils,
[...]
Piping output into a pager is very uncomfortable for screen reader users
IMHO. [...]
Ciao,
Schoepp
Thanks for the hint, Schoepp.
This sounds like the screen reader optimized output mode should imply
Hi
Niels Thykier schrieb am 29.01.2024, 14:50 +0100:
>Christian Schoepplein:
>> Hi Nils,
>>
>> [...]
>>
>> Piping output into a pager is very uncomfortable for screen reader users
>> IMHO. [...]
>>
>> Ciao,
>>
>>Schoepp
>>
>
>Thanks for the hint, Schoepp.
Just as a second confirmation,
Christian Schoepplein:
Hi Nils,
[...]
Piping output into a pager is very uncomfortable for screen reader users
IMHO. [...]
Ciao,
Schoepp
Thanks for the hint, Schoepp.
This sounds like the screen reader optimized output mode should imply
disabling the automatic pager feature.
For
Hi Nils,
On Sun, Jan 28, 2024 at 11:54:24AM +0100, Niels Thykier wrote:
>In my case, my tool is not interactive. It generates text output and either
>emits all of it on standard out or pipes it to a pager. It is closer to a
>tool like ls than mutt in spirit. As far as I know, my tool cannot
On 1/28/24 22:09, Sébastien Hinderer wrote:
john doe (2024/01/28 21:33 +0100):
Generaly speaking, what is machine readable is screenreader friendly
(JSON/YAML).
To me, it's more importent to have an extensive documentation explaning
what a text file output contains than spending time on getting
john doe (2024/01/28 21:33 +0100):
> Generaly speaking, what is machine readable is screenreader friendly
> (JSON/YAML).
> To me, it's more importent to have an extensive documentation explaning
> what a text file output contains than spending time on getting the
> "correct" output.
I'd say it
On 1/27/24 22:18, Niels Thykier wrote:
Hi,
(Please CC on replies as I am not subscribed)
I am looking for advice on how to make the terminal more accessible.
The context is that I have a terminal program sub-commands. For some of
them, I currently render an ASCII table sometimes with
Just to add one thing:
Sébastien Hinderer (2024/01/28 12:10 +0100):
> At the very least, if you want to embelish your output, it would be nice
> if there is a mode where this embelishment can be disabled, either
> through a command-line option, an environemnt variable or a directive in
> a
Niels Thykier (2024/01/28 11:54 +0100):
> Thanks, I get what you mean now. :)
>
> In my case, my tool is not interactive. It generates text output and either
> emits all of it on standard out or pipes it to a pager. It is closer to a
> tool like ls than mutt in spirit. As far as I know, my tool
Samuel Thibault:
Niels Thykier, le sam. 27 janv. 2024 23:10:08 +0100, a ecrit:
Samuel Thibault:
One thing that is important for the screen reader to know what to render
is to put the caret on the item that matters.
I have trouble with this one. Can you provide an example that would work in
Hi,
To (try to) complete what Samuel has written...
Niels Thykier (2024/01/27 23:10 +0100):
> > One thing that is important for the screen reader to know what to render
> > is to put the caret on the item that matters.
>
> I have trouble with this one. Can you provide an example that would work
Niels Thykier, le sam. 27 janv. 2024 23:10:08 +0100, a ecrit:
> Samuel Thibault:
> > One thing that is important for the screen reader to know what to render
> > is to put the caret on the item that matters.
>
> I have trouble with this one. Can you provide an example that would work in
> the
Samuel Thibault:
Hello,
Giving a very small answer here.
Niels Thykier, le sam. 27 janv. 2024 22:18:23 +0100, a ecrit:
Like should the tool disable
ANSI color and boldface output to avoid creating confusing output?
Screen readers just ignore colors & bold/italic :)
Thanks. :)
One thing
Hello,
Giving a very small answer here.
Niels Thykier, le sam. 27 janv. 2024 22:18:23 +0100, a ecrit:
> Like should the tool disable
> ANSI color and boldface output to avoid creating confusing output?
Screen readers just ignore colors & bold/italic :)
One thing that is important for the
Hi,
(Please CC on replies as I am not subscribed)
I am looking for advice on how to make the terminal more accessible.
The context is that I have a terminal program sub-commands. For some of
them, I currently render an ASCII table sometimes with unstructured
notes following it as legends for
19 matches
Mail list logo
