Confirmed users
1,396
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Jump to navigation
Jump to search
m
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 07:45, 31 May 2010
, 31 May 2010→Rich element terminology
| Line 76: | Line 76: | ||
In short, rich elements can be classified by the following groups: | In short, rich elements can be classified by the following groups: | ||
* in-text elements, i.e. elements behaving mostly as a part of the surrounding text | * {{term|in-text element|in-text elements}}, i.e. elements behaving mostly as a part of the surrounding text | ||
** native focusable elements (e.g. HTML:a) | ** native focusable elements (e.g. HTML:a) | ||
** user defined focusable elements (e.g. HTML:div with tabindex="0") | ** user defined focusable elements (e.g. HTML:div with tabindex="0") | ||
** ARIA widgets like @role="link" | ** ARIA widgets like @role="link" | ||
* integral elements, i.e. elements having different navigation rules than rich text | * {{term|integral element|integral elements}}, i.e. elements having different navigation rules than rich text | ||
** elements containing navigable content | ** elements containing navigable content | ||
*** form controls like HTML input | *** form controls like HTML input | ||
| Line 88: | Line 88: | ||
*** ARIA widgets like @role="button" | *** ARIA widgets like @role="button" | ||
*** disabled form controls and HTML image within the editable area | *** disabled form controls and HTML image within the editable area | ||
* static elements | * {{term|static element|static elements}} | ||
** disabled form controls and HTML image | ** disabled form controls and HTML image | ||