EWG:Draft Oct 26 Size shape location

3-C - Size, shape, location

This page is the text proposed in the Nov Plenary Meeting.

Go to the Oct 26 Draft of this Provision

Go to the Sandbox of this Provision

Proposed text in Oct 26 draft:
Instructions provided for understanding information and operating user interfaces must not rely on shape, size, visual location, or orientation of components.

• Note: Object information provided per the "Information and Relationships", "User Interface Components", or "AT interoperability" provision that describes the necessary visual cues or relationships can be used to meet this provision.
• Note: This applies to onscreen information only.

Rationale: This applies to instructional text in the interface or other onscreen information. Harmonization with WCAG 2.0.

Discussion of Work in Progress: 
* (Allen H) Shouldn't this include the phrase "as the only means of conveying information"?

Comments from ITAA
a. Precede with "Onscreen".
b. Delete 2nd note
c. Need an example of "orientation of components"
d. Many vendors don't have an appreciation for what this is all about. Provision must make this clear.

Comments from (Japan/Haijime Yamada)
Suggest replacing "Instructions" with "Onscreen information", so the provision would read:

"Onscreen information provided for understanding components and operating user interfaces must not rely on size, shape, visual location, or orientation of components."

Comments from CSD/Trace Center

1. Agree with ITAA (and Japan) to remove 2nd note and add "on-screen" to provision. BUT "on-screen" should relate to the buttons and controls not the location of the instructions. (Referring to the shape of a physical button works well – no matter where the instructions are – but the shape of the onscreen button is lost on screen reader users). It would then read: "Instructions provided for understanding information and operating on-screen user interfaces must not rely on shape, size, visual location, or orientation of components."
2. Agree with ITAA that example is needed. Suggest: Example: A user of a screen reader cannot discern which on-screen button he or she needs to trigger if the desired button is only identified by a visual characteristic such as shape, size or location such as "When done press the button on the right" or "round button" or "large button" or "arrow pointing to the right".