Difference between revisions of "Horizon/WebAccessibility"
< Horizon
m |
m (add links to w3c spec) |
||
| Line 1: | Line 1: | ||
We inspected the Horizon (Havana release) for web accessibility and found the following problems. | We inspected the Horizon (Havana release) for web accessibility and found the following problems. | ||
| − | * 1.1.1 Non-text Contents | + | * [http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html 1.1.1 Non-text Contents] |
** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives. | ** A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives. | ||
| − | * 1.4.3 Contrast (Minimum) | + | * [http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html 1.4.3 Contrast (Minimum)] |
** text color and background color in the left menu | ** text color and background color in the left menu | ||
** text color and background color in the top menu | ** text color and background color in the top menu | ||
| Line 10: | Line 10: | ||
** text color and background color of the some buttons | ** text color and background color of the some buttons | ||
| − | * 2.1.1 Keyboard | + | * [http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html 2.1.1 Keyboard] |
** It's not easy to handle the layered message window by keyboard only. | ** It's not easy to handle the layered message window by keyboard only. | ||
** It may be difficult for a blind person to notice this layered error message. | ** It may be difficult for a blind person to notice this layered error message. | ||
| − | * 2.4.1 Bypass Blocks | + | * [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html 2.4.1 Bypass Blocks] |
** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area. | ** There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area. | ||
| − | * 2.4. | + | * [http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html 2.4.3 Focus Order] |
** The order of navigation doesn't match the visual order in some cases. | ** The order of navigation doesn't match the visual order in some cases. | ||
** The focus movement is not restricted to the layered pop-up window. | ** The focus movement is not restricted to the layered pop-up window. | ||
| − | * 3.1.1 Language of Page | + | * [http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html 3.1.1 Language of Page] |
** There is no lang attribute on the html element. | ** There is no lang attribute on the html element. | ||
Revision as of 05:46, 23 January 2014
We inspected the Horizon (Havana release) for web accessibility and found the following problems.
- 1.1.1 Non-text Contents
- A few non-text contents such as Network Topology (for Neutron) and Resource Usage (for Ceilometer) have no text alternatives.
- 1.4.3 Contrast (Minimum)
- text color and background color in the left menu
- text color and background color in the top menu
- link color and background color in the main content area
- text color and background color of the some buttons
- 2.1.1 Keyboard
- It's not easy to handle the layered message window by keyboard only.
- It may be difficult for a blind person to notice this layered error message.
- 2.4.1 Bypass Blocks
- There is no mechanism to skip repeated contents such as menu. For example, we can add a link at the top of each page that goes directly to the main content area.
- 2.4.3 Focus Order
- The order of navigation doesn't match the visual order in some cases.
- The focus movement is not restricted to the layered pop-up window.
- 3.1.1 Language of Page
- There is no lang attribute on the html element.
