2.3.3

Return to Tests_for_CR

Status

Survey of 9 October 2014

Author

Jim Allan

Success Criteria

2.3.3 Present Direct Commands from Rendered Content: The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). (Level AA)

Test

Assertion:

The user can have any recognized <http://w3c.github.io/UAAG/UAAG20-Reference/#def-recognize> direct commands <http://w3c.github.io/UAAG/UAAG20-Reference/#def-direct-command> in rendered content <http://w3c.github.io/UAAG/UAAG20-Reference/#def-rendered-content> (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email).

1. load page with rendered text and direct commands in (e.g. accesskeys),

2. observe that no accesskey key definitions (e.g. Alt+R) are visible on the page

[Suggested rewrite:

2. If direct commands are NOT presented by the user agent (e.g. included immediately after or next to the element they navigate to), identify and enable an option that presents these commands (consult the user agent documentation if necessary)

3. Check that direct commands are now presented by the user agent (e.g. included immediately after or next to the element they navigate to).]

3. using the browser user interface mechanism to select "present Accesskey keystrokes (Control +Alt+R) in context" (or something similar) ( if pass go to next else fail)

Expected results:

2 is true

3 modifier keys + accesskey is displayed in context (adjacent to, immediately following the content with which the accesskey is associated) in rendered content

this will need to be tested with AT (screen reader) or DOM inspector, to ensure 3 also shows in the DOM

Return to Tests_for_CR