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

2.1.1 Keyboard and ACCESS_KEY, TAB_ORDER in MWBP to WCAG 2.0

From: Alan Chuter <achuter@technosite.es>
Date: Fri, 11 Jan 2008 13:00:30 +0100
Message-ID: <79cab0900801110400j370f5e79vff44d40fc93beed6@mail.gmail.com>
To: EOWG <w3c-wai-eo@w3.org>
Cc: "Wayne Dick" <wed@csulb.edu>

On 10/01/2008, Wayne Dick <wed@csulb.edu> wrote:
> Wayne Dick wrote:
> > I was reading MWBP to WCAG 2.0 carefully, and noticed the following
> > issues.  Some appear to be serious
...
> > 2.1.1 Does ACCESS_KEY, TAB_ORDER  apply?
IMHO, providing access keys and a correct tab order doesn't help make
the content operable through a keyboard interface. It might make it
easier to use the keyboard, but they're not alternatives to a mouse.

What do other people think?

regards,

Alan




On 10/01/2008, Wayne Dick <wed@csulb.edu> wrote:
>
> Wayne Dick wrote:
> > Hi all,
> >
> > I was reading MWBP to WCAG 2.0 carefully, and noticed the following
> > issues.  Some appear to be serious
> >
> > Mobile Web Best Practice to WCAG 2.0
> >
> >
> >
> > This probably needs a careful overview:
> >
> >
> >
> > Question:
> >
> > Do we want to list all Level A success criteria in Level AA
> >
> > Do we want to list all Level A  and level AA success criteria in Level
> > AAA
> >
> >
> >
> >
> >
> > Sort the Noting, Something, Everything lists by WCAG 2.0 Success
> > Criteria number
> >
> >
> >
> > Level A...
> >
> > 1.3.1 is supported by
> >
> > STRUCTURE, STYLE SHEET SUPPORT, STYLE SHEET USE, TABLE LAYOUT -- as
> > well as FONT
> >
> > 2.1.1
> >
> > Does ACCESS_KEY, TAB_ORDER  apply?
> >
> >
> >
> > Level AA
> >
> > On the everything list for Level AA,
> >
> > the level A
> >
> > 1.1.1 appears: only something
> >
> > 1.1.2 , 1.2.5, 1.2.6, 1.2.7 is AAA
> >
> > 1.3.1 appears : it only requires something
> >
> > 1.3.2 is level A and TAB_ORDER applies
> >
> > 2.1.1 is listed as partial before  OBJECT_OR_SCRIPT is sited
> >
> >
> >
> > I think all keyboard success criteria need to be reviewed.  The MWBP
> > emphasizes the need for keyboard interface throughout.
> >
> >
> >
> > 2.2.1 requires only something --- AUTO_REFRESH
> >
> >
> >
> > 2.2.4 is level AAA
> >
> >
> >
> >
> >
> > I need to stop here.
> >
> >
> > I haven't covered Level AAA consideratins
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi all,
> >
> > I was reading MWBP to WCAG 2.0 carefully, and noticed the following
> > issues.  Some appear to be serious
> >
> > Mobile Web Best Practice to WCAG 2.0
> >
> >
> >
> > This probably needs a careful overview:
> >
> >
> >
> > Question:
> >
> > Do we want to list all Level A success criteria in Level AA
> >
> > Do we want to list all Level A  and level AA success criteria in Level
> > AAA
> >
> >
> >
> >
> >
> > Sort the Noting, Something, Everything lists by WCAG 2.0 Success
> > Criteria number
> >
> >
> >
> > Level A...
> >
> > 1.3.1 is supported by
> >
> > STRUCTURE, STYLE SHEET SUPPORT, STYLE SHEET USE, TABLE LAYOUT -- as
> > well as FONT
> >
> > 2.1.1
> >
> > Does ACCESS_KEY, TAB_ORDER  apply?
> >
> >
> >
> > Level AA
> >
> > On the everything list for Level AA,
> >
> > the level A
> >
> > 1.1.1 appears: only something
> >
> > 1.1.2 , 1.2.5, 1.2.6, 1.2.7 is AAA
> >
> > 1.3.1 appears : it only requires something
> >
> > 1.3.2 is level A and TAB_ORDER applies
> >
> > 2.1.1 is listed as partial before  OBJECT_OR_SCRIPT is sited
> >
> >
> >
> > I think all keyboard success criteria need to be reviewed.  The MWBP
> > emphasizes the need for keyboard interface throughout.
> >
> >
> >
> > 2.2.1 requires only something --- AUTO_REFRESH
> >
> >
> >
> > 2.2.4 is level AAA
> >
> >
> >
> >
> >
> > I need to stop here.
> >
> >
> > I haven't covered Level AAA consideratins
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>


-- 
Email: achuter@technosite.es
Alternative email: achuter.technosite@yahoo.com
Blogs: www.blogger.com/profile/09119760634682340619
Received on Friday, 11 January 2008 12:00:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:47 GMT