See also: IRC log
akim, this will be AUWG
zakim code?
AM: Ann can attend by teleconference
<scribe> ACTION: JR to Announce the F2F data and time [recorded in http://www.w3.org/2009/04/20-au-minutes.html#action01]
<trackbot> Created ACTION-140 - Announce the F2F data and time [on Jan Richards - due 2009-04-27].
http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0010.html
JR B.2.4 Assist authors with maintaining alternative content fornon-text objects.
Rationale: Improperly generated alternative content can create
accessibility problems and interfere with accessibility checking.
JT: B.2.4 Assist authors with managing alternative content for non-text objects.
B.2.4.1 Editable: Authors are able to modify alternative content for
non-text objects. This includes types of alternative content that may
not typically be displayed on screen by user agents.
B.2.4.2 Automated suggestions: During the authoring session, the
authoring tool can automatically suggest *alternative content* for
non-text objects under the following conditions:
- author control: authors have the opportunity to accept, modify, or
reject the suggested *alternative content* prior to insertion.
- relevant sources: the suggested *alternative content* is only derived
from sources designed to be fulfill the same purpose (e.g., suggesting
the value of an image's "description" metadata field as a long description).
B.2.4.3 Let user agents repair: After the authoring session, the
authoring tool does not attempt to repair *alternative content* for
non-text objects using text content that is equally available to user
agents (e.g., the filename). (Level A)
B.2.4.4 Special Values: The authoring tool follows recommendations on
special values for *alternative content* (e.g., in HTML4 alt="" denotes
images that should be ignored by assistive technology). (Level A)
B.2.4.5 Save for Reuse: Provide authors with the option of having
any *recognized* plain text alternative content that they enter (e.g.,
short text labels, long descriptions) stored for future reuse (Level AA).
Applicability Note:
- This guideline applies when non-text objects are specified by
authors (e.g., an author inserts an image). When non-text objects are
automatically added by the authoring tool, Guideline B.1.3 applies.
http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0016.html
To help people understand the implications of the proposal
(http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0010.html),
here's an example workflow of a person uploading a bunch of images to a
photo-sharing site:
1. author logs into the photo sharing site
2. author uses the uploader feature to upload 50 pics of a vacation
(XYZ0001.png, XYZ0002.png,..., XYZ0050.png) into an album the author
calls "Paris 2009".
3. a prompt appears asking the author to write descriptive labels for
each image to facilitate text searching and access by people with
disabilities. [This meets B.2.1.1 (prompting for accessibility info.
req.) and also B.2.4.1.]
4. Since no label or description is included in the photo metadata no
default @alt value is provided. [meeting B.2.4.2]
5. the author logs off without adding individual text alternatives
(ending their "authoring session")
6. the photo sharing site assigns the @alt strings "Photo 1 of 50 of
album Paris 2009" [meeting B.2.4.3 because this info isn't equally
available to user agents]
7. when the author logs back in they still see indicators on the images
and/or the album that reminds them that the images are still lacking
descriptive labels. [meeting B.2.2.1 (Check Accessibility req.)]
NOTE: the page will NOT meet WCAG 2.0 because the text alternative does
not serve the equivalent purpose - BUT REMEMBER there is no absolute
requirement of ATAG 2.0 that all user-specified content meet WCAG 2.0.
http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0010.html
<Greg> +1
Resolution: Put in the proposed B.2.4
http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0014.html
> appropriate version/spec..
All: Agree
CURRENT:
ATAG 2.0 defines an "authoring tool" as any application, part of an
application, or collection of applications that authors interact with to
create, modify or assemble Web content to be used by other people.PROPOSED:
ATAG 2.0 defines an "authoring tool" as any software application, part
of an application, or collection of applications that authors interact
with to create, modify or assemble Web content to be used by other people.
All: Agree
CURRENT:
- WYSIWYG editors, plain text editors (embedded and stand-alone)
PROPOSED:
- WYSIWYG editors, plain text editors
All: OK
GP: Actually...
... OK
Content => Web Content
All: OK
PROPOSED:
APPLICATIONS THAT ARE USED TO CREATE CONTENT IN REAL TIME (e.g., chats,
collaboration tools, whiteboards, etc.) are only required to meet Part
A. However, many guidelines in Part B may still usefully apply,
especially if the AUTHORING tool archives as Web content. For more
information, please see the Techniques - Appendix E: Real-time content
production.
All: OK
PROPOSED:
Generally use "authoring tool" instead of just "tool".
All: OK
functions related to accessibility=>accessible content support features
All: OK
> Relationship to the WCAG:
> Do we want to still list "WCAG1.0" after "e.g.", since WCAG2.0 is
> now a rec?
http://www.w3.org/TR/2009/WD-ATAG20-20090217/#intro-rel-wcag
JR: Concerns about older tools
GP: WCAG2 is the current standard
TB: WCAG group is trying to push adoption of next WCAG version
<Greg> wcag 2.0 only
TB: +1
AM: +1
JT: Brings up point of system
meeting wcag2 vs. all pages meeting wcag2
... WCAG2 takes the "every page" approach
<Greg> I also remembered more than just wysig and text required, template, command line driven
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: JR Inferring Scribes: JR Default Present: +44.208.123.aaaa, JR\, JR, SueAnn, Greg_Pisocky, JuttaT, Tim_Boland Present: +44.208.123.aaaa JR\ JR SueAnn Greg_Pisocky JuttaT Tim_Boland Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009AprJun/0017.html Got date from IRC log name: 20 Apr 2009 Guessing minutes URL: http://www.w3.org/2009/04/20-au-minutes.html People with action items: jr WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]