- From: Wendy Chisholm <wendy@w3.org>
- Date: Thu, 18 Nov 2004 13:52:41 -0500
- To: David MacDonald <befree@magma.ca>
- Cc: w3c-wai-gl@w3.org
David, Thank you for the quick and thorough analysis. > 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? > The primarily issue is not the lack of font support, the issue is using CSS instead of raster based images of text. So, I mapped it to Guidelien 1.3. For the time being, mapping the SC to "UNKNOWN" although it might map to emphasis. > 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. > Added ednote. Will create bug after publication. > 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” > Linked to 1.3, added ednote, will add bug after publication. > 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 > Linked to 1.3, added ednote, will add bug after publication. > 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]” > Linked to guideline 3.1 and the first Level 1 criterion. Will need to add a bug about this. It's not a perfect fit. > *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. > linked to 1.3. will add bug later. > *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. > linked to 1.3, will add bug later. > *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] > done. > *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. > added 1.3, bug later > *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. > added 1.3, bug later no change to all of those that are placeholders. Thank you, --wendy -- wendy a chisholm world wide web consortium web accessibility initiative http://www.w3.org/WAI/ /--
Received on Thursday, 18 November 2004 18:52:50 UTC