RE: AUWG Teleconference on August 8, 2005

-----Original Message-----
From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
Of Jan Richards
Sent: Sunday, August 07, 2005 6:16 AM
To: w3c-wai-au@w3.org
Subject: AUWG Teleconference on August 8, 2005

>(b) The guideline draft (guideline 1)
http://jan.atrc.utoronto.ca/public/auwg/guidelines.html

Hi,
One question:

GUIDELINE A.?:
A.?.1 Ensure that browser-accessed functionality conforms to WCAG [Priority
RP]. 

Success Criteria: Any component of an authoring tool that is accessed by the
author within a Web browser must conform to WCAG. 

This means, in a CMS system, that the WYSIWYG editor (= plugin) should be:
- if script-based, usable also without script (6.3 Ensure that pages are
usable when scripts, applets, or other programmatic objects are turned off
or not supported. If this is not possible, provide equivalent information on
an alternative accessible page. [Priority 1] )
- if an object, directly accessible: eg, using MSAA inside MS Windows, but
for the other OS?. (8.1 Make programmatic elements such as scripts and
applets directly accessible or compatible with assistive technologies
[Priority 1 if functionality is important and not presented elsewhere,
otherwise Priority 2]) 

In both cases, there are WCAG priority 1. At now there is a CMS/plugin/tool
that support this? OR we can put a note like:
- if a CMS web based application uses technologies referred in WCAG
Checkpoint 6.3 or 8.1, authoring tools should guarantee that the scope of
the object is supported also without script and/or object. For eg, in case
of CMS plugins that have as scope support to edit contents and generate
valid code the web application should have some checks of server-side for
retrieve content post by the user (eg: in a simple textarea, where the user
edit/put HTML code?) and check it for conformance (eg, using Tidy?)


Another point:
B.1.3 Ensure that when the tool automatically generates content it conforms
to WCAG. [Web Content Checkpoints Relative to WCAG] 

This is a problem, because remember that for WCAG there is a checkpoint:
4.1 Clearly identify changes in the natural language of a document's text
and any text equivalents (e.g., captions). [Priority 1] 

This cannot do by an authoring tools and also this violates HTML
specification. Think about, for example, a text equivalent for an image. If
I've got an image of "Palazzo Ducale" and the page content is in english -
for respect 4.1 the code should be:

<img src="palazzoducale.jpg" alt="Image of <span xml:lang="it">Palazzo
Ducale</span>" />

But this code is not valid...

I think that we should check WCAG 1.0 and see what checkpoints can be
related to ATAG. I can check it, if the group agree.

Received on Sunday, 7 August 2005 08:27:04 UTC