4.1 work in progress

 

 

We have been working on 4.1 to clean it up and develop the HTM docs etc.
In the process we are have come up with some clearer and more accurate
wording.  We are posting this to the GL list for comment.

 

 

Some intro comments.

 

Label - usually refers to something you can see (or hear if presentation is
auditory).

 

Name - is a user comprehensible ID for a component.   A widget on a screen
may not have a label - or the label may be an icon.  But it must have a name
attribute that is attached to it.  

 

We changed name of Guideline from  "ensure compatibility"  to   "Enable
compatibility" since you can't ensure it without controlling the AT.  Also
it refers to the future.  So Ensuring the future is .. Well..  ambitious.
Enable is a bit better. 

 

Also proposing changes to some definitions - so look at those as well. 

 

 

If these look good we will proceed go write up the HTM and how to meet docs.

 

We will survey these tomorrow - but if you have suggestions - post them now
so we can incorporate them.

 

Thanks 

Gregg

 

 

 

 


DEFINITIONs 


PROGRAMMATICALLY DETERMINED 
determined using software services that are supported, publicly documented,
and implemented by assistive technology. 

PROGRAMMATICALLY SET 
set using software services that are supported, publicly documented, and
implemented by assistive technology. 

label 

SUGGEST DELETING LABEL AND REPLACE WITH NAME  -- in 1.1.2  1.1.4    and
2.4.6
     [ WAS "text that identifies a component within Web content. (from ED
24Jan06)"] 
this allows us to not use LABEL which has HTML connotations.  AND it
acknowledges that the name may not be visible - though labels usually are.
FINALLY - it harmonizes us with other US and ISO accessibility standards

NAME 
text by which software can identify a component within Web content to the
user. 

ROLE 
text or a number by which software can identify the function of a components
within Web content (such as an image that functions as a hyperlink, command
button, or check box). 

PERCEIVABLE PROPERTIES
information about the identity, nature, and state that are presented to the
user. 

 

 


Guideline 4.1 Enable compatibility with current and future user agents
(including assistive technologies)


 


Level 1 Success Criteria for Guideline 4.1


 


Guideline 4.1 Support compatibility with current and future user agents
(including assistive technologies)


 


4.1.1 Web Pages (including Web
<http://trace.wisc.edu/wcag_wiki/index.php?title=Web_Pages_%28including_Web_
Applications%29&action=edit>  Applications) can be parsed unambiguously and
the relationships in the resulting data structure are also unambiguous. [
How_to_Meet_Success_Criterion_4.1.1
<http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criteri
on_4.1.1>  ]


 


4.1.2 For each user interface component in the content, the name
<http://trace.wisc.edu/wcag_wiki/index.php?title=Name_attribute&action=edit>
, role
<http://trace.wisc.edu/wcag_wiki/index.php?title=Role_attribute&action=edit>
, and all perceivable properties
<http://trace.wisc.edu/wcag_wiki/index.php?title=Perceivable_attributes&acti
on=edit>  can be programmatically determined
<http://trace.wisc.edu/wcag_wiki/index.php?title=Programmatically_determined
&action=edit> .[ How_to_Meet_Success_Criterion_4.1.2
<http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criteri
on_4.1.2>  ]


NOTE: SC 4.1.2 through 4.1.4 are usually automatically met by HTML and other
markup languages in conjunction with accessible user agents unless authors
are creating their own user interface components in software. 

 
DELETE THIS new 4.1.3 IF NEW 1.3.1. SAYS "INFORMATION AND RELATIONSHIPS
CONVEYED THROUGH PRESENTATION CAN BE PROGRAMMATICALLY DETERMINED.

4.1.3 Relationships between user interface components in the content can be
<http://trace.wisc.edu/wcag_wiki/index.php?title=Programmatically_determined
&action=edit> programmatically determined. 


 

 


4.1.4 Content and attributes of user interface components can be
programmatically set
<http://trace.wisc.edu/wcag_wiki/index.php?title=Programmatically_set&action
=edit>  directly to any values to which they can be set through the user
interface [ How_to_Meet_Success_Criterion_4.1.4
<http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criteri
on_4.1.4>  ]


Note: Some examples of standardized properties that typically can be changed
by the user interface include its value, whether it is currently selected,
and whether it currently has the focus. 


 


4.1.5 Any changes to user interface components in the content can be
programmatically determined
<http://trace.wisc.edu/wcag_wiki/index.php?title=Programmatically_determined
&action=edit>  without having to compare current and past values to detect
change. [ How_to_Meet_Success_Criterion_4.1.5
<http://trace.wisc.edu/wcag_wiki/index.php?title=How_to_Meet_Success_Criteri
on_4.1.5>  ]


 

 

 

 

 


Gregg

------------------------

Gregg C Vanderheiden Ph.D. 
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848  
For a list of our list discussions http://trace.wisc.edu/lists/

The Player for my DSS sound file is at http://tinyurl.com/dho6b 

 <http://trace.wisc.edu:8080/mailman/listinfo/>