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

Re: Comments on Section 3.4 related to checkpoint grouping

From: Ian Jacobs <ij@w3.org>
Date: Thu, 12 Oct 2000 09:43:50 -0400
Message-ID: <39E5C016.8FDBCDEF@w3.org>
To: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
CC: w3c-wai-ua@w3.org
Jon Gunderson wrote:
> 
> Ian,
> 1.  We don't have minimal requirements for images on 8.2, 8.3, 4.15 and
> 4.16.  It seems like we should say something about that.  I think we should
> have for these checkpoints more of a description of why some element types
> have minimal requirements and other don't.  What do you think?

I'm not sure I understand. Can you give an example?

> 2. The labels part of section 3.4 are informational in nature.  The current
> wording "Portions of the following checkpoints related to" seems to
> indicate that the checkpoint is not limited to certain element type.  I
> think that we should include elements that we want to highlight to
> developers for specific consideration on a checkpoint and in this case 8.2,
> 8.3, 4.15 and 4.16. I think we could ask developers in last call if they
> think some should be removed or do they think they were helpful.

Again, can you show an example?

Thanks,

 - Ian
 
> Jon
> 
> At 08:10 PM 10/11/2000 -0400, Ian Jacobs wrote:
> >Jon Gunderson wrote:
> > >
> > > Ian,
> > > It seems to me they were included in your original proposal because they
> > > had minimal requirements for output for text.  Since these checkpoints had
> > > minimal requirements it seems that highlighting them in the labeled groups
> > > makes sense.  It seems that we are missing minimal requirements for speech
> > > rendering for 8.2, 8.3, 4.15 and 4.16.
> >
> >Here's my new reasoning: the selection (or focus) need not only be for
> >text. For instance, a selected image may have a border around it.
> >Similarly,
> >links may have text or non-text content. So for all four checkpoints,
> >the
> >content type doesn't matter.
> >
> >I agree that we don't have minimal speech requirements for the four
> >checkpoints in question. However, as we resolved in a previous
> >teleconference,
> >I think that we should not refine our speech requirements any further
> >for
> >this document since there are other W3C WGs working on voice/speech
> >issues.
> >
> >  _ Ian
> >
> > > Jon
> > >
> > > At 07:27 PM 10/11/2000 -0400, Ian Jacobs wrote:
> > > >jon gunderson wrote:
> > > > >
> > > > > Section 3.4 Content type labels
> > > > >
> > > > > 1. Audio label missing checkpoint 3.2, remove 4.15 and 4.16 (add to
> > speech
> > > > > label), and order checkpoints numerically.
> > > > >
> > > > > 2. Image label missing 3.4 (if label is to be consistent with including
> > > > > 3.3 in Text grouping for animations)
> > > > >
> > > > > 3. Speech label missing 4.15, 4.16, 8.2 and 8.3
> > > >
> > > >Jon,
> > > >
> > > >As I think about it, I think the following checkpoints apply
> > > >to all user agents (whatever the content type rendered): 4.16, 4.17,
> > > >8.2, and 8.3 (details below). Checkpoints 4.16 and 4.17 are about
> > > >selection and focus (which are independent of content type). Checkpoints
> > > >8.2 and 8.3 are about links (which are also independent of content
> > > >type). Therefore, I think these checkpoints should be removed from
> > > >all content type label sets since they apply to all UAs. I think
> > > >(but am not absolutely sure) that the way the checkpoints are
> > > >written, they already take into account applicability (e.g., they
> > > >say "for graphical user agents...").
> > > >
> > > >  _ Ian
> > > >
> > > >[1] http://www.w3.org/WAI/UA/WD-UAAG10-20000929/
> > > >
> > > >--
> > > >Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
> > > >Tel:                         +1 831 457-2842
> > > >Cell:                        +1 917 450-8783
> > > >
> > > >
> > > >Checkpoints 4.16, 4.17, 8.2, and 8.3:
> > > >
> > > >4.16 Allow the user to configure how the selection is highlighted
> > > >     (e.g., foreground and background color, voice pitch, etc.).
> > > >     For graphical viewports, offer at least three
> > > >     rendering options, including colors and fonts.
> > > >     Allow the user to select from among the range of system colors and
> > > >fonts.
> > > >
> > > >
> > > >4.17 Allow the user to configure how the content focus is highlighted
> > > >     (e.g., foreground and background color, voice pitch, etc.).
> > > >     For graphical viewports, offer at least three
> > > >     rendering options, including colors and fonts. For graphical
> > > >viewports,
> > > >     allow the user to select from among the range of system colors and
> > > >fonts.
> > > >     The default focus highlight mechanism must be different from the
> > > >default s
> > > >     election highlight mechanism.
> > > >
> > > >8.2 Render recently visited links in a distinct style and allow the user
> > > >to
> > > >     configure this style. For graphical viewports, offer at least three
> > > >     rendering options, including colors and
> > > >     fonts. Allow the user to select from among the range of system
> > > >colors and fonts.
> > > >
> > > >8.3 Render in a distinct style those links that have been marked up to
> > > >indicate that
> > > >     following them will involve a fee and allow the user to configure
> > > >this style.
> > > >     For graphical viewports, offer at least three rendering options,
> > > >including
> > > >    colors and fonts. Allow the user to select from among the range of
> > > >system colors
> > > >    and fonts.

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Thursday, 12 October 2000 09:43:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:22 GMT