RECOMMENDED EDITS TO FORMAL DRAFT

RECOMMENDED EDITS TO FORMAL DRAFT

EDITS THAT NEED TO BE MADE TO 1.2-F and 1.2-G

 The following notes need to be added to 1.2-F and 1.2-G

1.2-F - Audio information

All information that is needed for operation and use that is provided in audio form must also be available in visual form, either directly or via assistive technology.

• 1.2-F Note: Audio content that includes spoken content and that is closed due to DRM such that it cannot be rendered in visual form by AT and other players must include an visual form that can be.

1.2-G - Visual Information

All information that is needed for operation and use that is provided in visual form must also be available in audio form and, where appropriate, in tactile form, either directly or via assistive technology.

• 1.2-G Note: Visual Content that includes text and that is closed due to DRM such that it cannot be rendered in audio form by AT and other players must include an audio form that can be.

.

EDITS TO 1.2 B (Closed Functionality) and the Definition (Closed Functionality)

    Suggest that 1.2-B (Closed Functionality) be revised as follows    

Summary of changes

1. new short name (Closed Functionality)
2. New term for DEFINITIONS ( Change to "Closed Functionality" )
3. add listing of provisions that do not apply

Final Wording

1.2-B - Closed Functionality

If any functionality of a product is closed for any reason including policy constraints or technical limitations then that closed functionality must be made available to and operable by people with disabilities within the product itself and the following provisions would not apply to that functionality.

2.1-E - Connector or Connection Language

3-F - All Non-Text Objects

3-G - Human Language

3-H - Language of Parts

3-N - Link Purpose

3-O - Information and Relationships

3-P - User Interface Components

3-U - AT Interoperability

3-W - Accessibility Services

 RENAME THE DEFINITION FROM  "Closed Product Functionality"  TO  "Closed Functionality" 

Closed Functionality

Functionality of a product where assistive technology can not be used to achieve some or all of the functionality of the electronic user interface components for any reason including hardware, software, platform, license, or policy limitation.

• Products can be closed for one type of disability but not closed for another.
• Functionality is limited to "electronic UI components" because products are not considered ‘closed’ if mechanical devices like latches or lids cannot be operated by assistive technologies like screen readers. Mechanical devices such as keys that cause electronic input would however trigger “closed” designation if assistive technologies could not achieve the same functionality.
• A ‘product’ can consist of multiple devices some of which may be AT if the devices are all sold and kept together as a unit.
• Policy includes manufacturer, or vendor policies,etc. Agencies are responsibility for agency policies. If important to procurement agencies should reflect requirement as specifications in the RFP. (e.g. "Connection of user devices will not be allowed." or "All peripheral ports must be sealable.")

.

THE FOLLOWING THREE PROVISIONS NEED TO BE FIXED

3-M - Reading Sequence

When the sequence in which information is presented affects its meaning, a correct reading sequence can be programmatically determined and sequential navigation of interactive components is consistent with that sequence.

editorial suggestion: When the sequence in which information is presented affects its meaning, a correct reading sequence must be programmatically determinable. The sequential navigation of interactive components must be consistent with that reading sequence.

RESOLUTION

• add the following note to 3-M to clarify how this would apply to closed functionality.
  • For products with closed functionality the visual and (linear) audible presentation should match navigation

3-S Keyboard Operation

Version 1: All functionality of the product operable through the user interface must be operable through a keyboard interface without requiring specific timings for individual keystrokes. The only exception is where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

• Note: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path dependent input but the underlying function (text input) does not.
• Note: This does not forbid and should not discourage providing mouse input or other input methods, such as gestures, in addition to keyboard operation.

editorial suggestion for first paragraph in version 1: All functionality operable through the user interface must be operable through a keyboard interface without requiring specific timings for individual keystrokes. The only exception is where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

• Some portable handheld products should not be required to be operated with a keyboard. Digital cameras and camcorders are examples.

RESOLUTION

• NEEDS TO HAVE PHRASE ADDED TO FRONT: For products that have a keyboard or keyboard interface, or content that can be viewed on devices that have a keyboard,...

. RESOLUTION

 2.1-E RENAME  "User Interface Connector or Connection" 

2.1-E should be renamed "User Interface Connector or Connection" or "User Interface Connection"

.