Confirmed users
1,396
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Jump to navigation
Jump to search
m
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 03:27, 9 November 2009
, 9 November 2009→Summary
m (→Summary) |
m (→Summary) |
||
| Line 3: | Line 3: | ||
The article is aimed to propose editor behaviour on user input when control elements are contained in editable area. The start point of this proposal is control elements inside of editable area should have normal behaviour as they wouldn't be inside of editable area. So that they should be operable with mouse and keyboard as usually. The point doesn't contradict with HTML 5 specification. However the specification doesn't address editable area behaviour in question. That was a reason to start this proposal. | The article is aimed to propose editor behaviour on user input when control elements are contained in editable area. The start point of this proposal is control elements inside of editable area should have normal behaviour as they wouldn't be inside of editable area. So that they should be operable with mouse and keyboard as usually. The point doesn't contradict with HTML 5 specification. However the specification doesn't address editable area behaviour in question. That was a reason to start this proposal. | ||
The start point can be found not suitable for certain amount of web applications and they might want to change it somehow to meet their specific needs, for example, if web application wants to provide an ability to edit the button's label. | The start point can be found not suitable for certain amount of web applications and they might want to change it somehow to meet their specific needs, for example, if web application wants to provide an ability to edit the button's label in wysiwyg mode. This proposal is indented to provide sort of default behaviour and don't pretend to define unique one for all possible cases. | ||
The main goal | The main goal is to ensure control elements inside of editable area are accessible both for any user. Therefore it's necessary ensure control elements are accessible and operable by keyboard. | ||
In this proposal under control elements are considered either HTML controls or ARIA controls. However the proposal is not restricted by HTML only, proposed ideas should work for other markup languages. | In this proposal under control elements are considered either HTML controls or ARIA controls. However the proposal is not restricted by HTML only, proposed ideas should work for other markup languages. | ||