W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2001

Re: Sufficiency/checkpoint satisfaction criteria (repost of last week's draft)

From: Anne Pemberton <apembert@erols.com>
Date: Mon, 9 Jul 2001 07:04:35 -0400
Message-ID: <001a01c10867$07ee5c80$2427accf@stevepem>
To: <jasonw@ariel.ucs.unimelb.edu.au>, "Web Content Guidelines" <w3c-wai-gl@w3.org>
WCAG 2.0 notes: sufficiency criteriaJason,

            Read through your criteria and focused on Guideline 3 as usual.

            Yes, swap 3.1 and 3.2 .... I noticed when I tried to illustrate these guidelines that they were in reverse logical order.

            You did a good job with 3.3 .... 

            But 3.4 needs more work. The most important point to be made is that illustrations MUST be present if the page is to be considered accessible. That doesn't come across yet. 

  ----- Original Message ----- 
  From: Jason White 
  To: Web Content Guidelines 
  Sent: Monday, July 09, 2001 8:42 PM
  Subject: Sufficiency/checkpoint satisfaction criteria (repost of last week's draft)
  Guideline 3
  Checkpoint 3.1: 

    1.. Each type of structural element occurring in the logical structure of the content (see checkpoint 1.4), for example headings, tables, user interface controls etc., must be presented using the same formatting and layout conventions throughout a document or web site, as the case may be. 
  Checkpoint 3.2. With respect to each media type (in the CSS sense, e.g., screen, print, aural) for which you provide style sheets or other control over presentation: 

    1.. Each type of structural element (see checkpoint 1.4) occurring in the logical structure of the content, must be reflected in the presentation via a specific style or combination of style properties (this terminology does not imply that style sheets must be used, but only that specific and identifiable style properties be associated with each type of structural element). 
    2.. The place of a structural element within the hierarchy (e.g., the level of a heading within a document), where this information is significant in conveying the over-all structure of the content, must be assigned a distinct style. 
  Checkpoint 3.3. Here we go! 

    1.. The language used must be no more complex than that which members of the intended audience can be reasonably expected to comprehend. In identifying the intended audience, consideration should be given to the range of educational levels and anticipated background of individuals who are likely to be interested in reading the content, to the level of detail at which you propose to provide the information. 
    2.. Terminology which may not be familiar to members of the intended audience, and which may create obstacles to understanding, must be clearly explained and defined. 
  Checkpoint 3.4: 

    1.. Illustrations must be designed to portray important concepts or relationships employed in the content. 
    2.. Where appropriate, illustrations should be referred to in the text (e.g., in a caption or as part of the textual exposition), to provide the reader with an appropriate context in which to interpret the illustration. 
  Checkpoint 3.5: Where a yet to be defined complexity threshhold is exceeded: 

    1.. Provide a summary which clearly conveys the main ideas or relationships expressed in the content. 
    2.. Where the markup or data model allows, the summary should be associated explicitly with the content that it is intended to summarize. 
  Checkpoint 3.6: 

    1.. Abbreviations, acronyms and terms which occur frequently in the content, or which need to be understood in order to comprehend the main concepts or ideas expressed in the content, must be defined. 
    2.. Where the markup or data model permits, the abbreviations/acronyms and their expansions, and the terms and their definitions, respectively, must be explicitly associated with each other. 
  Where the size of a unit according to some ill-defined complexity threshold is too great, it must be divided up. This is really vague.
Received on Tuesday, 10 July 2001 07:10:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:38 UTC