- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
From WAI UA Wiki
--Simon Harper 12:25, 16 May 2011 (UTC)
1.2.3 Repair Missing Associations:
The user can specify whether or not the user agent should attempt to predict associations from author-specified presentation attributes (i.e. position and appearance). (Level AAA)
Intent of Success Criterion 1.2.3:
Sometimes the closeness of elements within the document object model is not the same as the visual rendering. This means logical connections are implied by visual associates as opposed to the explicit order in the document object model. These associations are not available to visually disabled users - putting these users at a disadvantage. Using rendered proximity may help to redress some of these disadvantages and enable implicit associations to be explicitly identified when the content cannot be seen. Indeed, this success criteria is linked to WCAG 2.0 SC 1.3.1 and provides for the requirement that 'relationships conveyed through presentation can be programmatically determined'.
Examples of Success Criterion 1.2.3
Fred is a blogger and use's a screen reader to gain access to the online software which facilitates data entry. However, Fred has problems with this software because buttons which are next to each other on the page are not spoken by his screenreader together because they are far apart in the visual presentation. Luckily Fred's new browser helps him by allowing adjacent items in the visual rendering to be explicitly identified - making his interactions much easier.
Related Resources for Success Criterion 1.2.3:
WCAG 2.0 Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.