Confirmed users
1,085
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Jump to navigation
Jump to search
m
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 15:52, 1 December 2009
, 1 December 2009→Summary
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) m (→Summary) |
||
| Line 17: | Line 17: | ||
Note: for discussions about navigation, unless specified assume caret navigation mode is off. | Note: for discussions about navigation, unless specified assume caret navigation mode is off. | ||
The problem we want to address here is: there is no specification which would define the interaction when special content is presented inside | The problem we want to address here is: there is no specification which would define the interaction when special content is presented inside an editable area. Browser implementations vary and none are perfect; editable text mixed with special content is not fully accessible by keyboard and mouse. | ||
The most widespread use case is applications used to create design of web pages, i.e. used to build forms and web pages with form elements. The more rarer case is when editable area with control elements is used as unformalized form where control elements are used to help to fill up the form however the user has an ability to remove the whole text including control elements and write his own version. | The most widespread use case is applications used to create design of web pages, i.e. used to build forms and web pages with form elements. The more rarer case is when editable area with control elements is used as unformalized form where control elements are used to help to fill up the form however the user has an ability to remove the whole text including control elements and write his own version. | ||