Confirmed users
1,085
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 19:46, 23 March 2010
, 23 March 2010→When the element is compound
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) |
||
| Line 110: | Line 110: | ||
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 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. | ||
Comment: I think asking the editor to pay that kind of attention to the role attribute makes things more complicated and possibly fragile. Note DHTML widget authors are currently responsible for keyboard handling via JS -- davidb | ''Comment: I think asking the editor to pay that kind of attention to the role attribute makes things more complicated and possibly fragile. Note DHTML widget authors are currently responsible for keyboard handling via JS. Specialize caret implementation based on role is pretty complicated. -- davidb'' | ||
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. | ||