Re: WCAG2-ATAG2 Harmonization (Glossary Terms)

We should make sure that ATAG2.0 satisfies the Quality Assurance Framework
Specficiation Guidelines (QASpecGL) Requirement -
"Define the terms used in the normative parts of the specification" [1].

Per the following, there is also QASpecGL Good Practice 10, which says:
"Use terms already defined without changing their definition."   If we 
change the
definitions from WCAG use, perhaps we should document the reasons why.

Thanks and best wishes
Tim Boland NIST

PS - There is also Good Practice 9, which says
"Define unfamiliar terms in-line and consolidate the definitions in a 
glossary section."
We should make sure we're doing that we're defining unfamiliar terms as 
needed in ATAG2.0..


[1]http://www.w3.org/TR/qaframe-spec/#define-terms-principle
[2]http://www.w3.org/TR/qaframe-spec/#reuse-terms-gp
[3]http://www.w3.org/TR/qaframe-spec/#define-terms-inline-gp

At 04:34 PM 5/14/2008 -0400, you wrote:

>Jeanne and I have an action to review places where WCAG2 and ATAG2 are 
>supposed to be harmonized but that may be unharmonized due to last minute 
>WCAG2 changes. Here I have begun by looking at the Glossaries.
>
>(Major formatting difference between the 2 docs is WCAG's use of "Notes")
>
>Here are the "Harmonized Terms":
>
>abbreviation:
>- minor changes would probably be enough
>- harmonization was originally incomplete due to WCAG Notes
>
>ASCII art:
>- OK
>
>assistive technology:
>- harmonization was originally incomplete due to WCAG Notes
>
>audio description:
>- harmonization was originally incomplete due to WCAG Notes
>
>blink:
>- minor changes would probably be enough
>- uses Notes
>
>captions:
>- harmonization was originally incomplete due to WCAG Notes
>
>change of context:
>- major changes required
>- uses Notes
>
>text alternative:
>- some changes required
>
>full text alternative for synchronized media including any interaction:
>- OK
>
>flash:
>- minor changes would probably be enough
>- uses Notes
>
>general flash and red flash thresholds:
>- major changes required
>- uses Notes
>
>informative:
>- OK
>- harmonization was originally incomplete due to WCAG Notes
>
>label:
>- OK
>- harmonization was originally incomplete due to WCAG Notes
>
>name:
>- OK
>- harmonization was originally incomplete due to WCAG Notes
>
>non-text content:
>- OK
>- harmonization was originally incomplete due to WCAG Notes
>
>normative:
>- OK
>- harmonization was originally incomplete due to WCAG Notes
>
>presentation:
>- minor changes would probably be enough
>
>relationships:
>- OK
>
>relative luminance:
>- minor changes would probably be enough
>- HERE WE USE SAME WCAG NOTE STRUCTURE!
>
>role:
>- OK
>
>synchronized media:
>- OK i think but we leave out "unless the media is a media alternative for 
>text that is clearly labeled as such"
>
>technology (Web content):
>- OK
>- harmonization was originally incomplete due to WCAG Notes
>
>user agent:
>- OK
>
>user interface component:
>- missing Note information
>
>video:
>- OK
>- since we have this we may want to add AUDIO
>
>
>
>
>Cheers,
>Jan
>
>
>--
>Jan Richards, M.Sc.
>User Interface Design Specialist
>Adaptive Technology Resource Centre (ATRC)
>Faculty of Information Studies
>University of Toronto
>
>   Email: jan.richards@utoronto.ca
>   Web:   http://jan.atrc.utoronto.ca
>   Phone: 416-946-7060
>   Fax:   416-971-2896
>
>
>

Received on Thursday, 15 May 2008 15:08:41 UTC