Thread Subject: Re: Gaps inWeb Requirements- keyboard operation
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: Gregg Vanderheiden
Date: Wed, Jan 10 2007 11:40 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: David Poehlman: "Re: Gaps inWeb Requirements- keyboard operation"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
I think that software written to work on a laptop is software that is
designed for a system that has a keyboard. The software itself may not use
the keyboard for all functions but the keyboard is part of the system. In
fact the keyboard is probably used to name the file when it is saved.
We don't want to say that things need to be accessible from the keyboard
only if they are designed to be accessible from the keyboard. It should be
as was suggested - that it is always except when it can't be done for
technical reasons.
No?
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Hoffman, Allen
> Sent: Wednesday, January 10, 2007 4:10 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Gaps in Web Requirements-
> keyboard operation
>
> I think that would be an excellent "clarification"/refinement
> of current standard.
>
>
>
> Allen hoffman -- 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Sean Hayes
> Sent: Wednesday, January 10, 2007 6:03 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Gaps in Web Requirements-
> keyboard operation
>
> Peter made a good point on the call today about pen input.
>
> I would argue that freehand drawing is not "software designed
> to run on a system that has a keyboard", whereas clearly the
> rest of Photoshop is designed to run on a system with a
> keyboard; so maybe the final wording should be fine grained
> enough to apply/not apply to software subsytems as opposed to
> a binary yes/no for the entire application.
>
> Sean Hayes
> Standards and Policy Team
> Accessible Technology Group
> Microsoft
> Phone:
> mob +44 7977 455002
> office +44 117 9719730
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Gregg Vanderheiden
> Sent: 10 January 2007 21:23
> To: 'TEITAC Web/Software Subcommittee'
> Subject: Re: [teitac-websoftware] Gaps in Web Requirements -
> keyboard operation
>
> Many devices that dont have keyboards have keyboard
> interfaces. And would accept 'keyboard control' from
> virtual keyboards or AT.
>
> This should apply to things that have keyboards or keyboard
> interfaces (real or virtual).
>
>
> Gregg
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
>
>
>
> > -----Original Message-----
> > From: = EMAIL ADDRESS REMOVED =
> > [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf Of Andi
> > Snow-Weaver
> > Sent: Tuesday, January 09, 2007 12:37 PM
> > To: = EMAIL ADDRESS REMOVED =
> > Subject: Re: [teitac-websoftware] Gaps in Web Requirements
> - keyboard
> > operation
> >
> >
> > At last week's meeting, we discussed the idea of having a keyboard
> > requirement for Web in 508 as WCAG 2.0 has. There was general
> > consensus for the idea but concern that it should not be applied in
> > cases where the content is known to be rendered on a device that
> > doesn't have a keyboard. I took an action item to propose something
> > that includes some kind of qualifier phrase like "when software is
> > designed to run on a system that has a keyboard" (from 21(a)).
> >
> > So, here is a proposal for discussion on the list and we
> will discuss
> > at tomorrow's call:
> >
> > For Web content or applications that are designed to run on
> a system
> > that has a keyboard, product functions shall be executable from a
> > keyboard where the function itself or the result of performing a
> > function can be discerned textually.
> >
> > When we discussed the existing 508 software requirement (21(a)),
> > concern was raised that the phrase "discerned textually" is unclear.
> > But no one had a better proposal.
> >
> > Andi
> >
> >
- Next message in Thread: David Poehlman: "Re: Gaps inWeb Requirements- keyboard operation"
- Previous message in Thread: None
WebAIM is an initiative of:
