slack in Ubintu?

slack in Ubintu?

[blinux-list]

Thanks, I am not using Linux directly, but a service which is based on 
Ubuntu as a shell.
will pass this thread on and thank you  for several  prospects.
Kare



On Sun, 25 Sep 2022, Hendursaga wrote:

> Karen Lewellen <klewellen at shellworld.net> writes:
>
>> Anyone have first hand experience using the program in Linux generally, or a Ubuntu shell specifically?
>
> I generally just use the browser client, I'm afraid, but sclack[1] was the last TUI client I tested, though I doubt it's very screen-reader friendly, unfortunately. I've looked around and it appears irslackd[2] might be the best Slack API <-> IRC gateway around. There's also localslackirc[3], which is packaged in Debian and thus Ubuntu, though if the version packaged is a bit old you might want to compile from source.
>
>> I understand there used to be an IRC client, but that the company no longer provides the Authentication token used to run it.
>
> An IRC gateway, yes.
>
> ~ Hendursaga
>
> [1] https://github.com/haskellcamargo/sclack
> [2] https://github.com/adsr/irslackd
> [3] https://github.com/ltworf/localslackirc
>
>

slack in Ubintu?

[blinux-list]

Sebastian,
This is a profoundly intelligent question.
Interestingly enough the Web access initiative list, which discusses and 
tracks action around wCaG and other universal design policies talked about 
this recently.  Tied to a case in India.
One of the most unfortunate mistakes many many many people make is to 
start with the screen reader, when in fact what makes  things work is the 
design elements.
Progressive enhancement where one starts with a good old fashioned html 
floor, then incorporates  other  elements to which browsers created for 
those elements can draw upon, is the most inclusive path to screen reader 
function.
That is because  a screen reader, and there are scores of them across 
platforms  is basically at its best a talking monitor and keyboard. 
Speaks when  keys are struck, responds if an enter key is hit, reacts if 
the site in turn is coded to properly react to this first and foremost.
Web  Access content guidelines are technology certainly browser agnostic. 
Meaning they focus on Interaction, not tool..so you do not end up 
expecting a person  to be disabled according to a specific definition. 
Inclusion  is not about blindness or screen readers, and more than those 
experiencing sight loss benefit from, and use screen readers.
Instead of asking about screen reader tools, perhaps consider exploring 
progressive enhancement web design practices.  that way not only screen 
readers work, but voice browsers and augmented keyboards too.
Does that resonate?
Karen



On Sun, 25 Sep 2022, Sebastian LaVine wrote:

> On Sun Sep 25, 2022 at 1:29 PM EDT, Hendursaga wrote:
>> I generally just use the browser client, I'm afraid, but sclack[1] was the
>> last TUI client I tested, though I doubt it's very screen-reader friendly,
>> unfortunately.
>
> Do you happen to know of any resources on screen-reader friendliness for
> TUIs in general? Is there any particular way screen-readers know how to
> distinguish from actual text and "graphical" elements? Or a way that TUI
> program developers can accomodate that?
>
>

slack in Ubintu?

[blinux-list]

> Do you happen to know of any resources on screen-reader friendliness for
> TUIs in general? Is there any particular way screen-readers know how to
> distinguish from actual text and "graphical" elements? Or a way that TUI
> program developers can accomodate that?

Here comes a wall of pontification...

Not really.  As a rule, I avoid TUIs.  Interfaces that exploit the
cursor-addressable terminal seem like the worst of both the text and GUI
world to me.  Essentially, a TUI is just a GUI with a VT100 as the
canvas and typically no underlying object toolkit[1].  But don't let
that discourage you.

I use three types of interfaces.

1. Self-voicing.  I make heavy use of Emacs with the Emacspeak
extension.  Emacs can be a TUI or a GUI program, and with extensions
like Emacspeak and speechd.el, it can be a self-voicing program as
well.  Editing text is a great UI metaphor.

2. Teletype-style programs, either with their own interactive input
loops, or called directly from the shell.  Edbrowse is an example of the
former category.  The reddit client I use, reddio, is an example of the
latter.  There's an excellent opinion piece about teletype-style interaction
written by Karl Dahlke: <https://www.eklhad.net/philosophy.html>.

3. GUIs, when I must.

[1] As a thought experiment, we could imagine an object toolkit for the
terminal: a GTK or QT for the VT100, if you will.  It's been done
before, though I don't remember any citations off the top of my head.
In theory, such a toolkit could provide hooks for screenreaders, to give
a more seamless / less frustrating experience.  That hasn't been done,
and I don't know if it would be worth doing.

-- Chris

slack in Ubintu?

[blinux-list]

What Chris said... And sorry if that does not address the question, but let's
not forget the Linux console aka tty.

No graphical element, only actual text, so no such issue.

Didier

Le 25/09/2022 ? 20:10, Linux for blind general discussion a ?crit?:
>> Do you happen to know of any resources on screen-reader friendliness for
>> TUIs in general? Is there any particular way screen-readers know how to
>> distinguish from actual text and "graphical" elements? Or a way that TUI
>> program developers can accomodate that?
> 
> Here comes a wall of pontification...
> 
> Not really.  As a rule, I avoid TUIs.  Interfaces that exploit the
> cursor-addressable terminal seem like the worst of both the text and GUI
> world to me.  Essentially, a TUI is just a GUI with a VT100 as the
> canvas and typically no underlying object toolkit[1].  But don't let
> that discourage you.
> 
> I use three types of interfaces.
> 
> 1. Self-voicing.  I make heavy use of Emacs with the Emacspeak
> extension.  Emacs can be a TUI or a GUI program, and with extensions
> like Emacspeak and speechd.el, it can be a self-voicing program as
> well.  Editing text is a great UI metaphor.
> 
> 2. Teletype-style programs, either with their own interactive input
> loops, or called directly from the shell.  Edbrowse is an example of the
> former category.  The reddit client I use, reddio, is an example of the
> latter.  There's an excellent opinion piece about teletype-style interaction
> written by Karl Dahlke: <https://www.eklhad.net/philosophy.html>.
> 
> 3. GUIs, when I must.
> 
> [1] As a thought experiment, we could imagine an object toolkit for the
> terminal: a GTK or QT for the VT100, if you will.  It's been done
> before, though I don't remember any citations off the top of my head.
> In theory, such a toolkit could provide hooks for screenreaders, to give
> a more seamless / less frustrating experience.  That hasn't been done,
> and I don't know if it would be worth doing.
> 
> -- Chris

slack in Ubintu?

[blinux-list]

Hi folks,
I amend speaking of the Linux distribution, but the messaging and 
communication platform.
Anyone have first hand experience using the program in Linux generally, or 
a Ubuntu shell specifically?
I  understand there used to be an IRC client, but that the company no 
longer provides the Authentication token used to run it.
anyone have one of those?
Thanks very much,
Karen