- From: Richards, Jan <jrichards@ocadu.ca>
- Date: Tue, 5 Jun 2012 15:34:38 +0000
- To: WAI-ua <w3c-wai-ua@w3.org>
EXISTING: 2.5.5 Access to Relationships which Aid Navigation: The user can access explicitly-defined relationships based on the user's position in content, and the path of nodes leading from the root of any content hierarchy to that position. (Level AA) PROPOSAL: -some of the SC is covered, by 1.10.1. The rest will be covered by a new SC: 1.10.2 Access to Element Hierarchy: The user can determine the path of element nodes from the root element of the element hierarchy to the currently focused or selected element. (Level AA) Intent: Users who have difficulty working with a web page or document can use user style sheets or scripts to modify its presentation or interaction to better meet their needs. This often requires them to identify specific elements, their attributes, and their position in the element hierarchy. The user agent can facilitate this process by allowing the user to navigate to an element, or select it if it is not navigable, and querying the information they need. If this features is not provided, the user may not be able to find the corresponding element in the source view or entire document tree. Examples: Jack wants certain content on a web page to be displayed in a larger font, and wants to create a user style sheet that would modify its appearance. He needs to identify the class or ID of the particular element, so he puts the focus onto or selects the text he's interested in, opens the browser's debug window, which shows him that the selected text is an element with class "story" inside a paragraph inside a DIV with class "Premiere". He then knows the combination of classes and element types to specify in the user style sheet.
Received on Tuesday, 5 June 2012 15:38:29 UTC