Thread Subject: Re: CombinedHardwareSubcommittee Proposal
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: Yamada@TOYO-UNIV
Date: Mon, Dec 18 2006 4:55 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: CombinedHardwareSubcommittee Proposal"
- Previous message in thread: Gregg Vanderheiden: "Re: CombinedHardwareSubcommittee Proposal"
- Messages sorted by: Author | Thread | Date
Gregg,
I completely agree your opinion.
> In the "general" group we have been looking at writing guidelines by
'characteristics" of product rather than product type for just this reason.
Still in analysis stage but with products morphing as they are. I think we
need to move in that direction.
What I wanted to say in the previous two messages are as follow:
It is recommended to include quantitative measures as far as possible in the
technical specifications so that we can check conformity objectively.
However, a single quantitative measure such as "font size must be larger
than xx inches" or "sound volume must be larger than xx dB" is meaningless
since as you repeatedly mentioned such quantitative measures depend on the
usage conditions/environments.
I have another example; i.e. flicker rate. Flicker is harmful. But no one
cares about a small light on USB memory flicking at the frequency between
2Hz and 55Hz. The reason is obvious: The light is too small to harm.
I think in the general section it is better not to include quantitative
measures. Quantitative measures are written in the detailed sections.
Hajime Yamada
- Next message in Thread: Gregg Vanderheiden: "Re: CombinedHardwareSubcommittee Proposal"
- Previous message in Thread: Gregg Vanderheiden: "Re: CombinedHardwareSubcommittee Proposal"