Hardware Subcommittee - March 12 Survey Report
From TEITAC
I. Material which can be described as “Changes to Existing Provisions”
- Modification – Material which modifies existing provisions.
- Rationale – Why is this change suggested?
| Current provision | Keep current language | Current language | Change in Jurisdiction? | Modification | Rationale: Why is this change suggested? |
|---|---|---|---|---|---|
| 1194.26 (a) | Yes | All mechanically operated controls and keys shall comply with § 1194.23 (k) (1) through (4). | No | A reminder that this provision deals only with mechanical controls & keys. Touch-sensitive is in the next section. | |
| 1194.26 (b) | Yes | If a product utilizes touch screens or touch-operated controls, an input method shall be provided that complies with § 1194.23 (k) (1) through (4). | No | There are conflicting benefits related to touch controls between different types of disabilities. For people with severe motor impairments (ie. people who can't use their hands), a 100% touch interface is a good thing because it means all controls are software-based and they can therefore actuate them. {?? Controls can be software based without being touch sensitive} Perhaps a new provision could be added which states something like "Functions that are performed by mechanical controls and keys shall also be performable via alternative interfaces". {This would go in AT compatibility.} Also, discussion here around the issue of being able to turn on a device from a cold shut-down via the USB port. Is it possible? It used to be on the old Apple Desktop Bus (ADB) that had the same pin functionality as USB (Power, Ground, Data+, Data-). | |
| 1194.26 (d) | Yes | Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards. | No | Yes - add language including wireless (IR, Bluetooth, etc.) as a port. | It offers other avenues for AT/IT interaction especially in small form factors. |
| 1194.23 (k) (1) | Yes | Controls and keys shall be tactilely discernible without activating the controls or keys. | We have identified at least 4 levels of information to be perceived about a control or key: 1)That is exists, 2) What its function is, 3) Feedback when the function is performed, and 4) What its status is (only for toggle controls). | ||
| 1194.23 (k) (2) | Yes | Controls and keys shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate controls and keys shall be 5 lbs. (22.2 N) maximum. | Yes | change the order of items listed to: "... with one hand and shall not require pinching, twisting of the wrist, or tight grasping". | There has been confusion over whether the adverb "tight" applied to grasping only, or also to pinching and twisting, with the current wording. Also note that most knob-type controls can still be actuated without pinching or twisting, using edge control (eg. push up on the left side of the knob with the outside of your hand to turn up the volume).
Sent: Tuesday, March 13, 2007 4:58 PM David Baquis |
| 1194.23 (k) (3) | Yes | If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character. | |||
| 1194.23 (k) (4) | Yes | The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound. | |||
| 1194.21(i) | Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Pulled this one as an example of potential language around color coding (impact to blind & color blind users). This may be a start with some work. | |||
| 1194.21 (k) | Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. | YES - to General. Applies to software and hardware and content and .... | Does this apply to LEDs or other light based messaging on in the “corporeal” interaction world? | ||
| 1194.25 (e) | When products provide auditory output, the audio signal shall be provided at a standard signal level through an industry standard connector that will allow for private listening. The product must provide the ability to interrupt, pause, and restart the audio at anytime. | From self-contained, will we just state that an auditory element is needed or do we define?? | |||
| 1194.25 (j) (1) | Yes | Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following. The position of any operable control shall be determined with respect to a vertical plane, which is 48 inches in length, centered on the operable control, and at the maximum protrusion of the product within the 48 inch length on products which are freestanding, non-portable, and intended to be used in one location and which have operable controls. | |||
| 1194.25 (j)(2) | Yes | Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following. Where any operable control is 10 inches or less behind the reference plane, the height shall be 54 inches maximum and 15 inches minimum above the floor. | |||
| 1194.25 (j)(3) | Yes | Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following, Where any operable control is more than 10 inches and not more than 24 inches behind the reference plane, the height shall be 46 inches maximum and 15 inches minimum above the floor. | |||
| 1194.25 (j)(4) | Yes | Products which are freestanding, non-portable, and intended to be used in one location and which have operable controls shall comply with the following. Operable controls shall not be more than 24 inches behind the reference plane. |
II. Entirely New Provisions
| New provision | Rationale: What issue does this provision address? |
|---|---|
| Something dealing with mixed mechanical and touch sensitive controls. | So that mechanical can be found without activating the touch |
II+ . Issues Not addressed
- Need visual and audio identification of keys (Tactile-Braille also good but not sufficient since most people who are blind cannot use braille to ID keys)
- Need visual and either tactile or sound feeedback of operation
- Is IPOD interface accessible? if not, do we need to add something to identify that type as not, or are we covered already?
III. Other Material
A. Recommendations on organization of the provisions
B. Issues this subcommittee is not addressing, but which should be addressed.
- Firmware and BIOS access were commonly brought up. There may be the need to form a team to address these specifically.
- Full operation from software (no functions that can only be done from one input device. EG only from the built in keyboard)
C. Recommendations relating to Themes or other content.
Shigetoyo Nomura submitted, via the listserv, several requirements that are currently set in JIS 8341-2 for consideration. We have not had time to discuss in detail amongst the SC but will put it as an action item for the next report.
