toggle quoted messageShow quoted text
I'm afraid that I don't have answers to the question about navigating by section. When the browse mode cursor is enabled I often press ctrl-home to move to the top of the screen and search for the word "unread", pressing enter on channels with unread messages
that I want to read. Once I do this the focus moves to the edit field for entering a message within that channel and you are also below the last unread message. I then press escape to reenable browse mode and use shift-K to move backward by links. Within each
message there are two links, one for the sender and another with the timestamp, which helps me to navigate across messages. I admit this is not the most elegant way to navigate this program but as it's how I first learned it I do it so quickly that, for me,
it's actually efficient.
This conversation is causing me to consider setting up a mailing list for blind users of Slack.
I just may do that ...
On 3/1/2019 11:35 PM, Sam Bushman wrote:
Is there a better way to get from section to section of the app than pressing f6 – is there a way to see all unread messages with out by mistake making them already read just by passing by them?
I do find it basically accessible but hard to navigate and vary slow by the time you move around – it’s quite clunky and hard to use.
Any thoughts to improve things? Any settings to turn on or off that helps?
If you are in a channel where you have a list of messages, disabling browse mode and then pressing shift-f6 should move your focus to the list of messages. You will likely find yourself at the bottom of the list, pointing to the newest message in the stack.
Pressing up arrow should move from one message to the next, going from newest to oldest. I have not tested this method with NVDA as I usually use browse mode. Admittedly, this may not be the most efficient way to read messages. However, it's the way that I
first learned how to navigate in Slack and I find that my muscle memory just kicks in and allows me to navigate very quickly.
On 3/1/2019 11:17 PM, Sam Bushman wrote:
I have been playing with slack. The added keyboard support is truly quite helpful.
I often have a problem using the f6 key taking me from section to section.
Can you please write me off list and maybe provide a few navigation tips?
I would be most grateful. I need this badly for work.
Thanks so much for your help.
Regarding Slack I have used it and the program is accessible. However, just because a program is screen reader accessible doesn't necessarily mean that it has an intuitive user-friendly interface. While the UI could do with some improvements to make the
program more usable for a screen reader user the fact is that it is usable enough that someone with decent screen reader skills should, after a bit of practice, be able to use it. The Windows version can either be used with browse mode disabled which, for
some, may be more efficient or it can be used with browse mode enabled by navigating through messages as you would navigate a Web page. The iOS version, on the whole, is also fairly good. As someone else on this list has stated, the development team is extremely
good at responding to users very quickly. Sometime last year, one of the developers inadvertently disabled the ability to navigate through messages using the virtual or browse mode cursor. As this is the way that I use Slack and since using the program is
essential for me I was in a bit of a panic and contacted them via their Twitter account (their handle is @SlackHQ.) This was on a Thursday. I very shortly received an apology from one of the developers who understood what the issue was and he promptly fixed
it by the end of Friday. That is certainly excellent service.
On 3/1/2019 10:00 PM, David Goldfield wrote:
Jonathan Mosen offers a tutorial covering the use of Zoom from a blindness perspective, which you can
acquire from this link.
On 3/1/2019 2:06 PM, hurrikennyandopo ... wrote:
is there a tutorial on how to use zoom? with nvda? or a section to guide you on how to use it?
I have never used it.
On 2/03/2019 3:47 AM, Robert Kingett wrote:
I'd also try writing Zoom's accessibility team as well. I haven't used the chat feature all that much, so can't comment, but below is zoom's accessibility team email.
below is their ticket system.