Confirmed users
1,085
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 15:23, 7 April 2010
, 7 April 2010→ARIA widgets
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) m (→ARIA widgets) |
||
| Line 30: | Line 30: | ||
ARIA is all about screen readers support and it doesn't change the content behavior, i.e. doesn't affect on sighted users. On the another hand ARIA always comes with custom widget development. It's always hard work to create the custom widget and make behave it correct in the web page context without the browser help. For example, if the div was used to create a button or link then it's a div from the browser point of view. However these widgets assume different keyboard navigation behavior. It would be really nice if the browser uses the ARIA as the widget classifier to fit the behavior depending on the widget type. | ARIA is all about screen readers support and it doesn't change the content behavior, i.e. doesn't affect on sighted users. On the another hand ARIA always comes with custom widget development. It's always hard work to create the custom widget and make behave it correct in the web page context without the browser help. For example, if the div was used to create a button or link then it's a div from the browser point of view. However these widgets assume different keyboard navigation behavior. It would be really nice if the browser uses the ARIA as the widget classifier to fit the behavior depending on the widget type. | ||
[davidb: I disagree with this; I don't think we should make any assumptions about keyboard behaviour based on @role] | [davidb: I disagree with this; I don't think we should make any assumptions about keyboard behaviour based on @role. I do think we could use @role for helping page traversal patterns] | ||
==Control the navigation sequence== | ==Control the navigation sequence== | ||