E-mail List Archives
Query on button navigation
From: Vemaarapu Venkatesh
Date: May 3, 2017 4:38AM
- Next message:
: "It's business as usual at TPG" - Previous message: Mohith BP: "Re: Tips on totally blind testing for the low vision accessibility"
- Next message in Thread: Jonathan Cohn: "Re: Query on button navigation"
- Previous message in Thread: None
- View all messages in this Thread
Hi all, Greetings
While testing with Voice Over in MAC I observed few buttons in the app are
not navigable with tab key but able to access them with VO+right/ left
arrow keys. I filed this as bug because I feel that every action element
should be in tab order though VO+right/ left arrow keys are primary
navigation keys in MAC. But this is not accepted as bug as these buttons
are navigable with VO+arrow keys. Is it really not a bug?
I have one more query on button navigation in general not in MAC. The
context is, I have a navigation tree view and all these tree view items are
buttons where I can arrow up/ down through the tree view. "Selected/ not
selected" states are assigned to these buttons in the tree view.
1. I feel that buttons should be navigable with tab key but not with arrow
keys. So role should not be button for these tree view items. Is it fine or
it's OK if buttons are navigable with only arrow keys instead of tab.
2. I didnt feel great seeing selected/ not selected states on buttons. Is
it recommendable to use these states on buttons? I think pressed/ not
pressed are only applicable states for buttons.
The above context is seen with JAWS and NVDA in a desktop app.
Need your expertise on these and thanks for the knowledge share in advance.
Thanks,
Venkatesh
- Next message:
: "It's business as usual at TPG" - Previous message: Mohith BP: "Re: Tips on totally blind testing for the low vision accessibility"
- Next message in Thread: Jonathan Cohn: "Re: Query on button navigation"
- Previous message in Thread: None
- View all messages in this Thread