Thread Subject: Re: Group A: 21(a) keyboard operation OnBehalf of Dewi Gani
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Gani, Dewi
Date: Fri, Oct 20 2006 5:20 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Group A: 21(a) keyboard operation"
- Previous message in thread: Barrett, Don: "Re: Group A: 21(a) keyboard operation"
- Messages sorted by: Author | Thread | Date
Jonathan's comment:
"Others have agreed that having MouseKeys in the OS shouldn't be an OS
requirement."
I think this statement is overgeneralized. According to ISO 9241-171
9.1.2: Platform software shall provide a keyboard alternative to
standard pointing devices that enables keyboard (or keyboard equivalent)
control of pointer movement and pointer button functions in parallel
with the standard pointing devices.
I agree with ISO 9241-171 9.1.2 that Platform software shall provide
this alternative. Thus, it is the requirement of the OS to provide such
a feature.
Best Regards,
Dewi Gani
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Jonathan Avila
Sent: Donnerstag, 19. Oktober 2006 20:31
To: 'TEITAC Web/Software Subcommittee'
Subject: Re: [teitac-websoftware] Group A: 21(a) keyboard operation
Luke,
//I would like to second Peter's comment about deferring this to the OS
layer. Overriding standard mouse control at the OS level with
different/local app settings would prob be in conflict with ISO and WCAG
points about not breaking interop. Besides...Consistency issues would
surface shortly if this were up to each individual authoring app. If
there
are issues with mousekyes not working in a particular Linux, Windows, or
Mac
OS, it is probably a separate thing to consider.
The point made earlier about the shapes drawn not being discernible by
the
reader is also something to mull over as a factor. //
----
I wasn't in any way suggesting that software move the mouse pointer or
provide keys to move the mouse pointer. I was instead suggesting that
all
mouse operations be supplemented by keyboard actions. Others have
agreed
that having MouseKeys in the OS shouldn't be an OS requirement. If it
is
not an OS requirement and not a software requirement then a user will
then
need to bring an AT into the mix.
Jonathan
- Next message in Thread: Gregg Vanderheiden: "Re: Group A: 21(a) keyboard operation"
- Previous message in Thread: Barrett, Don: "Re: Group A: 21(a) keyboard operation"
WebAIM is an initiative of:
