- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 27 Sep 2007 11:15:52 -0500
- To: w3c-wai-gl@w3.org
- Message-id: <00b901c80121$ad0cb9a0$a117a8c0@NC84301>
Two proposals for today. This one is only informative material and
advisory techniques.
Note that Katie proposes two different organizations for listing the
advisory techniques.
Here at the top - she summarized what will be found below.
Metadata Proposal 2 for WCAG 2.0 (No Success Criteria):
Summary
IN WCAG
1 new paragraph
In Understanding Doc
* Add a short paragraph and link (just before the 'Understanding the
Four Principles of Accessibility' heading) to the Understanding Metadata
section.
* Add a 'Understanding Metadata' section
3.1.5 Reading Level
* Add metadata example for how to do this.
* Add Advisory Techniques (2)
* HTML Example:
* XML Example:
Advisory Techniques ONLY
Add HTML Techniques: (2 New)
* (for 1.1.1)
* (for 3.1.5)
Add: New Heading Section:
XML Techniques: (2)
(for 1.1.1)
(for 3.1.5)
AND/OR
Add: New Heading Section:
Metadata Techniques: (4)
(for 1.1.1)
(for 3.1.5)
Notes
All examples and techniques are created using metadata from already fully
approved and
implemented international metadata standards.
Currently standards these are:
ISO IEC 24751 series - "Access for All" (2005)
I note that although the new metadata approach was developed for education,
it is generally applicable, and is so considered by the Dublin Core
metadata community.
For further details, please see:
http://www.imsglobal.org/accessibility (a number of documents available)
http://jtc1sc36.org/doc/36N1141.pdf (a nearly final version of the standard
to be released very soon by ISO)
http://dublincore.org/groups/access (a generalised approach to AccessforAll
metadata)
****************************************************************************
*************
****************************************************************************
*************
********
DETAILS
********
---------
WCAG Document
---------
FIRST Part of Proposal 2 (for WCAG Document):
To:
Web Content Accessibility Guidelines 2.0
(http://www.w3.org/WAI/GL/WCAG20/)
Introduction
Add: as last new paragraph (after the bulleted list).......
One other emerging and important component of achieving web accessibility is
the proper use
of standardized metadata. It is known that metadata can be useful in
bringing together people and relevant resources. There are several
recognized metadata standards which can be used to (among other things);
find alternative content and provide conformance claims. WCAG 2.0 has
provided general guidance and techniques for using metadata to improve
accessibility of web content.
****************************************************************************
***************
-----------------
Understanding Doc
-----------------
SECOND Part of Proposal 2 (for Understanding Doc):
To:
Understanding WCAG 2.0
A guide to understanding and implementing WCAG 2.0
(http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20/)
Table of Contents: (Links)
Understanding Metadata (put after 'Understanding Conformance' link)
Introduction to Understanding WCAG 2.0:
Add a short paragraph and link (just before the 'Understanding the
Four Principles of Accessibility' heading) to the Understanding Metadata
section.
Add:
A new 'Understanding Metadata' section
Accessibility information in metadata can be utilized by browsers, indexing,
search agents
and web services to bring people and relevant resources together.
Metadata is a technical name for the description that is machine readable
of some data . This usually means it is a formally structured description.
There are a number of formalities for such metadata, some aimed towards the
sort of descriptions people use for books in libraries, and some focused on
specific aspects of the data, or resource, as it is commonly known. Like
catalog records, metadata does not have to be part of the resource but it
can be attached to it by being included, like the label on a tin of food, or
stored somewhere else for convenience and searching. It is often useful to
know who made the description, and when, especially if the resource is
likely to have changed. Descriptions of resources are useful to
users because they can find out, without having to see the resource itself,
if it is going to satisfy their needs. In the case of accessibility needs,
knowing the exact attributes of the resource of concern to an individual
might help them choose what suits them even
when it may not suit everyone.
......Explanation in simple terms will continue here that discusses history,
state of
metadata stanadrds now, and what authors should do to implements..........
Main points to emphasise:
* metadata is necessary to find accessible resources
* the AccessForAll approach is good for authenticating sites etc ie
metadata for resource and user
* metadata supports WCAG and complements it in 2 ways - helps individuals
find what THEY need and publishers to target users more exactly and esp
helps when a resource is not universally accessible...
* metadata supports individual users not just a community with similar
assumed needs and
prefs
* metadata allows for needs AND prefs - not all users treated the same
* metadata very good for accessibility experts adding special components to
make existing
resources more accessible
* metadata makes personal optimisation possible
* avoids the problem that optimisation for some users may make resources
inaccessible for others
* allows dynamically varying requirements as environment changes
* bridges the gap between product design and contexts of use (not only
device contexts)
* responds to individual user's precise need/preference instead of guessed
generic requirements
-----------------------------------------------------------------
-------------------
3.1.5 Reading Level
-------------------
THIRD Part of Proposal 3 (for Understanding Doc):
To:
Understanding Success Criterion 3.1.5 [Reading Level]
http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20/meaning-supplements.
html
Add:
Examples of Success Criterion 3.1.5
Metadata Examples of Success Criterion 3.1.5
HTML Example: Providing, in metadata, URL(s) that point to a
pre-primary-reading-level and a primary-reading-level text transcript of a
new scientific discovery advanced-reading-level article.
XML Example: Providing, in metadata, URL(s) that point to a
pre-primary-reading-level and a primary-reading-level text transcript of a
new scientific discovery advanced-reading-level article.
Techniques and Failures for Success Criterion 3.1.5 [Reading Level]
Add to:
Additional Techniques (Advisory) for 3.1.5
After 5th bullet...
"Using the Dublin Core accessibility element to associate text content
with text, graphical, or spoken supplements (future link)"
Add bullet
"Using the ISO AfA accessibility element to associate text content with
text, graphical, or spoken supplements (future link)"
Add bullet
"Using the IMS accessibility element to associate text content with
text, graphical, or spoken supplements (future link)"
and
Making metadata viewable by humans (future link)
****************************************************************************
************
--------------
Techniques Doc
--------------
FOURTH Part of Proposal 2 (for Techniques Doc):
To:
Techniques for WCAG 2.0
Techniques and Failures for Web Content Accessibility Guidelines 2.0
(http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS/)
Add:
Advisory Techniques (ONLY)
HTML Techniques: (New)
(for 1.1.1)
H80: Providing, in metadata, URL(s) that points to an audio descrition
and a text transcript of a video.
(for 3.1.5)
H81: Providing, in metadata, URL(s) that point to a
pre-primary-reading-level and a primary-reading-level text transcript of a
new scientific discovery advanced-reading-level article.
ADVISORY?
Add: New Heading Section(s):
XML Techniques:
(for 1.1.1)
XML10: Providing, in metadata, URL(s) that points to an audio
descrition and a text transcript of a video.
(for 3.1.5)
XML11: Providing, in metadata, URL(s) that point to a
pre-primary-reading-level and a primary-reading-level text transcript of a
new scientific discovery advanced-reading-level article.
AND/OR I prefer the one below
Metadata Techniques:
(for 1.1.1)
M1: HTML Example: Providing, in metadata, URL(s) that points to an
audio description and a text transcript of a video.
M2: XML Example: Providing, in metadata, URL(s) that points to an
audio description and a text transcript of a video
(for 3.1.5)
M3: HTML Example: Providing, in metadata, URL(s) that point to a
pre-primary-reading-level and a primary-reading-level text transcript of a
new scientific discovery advanced-reading-level article.
M4: XML Example: Providing, in metadata, URL(s) that point to a
pre-primary-reading-level and a primary-reading-level text transcript of a
new scientific discovery advanced-reading-level article.
END Proposal 2
****************************************************************************
***************
* katie *
Katie Haritos-Shea
Section 508 Technical Policy Analyst
703-371-5545
People may forget exactly what it was that you said or did,
but they will never forget how you made them feel.......
Received on Thursday, 27 September 2007 16:16:36 UTC