W3C home > Mailing lists > Public > wai-xtech@w3.org > August 2002

RE: Implementation Technique Numbering

From: Haritos-Shea, Katie <sheak@milvets.com>
Date: Wed, 14 Aug 2002 11:34:37 -0400
Message-ID: <B10D84032BF1D311A32800A0CC595EDF3D655A@MSTNTS2>
To: "'Jan Richards'" <jan.richards@utoronto.ca>
Cc: "3WC WAI X-TECH (E-mail)" <wai-xtech@w3.org>, "_W3C WAI AU (E-mail)" <w3c-wai-au@w3.org>

Jan,

Restating what I suggested in March (with the inclusion of possible er and
xag checkpoint #s) 
this an idea for relevent numbering:
		
    a(checkpoint#)- t(technique#)  =(or~)  w(WCAG checkpoint#) (space)
Priority Level

Where:
    a = atag checkpoint
    u = uaag checkpoint
    w = wcag checkpoint
    e = er checkpoint (?)
    x = xag checkpoint
    P = priority level
    t = technique number
 
    a(ATAG checkpoint#)- t(technique#)  =(or~)  w(WCAG checkpoint#) (space)
Priority Level......RESOLVES TO THIS..........

    a3.2-t1=w5.2 P1

	or

    a1.3-t2~w2.1 P1

	or

    a6.4.1-t2=w3.2 P1



    But for ATAG 1.1, which is not relative, it would be:

    a1.1-t3

(in the main guidelines this could be used as:
    a3.2=w5.2  P1)


I think the use of lowercase letters makes the numbers easier to
determine, but that is just me. Stuck with uppercase for Priority Level
because that has been used all along.


If you are not doing a comparison per say, the technique number would just
be:

	a6.4.1-t10
	or
	w2.3-t4 P1


This convention could then possibly be used across all WAI checkpoints and
technique docs.

	u6.2-t1~w4.2 P2

		or

	w4.2-t14 P1~u6.5-t10

		or

	x2.2-t6~w4.2.5 P1


If you are not doing a comparison per say, the technique number would just
be:

w2.3-t4 P1

x2.2-t1 P2

	
I think I might be forgetting some of our past discussions on this, please
forgive my memory.
Hope you are well................................Katie
	



Katie Haritos-Shea
Assistive Technology/Section 508 
Program Manager, MILVETS

mailto:sheak@milvets.com
mailto:ryladog@earthlink.net
Direct: 301-731-1821
Voice: 301-731-9130
Fax: 301-731-4773

MILVETS Systems Technology, Inc.
4601 Forbes Boulevard
Suite 300
Lanham, Maryland
20706


"The best and most beautiful things in the world
     cannot be seen or even touched.
    They must be felt with the heart."
                - Helen Keller


Internet/Software/Device Accessibility and Standards
Strategist/Developer/Evangelist




-----Original Message-----
From: Jan Richards [mailto:jan.richards@utoronto.ca]
Sent: Wednesday, August 14, 2002 11:14 AM
To: Haritos-Shea, Katie
Subject: Implementation Technique Numbering


Katie,

Remember the ATAG implementation technique numbering proposal? Here are
my thoughts:

The "T####" method has become more and more untenable as techniques are
reordered, added, and removed. The resultant willy-nilly numbering
sequence is no help whatsoever when trying to find a technique.

Any attempt to give techniques new permanent numbers would be vulnerable
to the same problem.

I think that the best we can hope for is a
guideline#.checpoint#.technique# scheme (ex. 2.1.1) that changes as
techniques are moved around, added and deleted. At least it make editing
easier.

Your thoughts?

Cheers,
Jan

-- 
Jan Richards, User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC), University of Toronto

  Email: jan.richards@utoronto.ca
  Web:   http://ultrajuan.ic.utoronto.ca/~jan/jan.html
  Phone: 416-946-7060
  Fax:   416-971-2896
Received on Wednesday, 14 August 2002 11:36:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:15:37 GMT