Thread Subject: Re: Gaps in Web Requirements -keyboardoperation
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: Robinson, Norman B - Washington, DC
Date: Mon, Feb 05 2007 7:03 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Gaps in Web Requirements -keyboardoperation"
- Previous message in thread: Travis Roth: "Re: Gaps in Web Requirements -keyboardoperation"
- Messages sorted by: Author | Thread | Date
I'd say the definition of keyboard needs elaboration. For me any
key - only one for instance - is a keyboard. With that in mind, things
such as the ezaccess keys on kiosks, buttons on PDAs, etc. seem to be
covered. The only issue I see as problematic is software keyboards, when
used as a replacement for designing accessible keys (physical keys that
The key phrase is "WHERE THE FUNCTION CAN BE DISCERNED..." not
"we didn't design it to be used..." So if the developer continued to
insist they didn't design it that way, I'd say they weren't Section 508
Norman B. Robinson
Section 508 Coordinator
IT Governance, US Postal Service
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Travis
Sent: Friday, February 02, 2007 12:40 PM
To: 'TEITAC Web/Software Subcommittee'
Subject: Re: [teitac-websoftware] Gaps in Web Requirements
Andi Snow-Weaver wrote:
"For Web content or applications that are designed to run on a system
has a keyboard, product functions shall be executable from a keyboard
the function itself or the result of performing a function can be
I understand the intent of this is to get keyboard access to work when
hardware system has a keyboard.
The phrase "designed to run on a system that has a keyboard" concerns me
though in that what happens if an aplication is designed that may
on a system that may or may not have a keyboard, e.g., a PDA?
Another example. If a website is designed to be displayed and used on a
mobile device and the interface is not operable via keyboard. Can the
developer come back and say "We did not design this to work on a mobile
device with a keyboard, only those without keyboards." Even though both
types are able to access the application? Would there be a way to handle
Or are these concerns not valid?
(804) 749-8646 (office)
(402) 466-0907 (direct)
= EMAIL ADDRESS REMOVED =
Experts in Section 508 Compliance & Accessibility
NOTICE: This communication may contain privileged or other confidential
information. If you are not the intended recipient or believe that you
received this communication in error, please reply to the sender
that fact and delete the copy you received. Thank you.
- Next message in Thread: Gregg Vanderheiden: "Re: Gaps in Web Requirements -keyboardoperation"
- Previous message in Thread: Travis Roth: "Re: Gaps in Web Requirements -keyboardoperation"