SC 2.7.2

Still chomping my way through 2.7 - here is sc 2.7.2 for your perusal, 
there is an Editors note for this: 'postponed for more information about 
the intent of this SC. Is it about providing flyover information? Or is 
it out of place and really belongs in Principle 2' I'm just writing my 
interpretation so that we have somewhere to start.

2.7.2 (former 4.7.3) Access Relationships: The user can access 
explicitly-defined relationships based on the user's position in content 
(e.g., show form control's label, show label's form control, show a 
cell's table headers). (Level A)

Intent of Success Criterion 2.7.2 (former 4.7.3) :
HTML controls and elements are sometimes grouped together to make up a 
composite control; certain elements explicitly relate to others. This is 
the case with Ajax widgets and with form elements. By making sure the 
user can access these explicit relationships means that, say, visually 
disabled users can better understand these relationships even if the 
elements are not adjacent on the screen or the DOM.

Examples of Success Criterion 2.7.2 (former 4.7.3) :
John, has low vision and uses a screen magnifier to access his Browser. 
When interacting with tables and spreadsheets John has to move the 
viewport of the magnifier to understand the row and column titles of the 
cell with which he is interacting. This takes additional time and effort 
and is therefore frustrating. John has just purchased a new Browser 
because it presents the row and column titles when he hovers over a cell 
- this makes him much more productive at his accounting job.

Related Resources for Success Criterion 2.7.2 (former 4.7.3) :
WAI-ARIA
UAAG 2.7.3 Location in Hierarchy


Cheers

-- 
Si.

=======================
Simon Harper
University of Manchester (UK)

More:http://simon.harper.name/about/card/

Received on Friday, 11 March 2011 11:06:04 UTC