Accessibility/EditorBehaviourOnUserInput: Difference between revisions

Accessibility/EditorBehaviourOnUserInput (view source)

34 bytes removed , 1 December 2009

m

Confirmed users

1,085

edits

@@ Line 5: / Line 5: @@
 All these elements will be referred everywhere below as <i>special content</i>. Host language control elements (HTML) and ARIA control elements will be referred as <i>control elements</i>.
-Special content elements that manage their own content editing and/or navigation through their content  will be referred as <i>compound elements</i>. Other elements will be referred as <i>integral elements</i>. These are control elements and non editable areas when caret navigation mode is off which means navigation into their content is not allowed.
+Special content elements with their own editable/navigable content will be referred to as <i>compound elements</i>. Other elements will be referred as <i>integral elements</i>. These are control elements and non editable areas when caret navigation mode is off which means navigation into their content is not allowed.
 The problem is there is no specification which would define the behaviour when special content is presented inside of editable area. Browser implementations vary and none are perfect; the editable text mixed with special content is not fully accessible by keyboard and mouse.