4.2 - User interfaces.

Following the discussion, I'm asking what we need to require with this 
guidelines.

<Current Wording of guideline>

Guideline 4.2 Ensure that user interfaces are accessible or provide an
accessible alternative(s)

We need at least decide if we are "Web Content Accessibility Guidelines" 
or "Web Accessibility Guidelines".

Inside ISO Working Group, there are activities that involve in different 
mode user interfaces (for applications / plug-ins) and world wide web 
user interfaces.

I think that we need to clarify "what we want to do".

If we require conformance for applications/user agents we go outside 
WCAG and we go to UAAG. UAAG requirements at now are not applied by any 
user agent.

What we can ask is that the "object" inside a web page - that is "web 
content" - must be itself accessible, respecting the accessibility 
guidelines defined by the organization/company that has develop the 
programming rules for this.
For eg, if we have a java application, the object must follow the Java 
Accessibility API, if we have an object that works as ActiveX, it must 
conform to MS Accessibility API.

If we talk about world wide web user interfaces, we need to refer to 
other issues, like:
- right use of X/HTML, CSS, ...
- respect of the guidelines....

So, at least, Guideline 4.2 should be explained well making a 
clarification between "plug-ins" and "world wide web user interfaces".

For eg. what will happen if i have a PDF (tagged) document inside a web 
page and an user click on it, and it will be opened inside the browser 
window? If Acrobat Reader plugin don't conform to UAAG I cannot declare 
conformance of my web site to level 1 ?

Received on Saturday, 12 March 2005 10:33:34 UTC