|
|
Rank: Newbie
Groups: Member
Joined: 3/29/2012
Posts: 3
|
Can you please comment if the EO Controls are compliant with Section 508 accessibility ?
I am attempting to use the EO.Web Menu and TabStrip controls.
The EnableKeyboardNavigation property does allow use of the keyboard arrows, but doesn't respond to the Tab key like the ASP.Net Menu control.
Thank You
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
They are. Section 508 does not specifically require tab key to work (just imagine some device such as iPad doesn't even have a tab key), it only requires the page to work without a point device (mouse). I do believe it's a good idea to add tab key support though, so we will look into that and see what we can do.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 3/29/2012
Posts: 3
|
Thanks. I therefore have a dilemma..
I cannot reach focus on the menu control on the page to use the arrow keys (even when EnableKeyboardNavigation is enabled) without a pointing device (mouse) or a functional Tab Key.
Please explain how it is possible to navigate to the control without a pointing device so that the page is compliant.
When I Tab through the controls, navigation skips over the Menu. It is not accessible.
Thank you for your quick reply.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
You would setup a hot key to activate the menu through the menu control's Shortcut property. Once set, you can use the Shortcut key combination you set to activate the menu (usually automatically focus the first item), once you are there, you can use arrow/enter/esc to navigate the menu.
I agree with you that tab key looks like a more elegant solution. We will look into that and see what we can do.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 3/29/2012
Posts: 3
|
Hi !
Thanks again for the quick reply..
Unfortunately, we will not be able to use these two controls since they are not consistent with the accessibility support in the standard Asp.Net controls (ie Menu, etc.).
Users that are visually impaired must be able to use the tab key and narration of the control text to determine page context.
Activating short-cut keys for multiple controls on a page is non-standard, non-consistent and confusing for the visually impaired user and poses additional user-training and usability issues.
This is highly disappointing since the control set is extremely powerful and much more functional than the standard Asp.Net controls.
We strongly suggest you add this feature to the control set so that they will at least be consistent with the standard navigation behavior of the Asp.Net controls.
Thank you again for your responsiveness.
We look forward to using the rest of the control set.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Yes. Your suggestion makes perfect sense to us. Thank you very much for your excellent feedback!
|
|