Slack accessibility status?
|
Thanks for the reply! Could I have George's
email address? On the web interface. It is reading and
navigating. Using NVDA and FireFox, focus often gets stuck when
navigating menus. Chat menus, and switching channels. I will
join the group below, thank you! In FF, Could a messages header
be added so that I don't accidentally skip the messages list? As
for the desktop app, nothing reads, at all. Absolutely nothing,
using NVDA. On windows 10. On 4/21/2018 2:09 AM, Bel (Slack)
wrote:
|
||
|
|
||
|
Sam Bushman
How well does slack work with latest nvda and the windows desktop app?
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Kingett
Sent: Saturday, April 21, 2018 9:30 AM To: Slack <feedback+id1733065@...> Subject: Re: [nvda] Slack accessibility status?
Thanks for the reply! Could I have George's email address? On the web interface. It is reading and navigating. Using NVDA and FireFox, focus often gets stuck when navigating menus. Chat menus, and switching channels. I will join the group below, thank you! In FF, Could a messages header be added so that I don't accidentally skip the messages list? As for the desktop app, nothing reads, at all. Absolutely nothing, using NVDA. On windows 10.
On 4/21/2018 2:09 AM, Bel (Slack) wrote:
|
||
|
|
||
|
As of right now, it does not work at all with the windows desktop app, but their link in the first thread will give a better idea. Also, join their link. In the first thread. Ask these kinds of questions. |
||
|
|
||
|
This accessibility workstation, on slack, has many blind people using it and chatting about a11y in various places. The wordpress ones and slack channel are getting a lot of action tonight. Again, let me repeat. The, desktop, client, cannot. Cannot, cannot. Cannot! Be, used! At, all, With, NVDA. |
||
|
|
Hi Robert,
Thanks for your patience whilst I checked into this further for you.
Good news on the ARIA roles front. It’s part of the work we are currently doing to improve the experience when using screen readers—which is our number one priority project. We have a project tracker for this and I've added your details so I can keep you updated.
I've popped a link to our Help Centre article on screen readers below. It covers 3 common scenarios and how they can be accomplished right now with a screen reader.
https://get.slack.help/hc/en-us/articles/360000411963-Use-a-screen-reader-with-Slack
I've spoken to our Accessibility Product Manager, George, about your feedback and he's keen to get some specifics around what’s not working for you. For example, is it reading messages, writing, interacting with messages, navigation, etc. George is also keen to learn more about what your expectation is for a 100% ideal UX for screen readers.
In the meantime, you can have direct access to us by joining the web-a11y.slack.com workspace we have set up to discuss Accessibility issues in Slack and beyond. You can join by creating an account from here: http://web-a11y.herokuapp.com/
Warmly,
-Bel