RE: Proposal to drop A.3.6.5 Assistance with Preferences from ATAG2

Oops..."assistance" is just in the handle text. 

What I meant is that the "...mechanism to help authors configure..." needs to be clarified.

Cheers,
Jan




> -----Original Message-----
> From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On Behalf
> Of Richards, Jan
> Sent: September 29, 2011 1:42 PM
> To: Jeanne Spellman
> Cc: w3c-wai-au@w3.org
> Subject: RE: Proposal to drop A.3.6.5 Assistance with Preferences from ATAG2
> 
> Hi Jeanne,
> 
> I think the SC will also need to be edited to clarify what we mean by
> "assistance". Is it enough to provide help documentation on each setting
> field? Or are we thinking specifically of providing display previews within
> the settings area? In which case, be more specific and drop the "and/or
> control settings" part.
> 
> Cheers,
> Jan
> 
> 
> > -----Original Message-----
> > From: Jeanne Spellman [mailto:jeanne@w3.org]
> > Sent: September 29, 2011 11:26 AM
> > To: Richards, Jan
> > Cc: w3c-wai-au@w3.org
> > Subject: Re: Proposal to drop A.3.6.5 Assistance with Preferences from ATAG2
> >
> > I would rather see us add an additional example of a settings page with
> > preview screen as Jan suggested. Perhaps an additional example of a
> > settings page with links to the documentation would also be appropriate
> > to show the full range of examples that meet it.
> >
> > I don't think we should drop it. Although it does apply to all software,
> > it is particularly necessary to help authors with the complexity of
> > setting an accessible editing view. Without it, authors may not be able
> > to figure out how to set the editing view independently of the content.
> >
> > jeanne
> >
> > On 9/29/2011 11:08 AM, Richards, Jan wrote:
> > > On the call I took an action to better explain why I think we should drop
> SC
> > "A.3.6.5 Assistance with Preferences: If the authoring tool includes display
> > and/or control settings, then the authoring tool includes a mechanism to
> help
> > authors configure these settings." (Level AAA)
> > >
> > > My primary reason is that it is unclear what is required, so it is hard to
> > test. Our only example is a wizard, prompting one commenter to ask if that's
> > what we are requiring (http://lists.w3.org/Archives/Public/public-atag2-
> > comments/2011Aug/0000.html). But in my opinion a wizard isn't necessary. For
> > instance, a single page of settings with a preview panel would be fine for
> > setting display settings.
> > >
> > > I suppose we could work to refine it, but in my opinion it's not
> > sufficiently related to authoring interfaces (i.e. it's a general software
> > accessibility issue) to warrant the effort.
> > >
> > > Cheers,
> > > Jan
> > >
> > >
> > > (MR) JAN RICHARDS
> > > PROJECT MANAGER
> > > INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
> > >
> > > T 416 977 6000 x3957
> > > F 416 977 9844
> > > E jrichards@ocad.ca<mailto:jrichards@ocad.ca>
> > >
> > > Twitter @OCAD<http://twitter.com/ocad>
> > > Facebook
> > www.facebook.com/OCADUniversity<http://www.facebook.com/ocaduniversity>
> > >
> > > OCAD UNIVERSITY
> > > 100 McCaul Street, Toronto, Canada  M5T 1W1
> > > www.ocadu.ca<http://www.ocad.ca>
> > >
> > >
> >
> > --
> > _______________________________
> > Jeanne Spellman
> > W3C Web Accessibility Initiative
> > jeanne@w3.org

Received on Thursday, 29 September 2011 17:50:37 UTC