OK, Here are my thoughts on this based on the previous messages in this
First, hotkeys. Manager’s UI is rendered as a web page by screen
readers. This is a very good thing and gives additional options to what
i’ll lay out below.
Jump to hot keys.
These are keys that when pressed take you to a specific place on a page.
We can use this because of the web page statement i made above. These
are screen reader specific and already exist so we don’t need to create
the keys, just
elements we can use to make them do what we want to. This is why i was
talking about headings earlier in the thread. This is just one of the
possible elements, i chose it because it’s the one i use the most. It
also offers us the ability to create sub headings if we wish but i don’t
feel like there is enough to make that worthwhile. So if there were
level one headings at the beginning of each section i could cycle
through all 3 sections by pressing the letter h.
The letter h is a screen reader specific command and will work if the
person is using either the jaws or “NVDA” screen readers, but not
necessarily for other screen readers. Other screen readers will have a
similar command though. For people not using a screen reader this does
This is what would make manager keyboard friendly for sighted people.
These shortcut keys should be a combination of 2 or 3 keys pressed in
sequence. Most of us are probably familiar with “control c” as an
example. I’d recommend focusing on the navigation pain and the back
button as a beginning. My personal preference would be to have 2 key
shortcuts, for example, “alt left arrow” for back. I do recognize that
this could limit combinations though so if you’d rather want 3 keys that
could work as well. I haven’t thought through the rest of the navigation
pain and what each option should be so won’t list those out here. If
people want suggestions, just ask.
As mentioned earlier, all screen readers have options for navigating web
pages, these work within manager so this makes the program nagivable as
is, just a bit clumsy.
These controls aren’t standard across operating systems or screen
readers though so i’d recommend letting the screen readers handle the
navigation and just create the command keys section and headings.
Experience level and testing notes.
I should mention here in case no one has figured it out yet, I myself am
a blind computer user and am planning to start using manager at the end
of the year. All the work i have done in manager so far has been in
windows 7, 8.1, and 10. I have not tested it on mac so can’t comment on
accessibility or lack their of there.
The screen readers i use are jaws https://freedomscientific.com and
NVDA is open source for those that want to play. Also, the NVDA
developers will be more than happy to help with any development focused
questions if needed.
There was some mention made of windows built in accessibility in this
thread. If using anything older than windows 10 don’t bother testing as
“narator”, the built in screen reader was a peace of junk. Now with
windows 10 it’s better but if the above suggestions are followed narator
should work without needing more work.
Also, as one final note. I know i have focused almost completely on the
blindness perspective here and that is because as a blind user, this is
the part important to me and also what i can speak the most about. If
there are any other accessibility groups out there that want inclusion
in this just speak up, i’m more than happy to discuss those needs and
push for there inclusion into manager, i just don’t happen to know what