Accessibility/RichContentKeyboardBehaviour: Difference between revisions

Jump to navigation Jump to search
Line 12: Line 12:


==Content classification==
==Content classification==
The web page may include rich text like headings and paragraphs, structural elements like tables and lists. This content doesn't require anything special in the keyboard navigation support, the rules are standard and match to plain text.
The web page may include rich text like headings and paragraphs, and structural elements like tables and lists. This content doesn't require anything special in terms of keyboard navigation support; the rules are standard and correspond to plain text.


Form controls (like HTML input or HTML button) and focusable elements (either HTML anchor or user-defined widgets) can be presented. The keyboard navigation rules must be refined for this type of content.
Form controls (like HTML input or HTML button) and focusable elements (either HTML anchor or user-defined widgets) can be presented. The keyboard navigation rules must be refined for this type of content.


The third type is ARIA widgets, i.e. elements having @role attribute. The ARIA widgets are isolated into own content type since they need to be dealt specially while user navigates through them.
The third type is ARIA widgets, i.e. elements having @role attribute. The ARIA widgets are treated as a separate content type since they need to be dealt specially while user navigates through them.


The other type is static elements like HTML image or disabled form controls. When the caret navigation is on then static element that is put in navigation sequence doesn't make a sense neither for sighted nor screen reader users, so it could be skipped. However when the user navigates through editable area where the user should have full control the static elements should be in navigation sequence.
The other type is static elements like HTML image or disabled form controls. Typically, when caret navigation is on then a static element that is put into the navigation sequence doesn't make sense for sighted and screen reader users, and so it could be skipped. However when the user navigates through editable areas where the user should have full control the static elements should be in navigation sequence.


The last type is generated content that is the content created by :before and :after pseudo styles.
The last type is generated content that is the content created by :before and :after pseudo styles.
Confirmed users
1,085

edits

Navigation menu