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

Continued Comments on WD-WCAG20-20020822

From: Brant Langer Gurganus <brantgurganus2001@cherokeescouting.org>
Date: Sat, 14 Dec 2002 12:47:15 -0500
Message-ID: <3DFB6EA3.7080403@cherokeescouting.org>
To: w3c-wai-gl@w3.org
http://www.w3.org/TR/2002/WD-WCAG20-20020822/


  Overview of Design Principles

    * How does assistive technology interpret "form(s)"?
    * Usage of "perceived" in the "Perceivable" definition is ambiguous.
    * The same applies to "Operable".
    * The same applies to "Navigable".
    * The same applies to "Understandable".
    * Item 3 needs a period at the end.
    * Should <q cite="http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/"> be
      around "How People with Disabilities Use the Web".?


  Guideline 1 - Perceivable.

    * Should "all intended function" be plural?
    * I would use a different word that "form(s)" because form can be
      confused with XForms or HTML forms or other input forms in
      general.  Perhaps "way(s)".


    Checkpoint 1.1

    * In item 2 under "Success Criteria", should "can not" be one word?
    * Shouldn't you have at least two items at each level of a list?
    * Should <span lang="la"> be around "i.e."?
    * I think there should be level headings or make the level names
      strong so they can be found at a glance.
    * Is there a reason that the examples are numbered and if so, should
      they be a numbered list with style :before { content: "Example" +
      number }?  I know that CSS syntax is wrong but you get the idea.

-- 
Brant Langer Gurganus
http://troop545.cjb.net/brant.htm


Received on Saturday, 14 December 2002 12:48:49 GMT

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