W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2005

Proposal for 4.2, Ensure that user interfaces are accessible

From: Loretta Guarino Reid <lguarino@adobe.com>
Date: Tue, 26 Apr 2005 16:38:22 -0700
To: w3c-wai-gl@w3.org
Message-id: <6.1.1.1.2.20050426163111.01cbd160@mailsj-v1.corp.adobe.com>

We propose removing this guideline, since much of it is now covered by the 
baseline question, and modifying other parts of WCAG to cover the remaining 
issues. The 6 proposed modifications are listed below.

Please review this proposal to ensure that we really have captured all the 
requirements, particularly for dynamic web content. Are there now 
techniques that no longer have a guideline associated with them?


Proposals

[1] Definition of baseline:
<proposal>
The minimum set of technologies that must be supported by user agents
in order to access all information and functionality of the Web
content. Developers must ensure that all information and functionality
comprising the Web content conforms to WCAG assuming user agents
support only this minimum set of technologies. Developers may also
choose to use technologies that are not in the minimum set provided
that the following are true:

      The Web content is still accessible using user agents
that only support the technologies that are in the minimum set
(i.e. the use of technologies that are not in the minimum set does not
"break" access to the Web content by user agents that don't support
them.)

      All content and functionality must be available using only
the baseline technologies.
</proposal>

[2] Definition of technology
<proposal>
"Technology" means a data format, programming or markup language, protocol 
or API.
</proposal>

[3] Conformance Requirements modifications
<proposal>
WCAG 2.0 defines accessibility guidelines and success criteria as
functional outcomes that are technology independent to allow conformance
using any Web technology that supports accessibility. WCAG 2.0 therefore
does not require or prohibit the use of any specific technology. It is
possible to conform to WCAG 2.0 using W3C and non-W3C technologies,
provided they are supported by accessible user agents. In choosing
technologies to rely upon, developers need to know what technologies they
can assume are supported by user agents. This is called the baseline.

Baselines may be defined outside the WCAG 2.0 guidelines as part of a more
comprehensive accessibility policy. Baseline considerations will be
significantly different if the organization defining the baseline can
guarantee the user agents used by the users. For example, a company or
government agency provides its employees with the information technology
tools they need to do their jobs. So for intranet sites used only by
employees, it is reasonable for the baseline to include newer technologies
that might only be supported in one user agent. For guidance, see "WCAG 2.0
Guide to Choosing Baselines".

Technologies that are NOT in the baseline may still be used as long as all
Web content and functionality is available, in a conforming way, to users
whose user agents do not support the additional technologies.

1. Any conformance with WCAG 2.0 requires that all level 1 success criteria
for all guidelines be met assuming user agent support for only the set of
baseline technologies.

2. WCAG 2.0 conformance at level A means that all level 1 success criteria
for all guidelines are met assuming user agent support for only the set of
baseline technologies.

3. WCAG 2.0 conformance at level Double-A means that all level 1 and all
level 2 success criteria for all guidelines are met assuming user agent
support for only the baseline technologies.

4. WCAG 2.0 conformance at level Triple-A means that all level 1, level 2
and level 3 success criteria for all guidelines are met assuming user agent
support for only the baseline technologies.
</proposal>

[4] Reading order
<proposal>
Promote the following success criteria of GL 2.4 to level 1:
      * When content is arranged in a sequence that affects its meaning,
that sequence can be determined programmatically.
      * When a page or other delivery unit is navigated sequentially,
elements receive focus in an order that follows relationships and sequences
in the content
</proposal>

[5] authoring applications (part of conformance?)
<proposal>
Web applications that are created for the sole purpose of assisting
users to create content intended for publication on the web must
conform to at least Level A of the ATAG 2.0 Guidelines.
</proposal>

[6] New GL 1.3 Level 1 SC
<proposal>
The role, state and value of every element of the web content can be
programmatically determined. Elements whose states and values can be
changed via the user interface can also be changed programmatically.
</proposal>
	
Received on Tuesday, 26 April 2005 23:38:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC