Confirmed users
1,085
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Jump to navigation
Jump to search
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 02:01, 19 March 2010
, 19 March 2010→When the element is compound
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) |
||
| Line 104: | Line 104: | ||
then editor should skip button from navigation sequence if user moves the caret by characters because the ARIA button is a control element and it's not focusable. | then editor should skip button from navigation sequence if user moves the caret by characters because the ARIA button is a control element and it's not focusable. | ||
The editor implementation should have a map to accomplish this requirement, | The editor implementation should have a map to accomplish this requirement, whereby the tag name can be used as a map 'key' for native markup elements, the role attribute value should be used for ARIA widgets, CSS display style should be used for any content it is applicable to. | ||
The editor should be extensible to plug elements of markup languages not supported natively. | The editor should be extensible to plug elements of markup languages not supported natively. | ||