W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2001

Re: Issue 324: Proposal for revised checkpoint 6.2

From: Jon Gunderson <jongund@uiuc.edu>
Date: Tue, 02 Jan 2001 08:37:10 -0600
Message-Id: <4.3.1.2.20010102083547.0139adc8@staff.uiuc.edu>
To: "David Poehlman" <poehlman1@home.com>, "Ian Jacobs" <ij@w3.org>, <w3c-wai-ua@w3.org>
David,
My understanding is that 6.2 was only for content.  What type of user 
interface uses a markup language that the group has an understanding of the 
accessibility issues?

Jon


At 10:33 AM 12/28/2000 -0500, David Poehlman wrote:
>as I originall read this it was for ui as well as content.  It seems
>that it is only for content as Ian Pointed out to me so that being the
>case, I'm not sure we can require p2.
>
>----- Original Message -----
>From: "Jon Gunderson" <jongund@uiuc.edu>
>To: "Ian Jacobs" <ij@w3.org>; <w3c-wai-ua@w3.org>
>Sent: December 28, 2000 10:17 AM
>Subject: Re: Issue 324: Proposal for revised checkpoint 6.2
>
>
>Ian,
>I like the new checkpoint.  How do you feel about making the
>requirement to
>conform to WCAG 1.0 at a P2 requirement.  I would use the same
>argument for
>P2 as the group used to make documentation conformance a P2 level.
>
>Jon
>
>
>At 01:50 PM 12/27/2000 -0500, Ian Jacobs wrote:
> >Hello,
> >
> >Per my action from the 16 November face-to-face meeting [1],
> >please consider this proposed change to checkpoint 6.2.
> >
> > >From the 23 October draft [2]:
> >
> >   6.2 Use and conform to W3C Recommendations when they are
> >       available and appropriate for a task. [Priority 2]
> >
> >       Note: For instance, for markup, conform to HTML 4 [HTML4],
>XHTML
> >       1.0 [XHTML10], or XML 1.0 [XML]. For style sheets, conform to
> >       CSS ([CSS1], [CSS2]). For mathematics, conform to MathML
> >       [MATHML]. For synchronized multimedia, implement SMIL 1.0
> >       [SMIL]. For information about programmatic access to HTML and
> >       XML content, refer to guideline 5. User agents may conform to
> >       other specifications in addition to those required by this
> >       checkpoint. For reasons of backward compatibility, user agents
> >       should continue to implement deprecated features of
> >       specifications. Information about deprecated language features
> >       is generally part of the language's specification.
> >
> >The discussion points at the face-to-face meeting were
> >the following:
> >
> >1) It's a P2 issue to implement W3C specifications, or if
> >    you don't, implement formats that allow conformance to
> >    WCAG 1.0 (at any level of conformance).
> >
> >2) It's a P2 issue to conform to a spec, not just
> >    to implement it incompletely.
> >
> >3) It's important to support deprecated features, but
> >    this will not a requirement of UAAG 1.0 (per our resolution).
> >
> >4) It's important to implement the latest version,
> >    but developers should consider supporting the version that
> >    has the latest accessibility features. [This is for Techniques]
> >
> >5) One reviewer requested a clearer statement of
> >    what "available" means.
> >
> >Putting these together:
> >
> ><NEW>
> >   6.2 Use and conform to either (1) W3C Recommendations when they
>are
> >       available and appropriate for a task, or (2) non-W3C
> >       specifications that enable the creation of content that
> >       conforms to the Web Content Accessibility Guidelines 1.0
> >       [WCAG10] at any conformance level. [Priority 2]
> >
> >       Note: For instance, for markup, conform to HTML 4 [HTML4],
>XHTML
> >       1.0 [XHTML10], or XML 1.0 [XML]. For style sheets, conform to
> >       CSS ([CSS1], [CSS2]). For mathematics, conform to MathML
> >       [MATHML]. For synchronized multimedia, implement SMIL 1.0
> >       [SMIL]. A specification is considered "available" if it is
> >       published (e.g., as a W3C Recommendation) in time for
> >       integration into a user agent's development cycle.
> ></NEW>
> >
> >For the techniques (in addition to other points):
> >
> >1) For reasons of backward compatibility, user agents should continue
> >to implement deprecated features of specifications. Information about
> >deprecated language features is generally part of the language's
> >specification.
> >
> >2) If more than one version or level of a specification is
>appropriate
> >for a particular task, user agents are encouraged to conform to the
> >latest version. However, developers should consider implementing the
> >version that best supports accessibility, even if this is not the
> >latest version.
> >
> >  - Ian
> >
> >[1] http://www.w3.org/WAI/UA/2000/11/minutes-20001116#issue-324
> >[2] http://www.w3.org/TR/2000/WD-UAAG10-20001023/
> >
> >--
> >Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
> >Tel:                         +1 831 457-2842
> >Cell:                        +1 917 450-8783
>
>Jon Gunderson, Ph.D., ATP
>Coordinator of Assistive Communication and Information Technology
>Division of Rehabilitation - Education Services
>MC-574
>College of Applied Life Studies
>University of Illinois at Urbana/Champaign
>1207 S. Oak Street, Champaign, IL  61820
>
>Voice: (217) 244-5870
>Fax: (217) 333-0248
>
>E-mail: jongund@uiuc.edu
>
>WWW: http://www.staff.uiuc.edu/~jongund
>WWW: http://www.w3.org/wai/ua
>

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL  61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: jongund@uiuc.edu

WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua
Received on Tuesday, 2 January 2001 09:35:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:29 UTC