Gap Analysis of Mobile Document and Low Vision Needs Document

From Low Vision Accessibility Task Force

On August 18, 2016, Jim Allan wrote:

In the early day of Mobile they had the following regarding low vision. They are no longer focusing on the low vision aspects. Can someone review these to ensure LVTF didn't miss anything from the mobile perspective.

This page documents gaps between Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile and Accessibility Requirements for People with Low Vision.

Gap Analysis

Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile

User Need From: Accessibility Requirements for People with Low Vision

Gap

2.1 Small Screen Size

  • Providing a reasonable default size for content
  • Adapting the length of link text to the viewport width.
  • Positioning form fields below, rather than beside, their labels (in portrait layout)
  • Text Size: Users can change the text size (font size) of all text, without zooming the entire interface.
  • Size: Users can change the size of all elements.
  • Line Length: Users can set the line length for blocks of text.
  • Reflow: Users can set blocks of text in one continuous block.
  1. Providing a reasonable default size for content
  2. Positioning form fields below, rather than beside, their labels (in portrait layout)

jim-seem more of a technique

2.2 Zoom/Magnification

  • allow the user to control content size on mobile devices
  • Ensure that the browser pinch zoom is not blocked by the page's viewport meta element so that it can be used to zoom the page to 200%.
  • Support for system fonts that follow platform level user preferences for text size.
  • Provide on-page controls to change the text size.
  • Text Size: Users can change the text size (font size) of all text, without zooming the entire interface.
  • Size: Users can change the size of all elements.
  1. Provide on-page controls to change the text size. jim-seems perscriptive

2.3 Contrast

  • Allowing different contrast ratios for larger text is useful because larger text with wider character strokes is easier to read at a lower contrast.
  • developers should strive to make sure to apply the lessened contrast ratio only when text is roughly equivalent to 1.2 times bold or 1.5 times (120% bold or 150%) that of the default platform size. Note, however, that the use of text that is 1.5 times the default on mobile platforms does not imply that the text will be readable by a person with low vision.
  • Contrast: Users can set the background color and the text color from the full color spectrum.
  1. developers should strive to make sure to apply the lessened contrast ratio only when text is roughly equivalent to 1.2 times bold or 1.5 times (120% bold or 150%) that of the default platform size. Note, however, that the use of text that is 1.5 times the default on mobile platforms does not imply that the text will be readable by a person with low vision. jim - this looks like a technique rather than an SC. ??what is the research base for this statement.

3.5 Placing buttons where they are easy to access

  • position interactive elements where they can be easily reached when the device is held in different positions.
  • Spacing Between Elements: Spacing groups related elements and separates less related elements.
  • Point of Regard: The point of regard remains visible within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed.

No Gap.

Should be covered by Spacing Between Elements and Point of Regard LVTF User Needs.

4.2 Consistent Layout

  • web pages within a particular view (set size and orientation) should be consistent in placement of repeated components and navigational components. Consistency between the different screen sizes and screen orientations is not a requirement under WCAG 2.0.
 Not Mentioned
  1. web pages within a particular view (set size and orientation) should be consistent in placement of repeated components and navigational components.

4.3 Positioning important page elements before the page scroll

  • Positioning important page information so it is visible without requiring scrolling can assist users with low vision and users with cognitive impairments. Placing important elements before the page scroll allows those who use screen magnifiers to locate important information without having to scroll the view to move the magnified area. This assists users that have cognitive impairments such as short-term memory disabilities. Placing important elements before the page scroll also helps ensure that elements are placed in a consistent location. Consistent and predictable location of elements assists people with cognitive impairments and low vision.
  • Rewrap: Blocks of text rewrap so that only one direction of scrolling is needed,
  1. Positioning important page information so it is visible without requiring scrolling can assist users with low vision...

4.4 Grouping operable elements that perform the same action

  • When multiple elements perform the same action or go to the same destination (e.g. link icon with link text), these should be contained within the same actionable element. This increases the touch target size for all users and benefits people with dexterity impairments. It also reduces the number of redundant focus targets, which benefits people using screen readers and keyboard/switch control.
 Not Mentioned

No Gap. Covered by:

  1. WCAG 2.4.4 Link Purpose (In Context) (Level A)
  2. WCAG 2.4.9 Link Purpose (Link Only) (Level AA)
  3. H2: Combining adjacent image and text links for the same resource

References

Email

Documents

Retrieved from "https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/index.php?title=Gap_Analysis_of_Mobile_Document_and_Low_Vision_Needs_Document&oldid=1258"