- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Sun, 30 Jul 2006 10:25:07 -0500
- To: "'David MacDonald'" <befree@magma.ca>, <public-wcag-teama@w3.org>
- Cc: "'Loretta Guarino Reid'" <lguarino@adobe.com>, "'Michael Cooper'" <cooper@w3.org>
- Message-ID: <004f01c6b3ec$58795c00$9d02fea9@NC6000BAK>
This is excellent David. Just what we need to address these issues.
You didn’t include the complete comments at the bottom (the ones down there
are from my example). Could you cut off the example items and paste on the
6 from your list?
OOPs I just noticed something
Audio-description has a hyphen in it. Therefore other mentions of it will
not get caught.
So I searched for “Audio description” in basic search and find that there
are 20 issues that mention it. sometimes it is in the SORT field but the
hyphen is missing so it wasn’t caught in the keyword summary.
We need to check the (few) keywords that are
1) not made up
2) hyphenated or concatenated.
And see if there are other items that should have been caught – and fix them
so they show up in the list.
David – you just need to go to basic search and type “audio description”
in the field and check them out
- add hyphens to the SORT names that don't have them. And
generally check out the rest to see if we need to include them in the
analysis.
Oops.
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center
University of Wisconsin-Madison
The Player for my DSS sound file is at http://tinyurl.com/dho6b
<http://tinyurl.com/cmfd9>
_____
From: public-wcag-teama-request@w3.org
[mailto:public-wcag-teama-request@w3.org] On Behalf Of David MacDonald
Sent: Sunday, July 30, 2006 7:58 AM
To: 'Gregg Vanderheiden'; public-wcag-teama@w3.org
Cc: 'Loretta Guarino Reid'; 'Michael Cooper'
Subject: RE: Please return home
Report on “Audio Description” comments.
>From the 6 comments I make two recommendations.
1) Allow for AD to cover video content we may not have mentioned <proposed>
"Audio descriptions of video provide information about actions, characters,
scene changes, on-screen text, etc. " </proposed> Or use “and other visual
content” instead of “etc” (if we think “etc.” is not testable)
2) Change Audio Description to a “Mass Noun” (always in singular) Search and
replace “Audio Descriptions” with “Audio Description” throughout all our
documents.
The WGBH wanted to move all audio descriptions including descriptions of
live video to Level 1, (this is not unexpected given their mandate) and NTT
CLARUTY CORP. of Japan wanted to remove AD completely because lack of
information in Japan. Sheilesh was calling for extended descriptions at a
higher level.
I think AD requirements are currently at the right levels and there is not
compelling evidence that they should be changed. I think all the proposed
responses are OK. The fact that there are only 6 comments says something I
think.
Cheers
David
A full discussion is below.
1) One is by Geoff Freed of WGBH National Center for Accessible Media. They
both say the same thing. That Descriptions “should be required at level 1,
Period!” RESPONSE: {reject} After much discussion, the group felt that a
full transcript should be allowed as an alternative. A full transcript
provides all the information from the multimedia (visual and auditory). That
has been our measure for an accessible alternative. It does not provide the
same experience, but text alternatives to graphics do not provide the same
experience either. In addition, audio-description very often does not
provide anywhere near all of the information presented visually. Audio
descriptions therefore may not actually provide enough information to
provide all of the information in a video such as a training video. Thus, a
full text alternative (audio and visual) would provide more information than
just an audio description. It was therefore decided to allow the option to
provide either audio description or a full text transcript at level 1.
2) Geoff Feed goes on to say LIVE Audio Descriptions should be Level one:
RESPONSE: “Unless live action is scripted, there is no way to know when the
gaps will occur so that live audio description can be done (unless it is
video footage which essentially has no audio dialog or, you are going to
delay broadcast by some significant amount).”
3) Eric Hansen of Educational Testing Service says it’s a significant change
for WCAG 1.0 which had AD at L1. RESPOND WITH: "Yes this is a significant
change. It was done with the realization that AD will not work for some
training videos where there is no gap in dialog and important visual
information. It also allows a full text equivalent as an alternative for
those cases where that is easier -- in recognition that a text alternative
is has always been viewed as sufficient.
4) Sheilesh says that extended audio descriptions are currently required at
Level 1 and 2 because he says we do not distinguish between extended and
natural, and he says they would be required pauses are too short. He wants
to delete 1.2.6 and thereby infer more explicitly that we require AD
extension. He thinks it’s repetitive. RESPONSE: {not accept} Extended audio
descriptions are not required by 1.2.2 and 1.2.3. In fact Audio Description
is described as additional audio content during the naturally occurring
gaps. 1.2.6 is therefore needed to introduce the extended audio description
concept.
5) Joe Clark .says Audio description provides ""information about actions,
characters, scene changes, and on-screen text"" among other things. Nobody
has produced an exhaustive list, and maybe we do or do not need such a
thing, but it isn't limited to those items. RESPONSE: @@ [partial accept]
<proposed> "Audio descriptions of video provide information about actions,
characters, scene changes, on-screen text, and other visual content.
</proposed>" Or simply add the word "etc." to the list (which is my
preference)
6) Joe Clark .says Change all instances of "Audio Descriptions" to "Audio
Description".RESPOND: We have changed the definition of Audio Description to
allow description of other visual elements not mentioned in the list. The
WCAG definitions standard audio description as an alternative that is
inserted during natural occurring pauses. We cannot require AD to occur over
dialogue, even if there is not enough space to fully describe the content,
because putting AD over dialogue would make that dialogue inaccessible.
Level 3 requires extended audio description which is usually how this should
be handled. Although AD is not yet standardized as a Mass Noun
(http://ncam.wgbh.org/richmedia/tutorials/audiodesc.html) There is momentum
in the industry to make it a Mass Noun and therefore we have changed it
according to your recommendation.
7) Audio description is typically ""added during existing pauses in
dialogue." There are quite a few occasions in which it is necessary to
describe over dialogue.
8) "Audio description"" is generally written as a mass noun, like
""captioning."" Hence ""audio description of video provides."" RESPOND:
Although AD is not yet standardized as a Mass Noun
(http://ncam.wgbh.org/richmedia/tutorials/audiodesc.html) There is momentum
in the industry to make it a Mass Noun and therefore we have changed it
according to your recommendation.
9) Tomoaki Kodaka <koda@pk9.so-net.ne.jp of NTT CLARUTY CORPORATION, wants
us to drop AD completely because they don’t know anything about them in
Japan.
...access empowers people...
...barriers disable them...
www.eramp.com
_____
From: public-wcag-teama-request@w3.org
[mailto:public-wcag-teama-request@w3.org] On Behalf Of Gregg Vanderheiden
Sent: Sunday, July 30, 2006 1:03 AM
To: public-wcag-teama@w3.org
Cc: 'Loretta Guarino Reid'; 'Michael Cooper'
Subject: Please return home
Now that team B and C have caught up to us. We need you back working on
team A issues.
People asked us to make assignments so I will do that. If you wish to do a
different topic that is fine.
Please do up reports for the following topics for the Tues Meeting.
Ben – MathML
David – Audio Description
Bruce - Font
Alex – You already have one - I can't remember which now.
Bengt - Aggregated
Remember
a) Don't just look at items in our column. Check out the ALL and ANYWHERE
to be sure there aren't any other items that should impact your summary. If
there are – include them in analysis.
b) the suggested format is
1 – summary of issues
2 – any comment, suggestions, or Proposals to address them if you can.
3 – paste the full comments for each comment a the bottom.
(suggest the abbreviated format of
a) Number – commenter
b) Comment
c) any working group notes or proposals
I pasted an example (of the full listing of comments) at the bottom of this
email
Here is our full workscope
Keyword
All
Anywhere
Team A
Team B
Team C
Editors
CLARIFICATION
10
20
1
3
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CLARIFICATION&keyword_wgnotes=TEAMB>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CLARIFICATION&keyword_wgnotes=TEAMC>
4
2.3*
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=2.3*&hold_only=false>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=2.3*&keyword_comment=2.3*&hold_only=false>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=2.3*&keyword_wgnotes=TEAMA>
4.1.2
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=4.1.2&hold_only=false>
6
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=4.1.2&keyword_comment=4.1.2&hold_only=false>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=4.1.2&keyword_wgnotes=TEAMA>
MATHML
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=MATHML&hold_only=false>
3
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=MATHML&keyword_comment=MATHML&hold_only=false>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=MATHML&keyword_wgnotes=TEAMA>
COGNITIVE
25
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=COGNITIVE&hold_only=false>
47
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=COGNITIVE&keyword_comment=COGNITIVE&hold_only=false>
3
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=COGNITIVE&keyword_wgnotes=TEAMA>
11
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=COGNITIVE&keyword_wgnotes=TEAMB>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=COGNITIVE&keyword_wgnotes=TEAMC>
8
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=COGNITIVE&keyword_wgnotes=EDITORZ>
AGGREGATED
4
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=AGGREGATED&hold_only=false>
7
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=AGGREGATED&keyword_comment=AGGREGATED&hold_only=false>
4
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=AGGREGATED&keyword_wgnotes=TEAMA>
AUDIO-DESCRIPTION
6
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=AUDIO-DESCRIPTION&hold_only=false>
6
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=AUDIO-DESCRIPTION&keyword_comment=AUDIO-DESCRIPTION&hold_only=
false>
6
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=AUDIO-DESCRIPTION&keyword_wgnotes=TEAMA>
FONT
8
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=FONT&hold_only=false>
25
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=FONT&keyword_comment=FONT&hold_only=false>
6
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=FONT&keyword_wgnotes=TEAMA>
1
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=FONT&keyword_wgnotes=TEAMB>
1
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=FONT&keyword_wgnotes=EDITORZ>
CONTRAST
13
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONTRAST&hold_only=false>
29
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONTRAST&keyword_comment=CONTRAST&hold_only=false>
10
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONTRAST&keyword_wgnotes=TEAMA>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONTRAST&keyword_wgnotes=EDITORZ>
LEVEL-CHANGE
36
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVEL-CHANGE&hold_only=false>
36
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVEL-CHANGE&keyword_comment=LEVEL-CHANGE&hold_only=false>
11
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVEL-CHANGE&keyword_wgnotes=TEAMA>
16
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVEL-CHANGE&keyword_wgnotes=TEAMB>
8
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVEL-CHANGE&keyword_wgnotes=TEAMC>
1
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVEL-CHANGE&keyword_wgnotes=EDITORZ>
LEVELAAA
13
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELAAA&hold_only=false>
13
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELAAA&keyword_comment=LEVELAAA&hold_only=false>
11
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELAAA&keyword_wgnotes=TEAMA>
2
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELAAA&keyword_wgnotes=TEAMB>
LEVELS
19
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELS&hold_only=false>
49
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELS&keyword_comment=LEVELS&hold_only=false>
15
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELS&keyword_wgnotes=TEAMA>
1
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELS&keyword_wgnotes=TEAMB>
3
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=LEVELS&keyword_wgnotes=EDITORZ>
4.1.1
24
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=4.1.1&hold_only=false>
25
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=4.1.1&keyword_comment=4.1.1&hold_only=false>
24
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=4.1.1&keyword_wgnotes=TEAMA>
CONFORMANCE
35
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONFORMANCE&hold_only=false>
113
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONFORMANCE&keyword_comment=CONFORMANCE&hold_only=false>
27
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONFORMANCE&keyword_wgnotes=TEAMA>
3
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONFORMANCE&keyword_wgnotes=TEAMB>
1
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONFORMANCE&keyword_wgnotes=TEAMC>
4
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=CONFORMANCE&keyword_wgnotes=EDITORZ>
BASELINE
70
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=BASELINE&hold_only=false>
101
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=BASELINE&keyword_comment=BASELINE&hold_only=false>
52
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=BASELINE&keyword_wgnotes=TEAMA>
5
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=BASELINE&keyword_wgnotes=TEAMB>
9
<http://www.w3.org/WAI/GL/WCAG20/issue-tracking/advanced_search_results.php?
keyword_title=BASELINE&keyword_wgnotes=EDITORZ>
REMEMBER – you don't need to necessarily solve the puppy. Just be sure to
have a good summary so we can discuss the key issues.
Thanks.
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
The Player for my DSS sound file is at http://tinyurl.com/dho6b
<http://trace.wisc.edu:8080/mailman/listinfo/>
SAMPLE SUMMARY LISTING OF ISSUES. (2 ISSUES IN THIS CASE - WITH 4 MORE
RELATED CASES)
ALL 6 are LISTED. IF YOU LOOK PAST THE FIRST TWO – YOU SEE WHY WE NEED TO
EXAMINE ALL RELATED ITEMS – NOT JUST THE TWO THAT GOT LABELLED 4.1.2 IN THIS
CASE.
==============
LC-912 <http://www.w3.org/2006/02/lc-comments-tracker/35422/wcag20-lc/912>
Giorgio Brajnik giorgio@dimi.uniud.it
... all user interface components...: you mean that each single DOM element
that has perceivable effects on some user needs to have name and roles
defined? eg every <p>?
=============
LC-1062 <http://www.w3.org/2006/02/lc-comments-tracker/35422/wcag20-lc/1062>
Gian Sampson-Wild gian@tkh.com.au
4.1.2: What is the "name" or the "role"? What does it mean "values can be
set by the user"?
Proposed Change:
Rewrite SC 4.1.2
=============
LC-587 <http://www.w3.org/2006/02/lc-comments-tracker/35422/wcag20-lc/587>
Jim Thatcher <jim@jimthatcher.com>
Part of Item:
Comment Type: TE
Comment (including rationale for proposed change):
I am doing final copy editing of a book chapter on forms.
I had talked about how clear the January version of WCAG20 was about forms:
SC 4.1.3 The label of each user interface control in the Web content that
accepts input from the user can be programmatically determined and is
explicitly associated with the control.
But now that has apparently been replaced by:
SC 4.1.2 For all user interface components, the name and role can be
programmatically determined, values that can be set by the user can be
programmatically set, and notification of changes to these items is
available to user agents, including assistive technologies.
The problem is that 4.1.2 is absolutely inadequate. The \"Role\" of text
input field is \"text input\"; the name could be \"keyinput\". 4.1.2 is
basic software accessibility - leaving to the AT the process of figuring out
what the prompt (label) is.
I just talked with John (who sounds terrific) and he pointed out that -
1.3.1 Information and relationships conveyed through presentation can be
programmatically determined, and notification of changes to these is
available to user agents, including assistive technologies.
Served the same purpose as 4.1.3 - I agree. But it is abstract. It requires
interpretation.
With the Last Call version of WCAG 2.0 there is no success criterion that
specifically addresses labeling forms and I think that is a very serious
mistake.
Proposed Change:
Please reinstate 4.1.3.
WG COMMENTS
[TEAMC] [HOLD]
See proposal at
http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jun/0036.html
discussed by Team C on 19 June 2006.
(Part of this proposal was to add a "failure due to omitting labels
for form controls for item selection or text input".)
The definition of "relationships" is also relevant; see thread starting at
http://lists.w3.org/Archives/Public/w3c-wai-gl/2006AprJun/0357.html
previous proposal:
[PARTIAL]
@@change wording of 4.1.2 to "For all user interface components, the name,
role, perceivable properties and relationships can be programmatically
determined, values that can be set by the user can be programmatically set,
and notification of changes to these items is available to user agents,
including assistive technologies."
@@respond with: "Labels for form controls are covered by SC 1.3.1, except
for labels that are not visible. For this reason we have merged the text of
SC 4.1.3 from the January 2006 draft with the current text of SC 4.1.2. This
also means all of the 'programmatic control' provisions are now together."
--
Discussed on the 22 June 2006 teleconference
Resolution: Do not accept the proposed resolution for LC-587. Action item
to Gregg, Bruce, Becky to see if it can be made clearer that 1.3.1
http://www.w3.org/WAI/GL/2006/06/22-wai-wcag-minutes.html
Bruce adds: There is also some disconnect between SC 1.3.1/4.1.2 and §508
1194.22(n) which reads:
When electronic forms are designed to be completed on-line, the form shall
allow people using assistive technology to access the information, field
elements, and functionality required for completion and submission of the
form, including all directions and cues.
The “all directions and cues” portion of the above was more directly
addressed by the deleted 4.1.3 that Jim is writing about.
LC-654
<http://www.w3.org/2006/02/lc-comments-tracker/35422/understandingwcag20/654
> Johannes Koch koch@w3development.de
Part of Item: Common Failures
Comment Type: TE
Comment (including rationale for proposed change):
While there are two HTML techniques about labeling form controls--\"H44
(Using label elements to associate text labels with form controls)\" and
\"H65 (Using the title attribute to identify form controls when the label
element cannot be used)\"--there is no common failure about _not_ labeling
form controls. This also applies to 4.1.2.
Proposed Change:
Add a common failure about not labeling form controls.
Wg notes
[TEAMC]
DONE change test procedure in H44 to:
For all input elements of type text, file or password, for all textareas and
for all select elements in the Web unit:
1. check that there is a label element that identifies the purpose of the
control before the input element;
2. check that the for attribute of the label element matches the id of
the input element.
For all input elements of type checkbox or radio in the Web unit:
1. check that there is a label element that identifies the purpose of the
control after the input element;
2. check that the for attribute of the label element matches the id of
the input element.
Discussed in the 20 July 2006 telecon:
Resolution: Accept proposal for LC-654 as ammended to reference SC 1.3.1.
http://www.w3.org/2006/07/20-wai-wcag-minutes.html
DONE (28 July 2006) add "Failure of SC 1.3.1 and 4.1.2 due to omitting
labels for form controls for item selection or text input"
Proposed technique is available at
http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jul/0018.html
RESOLVED
RESOLUTION
Thank you for pointing out the missing failure. We will add a "Failure of
SC 1.3.1 due to omitting labels for form controls for item selection or text
input".
===================
LC-935 <http://www.w3.org/2006/02/lc-comments-tracker/35422/wcag20-lc/935>
Andi Snow-Weaver <andisnow@us.ibm.com>
Repurposed widgets require the user to have state information as well. For
example, if a <div> is used to make a checkbox you would need to know if it
were checked or not. States, properties, and values need to be
programmatically determinable.
Proposed Change:
Change 4.1.2 to "For all user interface components, the name and role can be
programmatically determined, states, properties, and values that can be set
by the user can programmatically determined and set, and notification of
changes to these items is available to user agents, including assistive
technologies."
WG NOTES:
[TEAMA]
Propose to accept Andi's proposal.
BBC: editorial nit (missing "be") and copied below.
Discussed in the 13 July 2006 telecon:
Accepted by unanimous consent.
http://www.w3.org/2006/07/13-wai-wcag-minutes.html
RESOLVED
RESOLUTION:
{accept}
@@ Change 4.1.2 to "For all user interface components, the name and role can
be programmatically determined, states, properties, and values that can be
set by the user can be programmatically determined and set, and notification
of changes to these items is available to user agents, including assistive
technologies."
Respond with:
The success criterion has been updated as proposed.
===========================
LC-1173 <http://www.w3.org/2006/02/lc-comments-tracker/35422/wcag20-lc/1173>
Greg Lowney gcl-0039@access-research.org
4.1.2 includes the phrase "available to user agents, including assistive
technologies", but other criteria say "available to user agents" without the
"including assistive technologies". The phrase is not strictly required
since we define user agents as including assistive technologies; you may
feel it's useful to re-emphasize that here, but if that's the case, wouldn't
it also be warranted in those criteria that say "programmatically..." by
adding "including assistive technology" to the definitions of
programmatically set and programmatically determined?
Proposed Change:
Delete the phrase ", including assistive technologies", to read "For all
user interface components, the name and role can be programmatically
determined, values that can be set by the user can be programmatically set,
and notification of changes to these items is available to user agents."
=============================
Received on Sunday, 30 July 2006 15:25:35 UTC