Accessibility/EditorBehaviourOnUserInput: Difference between revisions

m
Line 11: Line 11:
The other and 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 other and 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 [http://www.w3.org/TR/html5/ HTML 5 specification] doesn't specifically address the issue of editable area behaviour. However it's founded on the  assumption that rich elements inside an editable area should have the same behaviour as they would if they weren't inside an editable area (see [http://dev.w3.org/html5/spec/Overview.html#user-editing-actions user editing actions] section). As well this was confirmed by Ian Hickson on [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/021680.html Whatwg list] and by Richard Schwerdtfeger on [http://lists.w3.org/Archives/Public/wai-xtech/2009Jul/0179.html WAI ARIA list].
The [http://www.w3.org/TR/html5/ HTML 5 specification] doesn't specifically address the issue of editable area behavior. However it's founded on the  assumption that rich elements inside an editable area should have the same behavior as they would if they weren't inside an editable area (see [http://www.w3.org/TR/html5/editing.html#user-editing-actions user editing actions] section). As well this was confirmed by Ian Hickson on [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/021680.html Whatwg list] and by Richard Schwerdtfeger on [http://lists.w3.org/Archives/Public/wai-xtech/2009Jul/0179.html WAI ARIA list].


However it drops the case of form builder applications when they want to have stubs instead real control elements which is found unsuitable for their needs. This is a reason to propose two behavior models allowing the user to switch between them.
However it drops the case of form builder applications when they want to have stubs instead real control elements which is found unsuitable for their needs. This is a reason to propose two behavior models allowing the user to switch between them.
Confirmed users
1,396

edits