W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2004

[TECHS] CSS links to Guidelines as per Action item

From: David MacDonald <befree@magma.ca>
Date: Wed, 17 Nov 2004 16:54:09 -0500
Message-Id: <200411172154.iAHLs9IA025374@mail3.magma.ca>
To: <w3c-wai-gl@w3.org>, <wendy@w3.org>
Hi Wendy 

 

Here re is my action item from this morning's  Techniques call. There are
some links that can be added easily and are noted below. I've also suggested
editor notes and new bugs that would have had to been filed later anyway.
The exercise dovetails well with the End to End work and shows some of the
holes we still have between the Tech docs and the Guidelines.

_________________________________________________________________

 

2.1 (use span for Drop Caps - not all fonts available in User agents) 

 

It links to: 

A) Principle 1: "Content must be perceivable"        

B) Principle 4: "Content must be robust enough to work with current and
future technologies." 

 

Add editor note to CSS 2.1:  "There is currently no guideline or SC
currently to link to" 


New Bug for CSS 2.1: 

- there are no Guidelines and no success criterion that would be a direct
hit, only the top level Principles above.

- Is this is a "repair technique" because user agents aren't providing
enough fonts or do we need to provide a list of good font families to
webmasters or do we need to add a SC in the Guidelines about legit
limitations of agents?

________________________________________________________________

 

2.2 Accessing alternative representations of content

Links to:

Principle 1: "Content must be perceivable"  

 

Add editor note to CSS 2.2:  "There is currently no guideline or SC
currently to link to" 

            

 

New Bug for CSS 2.2

-- there are no Guidelines and no success criterion that would be a direct
hit, only the top level Principle.

 

_________________________________

 

4.1 Creating borders (using CSS rather than tables)

 

Link to:

Guideline 1.3 Ensure that information, functionality, and structure are
separable from presentation.

 

Add editor note to CSS 4.1:  "There is currently no SC to link to" 

 

 

New Bug for CSS 4.1

-- There is no success criterion that would be a direct hit. SC. 1.2
"Emphasis can be programmatically determined. [I]" kind of applies but not
really. 

 

_________________________________

 

4.2 Margins

Link to:

1) Guideline 1.3 Ensure that information, functionality, and structure are
separable from presentation.

 

New Bug for CSS 4.2

-- There is no success criterion that would be a direct hit. SC. 1.2
"Emphasis can be programmatically determined. [I]" kind of applies but not
really

 

____________

 

5.1 Specifying the direction of text

 

Link to:

Guideline 3.1 Ensure that the meaning of content can be determined

 

Add editor note to CSS 5.1:  "There is currently no SC to link to" 

 

 

New Bug for CSS 5.1

-There is no success criterion that would be a direct hit.  SC 2.3 Is close
"For each foreign language passage or phrase in the body of the content, the
language is identified through markup or other means. Foreign passages or
phrases are passages or phrases that are in a language other than the
primary language of the document. [I]" 

 

____________

 

5.3 Positioning (float, position)

 

Link to:

1) Guideline 1.3 Ensure that information, functionality, and structure are
separable from presentation.

 

New Bug for CSS 5.3

-- There is no success criterion that would be a direct hit.

________________________

 

5.4 Hiding and showing content

 

Placeholder

______________________

 

6.2 Providing additional structural information

 

Link to:

1) Guideline 1.3 Ensure that information, functionality, and structure are
separable from presentation.

 

New Bug for CSS 6.2

-- There is no success criterion that would be a direct hit.

 

__________________________

 

8.3 Specifying font sizes using xx-small to xx-large

Placeholder

______________________

 

9.6 Creating shadow effects (deprecated)

Deprecated

________________________

 

10.1 Displaying empty table cells (do not use characters to get white space)

 

Link to:

Principle 4: Content must be robust enough to work with current and future
technologies.

Guideline 4.1 Use technologies according to specification.

1.	SC 3.1 Technologies are used according to specification without
exception. [V] 

__________________________

11.1 Outlining content

 

Link to:

1)       Guideline 1.3 Ensure that information, functionality, and structure
are separable from presentation.

 

New Bug for CSS 11.1

-- There is no success criterion that would be a direct hit.

 

____________________

 

13.1 Providing structural markup for graceful degradation

 

Link to:

2)       Guideline 1.3 Ensure that information, functionality, and structure
are separable from presentation.

 

New Bug for CSS 11.1

-- There is no success criterion that would be a direct hit.

 

___________________________

 

13.2 & 13.3 are placeholders

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 
Received on Wednesday, 17 November 2004 21:54:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:32 GMT