Jump to: navigation, search

Difference between revisions of "Horizon/WebAccessibility"

Line 8: Line 8:
 
* Testing Techniques
 
* Testing Techniques
 
A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface.  You should be able to reach and activate all of Horizon's functions this way.  You should always be able to see the focus.  The tabbing should happen in a logical order.  I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.
 
A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface.  You should be able to reach and activate all of Horizon's functions this way.  You should always be able to see the focus.  The tabbing should happen in a logical order.  I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.
 +
 +
http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/ An informative article that helps understand guideline 1.4.3 (http://www.w3.org/TR/WCAG20/#visual-audio-contrast).  Includes links to tools to interactively view web pages with filters to help understand how the page might be perceived by various users.  Also includes a calculator to help determine if specific foreground/background combinations have sufficient contrast.
  
 
* Known Issues:
 
* Known Issues:

Revision as of 14:39, 5 May 2014

  • Testing Techniques

A simple way to start testing for accessibility problems is to set aside your mouse and use the keyboard to navigate the interface. You should be able to reach and activate all of Horizon's functions this way. You should always be able to see the focus. The tabbing should happen in a logical order. I expect that Horizon will generally be impacted by http://www.w3.org/TR/WCAG20/#keyboard-operation sections 2.1 and 2.4.

http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/ An informative article that helps understand guideline 1.4.3 (http://www.w3.org/TR/WCAG20/#visual-audio-contrast). Includes links to tools to interactively view web pages with filters to help understand how the page might be perceived by various users. Also includes a calculator to help determine if specific foreground/background combinations have sufficient contrast.

  • Known Issues:

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.3.1 Info and Relationships
    • There is no caption element, summary attribute in tables such as instances, volumes, images, so on.
    • There is no scope attribute in th elements.
  • 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.
Retrieved from "https://wiki.openstack.org/w/index.php?title=Horizon/WebAccessibility&oldid=51171"