RE: Action-467 1.11.1 and 1.11.2 again

Following up on 1.11.1 and 1.11.2.

The full current text for these state what is below.

I would propose the following changes:

Original:

Summary:The user agent presents information about content relationships (e.g. form labels, table headers)(1.11.1), and extended link information (e.g. title, internal vs. external) (1.11.2)


1.11.1 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) @@ 467
 
Intent of Success Criterion 1.11.1: 
Some users have difficulty perceiving, remembering, or understanding the relationships between elements and their contexts. HTML controls and elements are sometimes grouped together to make up a composite control; certain elements relate to others in a recognizable manner, such as relationships with 'id' attributes and child elements. This is the case with Ajax widgets and with form elements. By making sure the user can be informed about these 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 1.11.1:◦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 1.11.1:◦WAI-ARIA
◦UAAG 2.5.3 Location in Hierarchy


1.11.2 Extended Link Information:

 The user agent provides for each link: (Level AAA) @@ 467

 •link title
•technology type (of the linked Web resource)
•internal/external (whether the link is internal to the resource e.g. the link is to a target in the same Web page)

 Intent of Success Criterion 1.11.2: 
Users who use screen readers need to be able to easily discover information about a link, including the title of the link, whether or not that link is a webpage, PDF etc. and whether the link goes to a new page or a different location in the current page, in order to navigate Web content more quickly and easily.
Examples of Success Criterion 1.11.2:◦ Robert, who uses a screen reader, needs to know whether a given link will automatically open in a new page or a new window. The browser indicates this information so he can discover it before he makes a decision to click on a link.
◦Maria has an attention disorder, new windows opening are a large distraction. She needs to know whether a given link will automatically open in a new page or a new window. The browser indicates this information so she can decide not to follow a link that opens a new window.

Related Resources for Success Criterion 1.11.2:◦To be written

Proposed Changes:

1. Make 1.11.1 a level AA.

I would like to discuss 1.11.2.  I still ask why the title for example is more important to a user with a screen reader or other accessibility need than anyone else.  You can make a bit of a case for the link type and perhaps the open in new window/within the same page cases.




-----Original Message-----
From: Jim Allan [mailto:jimallan@tsbvi.edu] 
Sent: Wednesday, May 30, 2012 11:37 AM
To: WAI-ua
Subject: Action-467 1.11.1 and 1.11.2 again

after an hour of forensics...1.11.1 was removed at the Nov 2010 F2F.
the current wording appeared in the 25 May 2011 draft as 1.11.2 complete with IER. It has remained unchanged since that time. At some time (I didn't bother to check) it was moved to 1.11.1 because it is Level A.

the current 1.11.2 Extended Link info had some discussion and Kelly was to have an action, but Zakim would not allow him to have actions at that time (Nov 2010). He may have additional comments.

I propose closing Action-467.
Pass judgement on the current 1.11.1. Current browser behavior includes form controls but not table cell associations. There is an extension for FF that add the feature for table cells (Firefox Accessibility Extension http://firefox.cita.illinois.edu/)

current 1.11.1 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)

see if Kelly has anything to say about 1.11.2, make a decision.

and finally mark 1.11 as done.

--
Jim Allan, Accessibility Coordinator & Webmaster Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/ "We shape our tools and thereafter our tools shape us." McLuhan, 1964

Received on Thursday, 31 May 2012 12:33:02 UTC