Low Vision User Needs Coverage

This page analyzes low vision user needs coverage:

Note: Do not change the wording in the first column, since it is taken directly from the User Needs/Requirements draft. If you suggest different wording, add it in [brackets] to the first column or in the last column "Thoughts".

User Needs - with links to relevant User Need document section

Author/Browser/OS
A, B, O
What can authors do to not interfere with these needs?

WCAG 2.1
Success Criteria		 WCAG 2.2 Silver References, Resources, Thoughts, etc.

Proximity of Related Information: Users know about and can find related information.

 A   x   Perhaps a joint COGA - LVTF SC. when page reflows related information is separated. Need to find examples in the wild. How to keep programatically associated information in close proximity when page is zoomed, or viewport changes size.

example: large input control (50 characters) label of 'Name' on left edge. 'Required' is aligned on the right. huge amount of white space between. if using screen magnifier info on right is lost. If attention not directed to the right... info is easy to miss. (was in the US gov style guide. it has since been corrected.)
also, Mobile overlap perhaps a use case. Non-responsive sites are an issue.

Justification: Users can change the justification / alignment (left, right, full/both, centered) of blocks of text.

 B - user CSS, possible UI setting   x - ??Authors don't use full justification. We have the research to back this up.   @@Laura I suspect that a justification / alignment SC would not be accepted in 2.2 and would be pushed to Silver.
JF thinks it would be easy to add "don't use full justification" as an SC for authors.
Visual affordance - focus and controls     x   perhaps split 1.4.11 into UI and graphics. Focus on requirements for accessible visual affordance of user interface User Interface Component Contrast (Minimum). States are critical. Detlev - functional state (visited/unvisitied) transitional/transactional (checked/unchecked). component should maintain contrast between states. adjacent color applies to current state at current moment (not across states). different states do not need to contrast with each other. visited and non-visited are not adjacent so not covered. So only the visited and non-visited states as they stand on their own are covered. check in the checkbox is a graphical object - you have to be able to see the check.
Page Refresh - an aspect of Point of Regard. When new information is added to a page [content update/injection or page refresh] maintain focus at current location (do not move focus to top page as it disorients user and workflow).     x   This seems more of a failure technique for 2.2.4 - interrupting workflow on a page
Brightness: Users can set the overall brightness of a display.

B - media players

O - brightness setting

     X  

Contrast: Users can set the background color and the text color from the full color spectrum.

B - override forground/background in browser settings. User CSS.

O - forground/background color of application

1.4.11 Non-Text Contrast

1.4.8 Visual Presentation

   X @@Jim - Exception for browser default.

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.

 B     X  

User Settings: Content picks up all relevant user settings, such as ... [Draft Note: The Task Force plans to add additional information here.]

 B - possible UI setting. Should inherit OS settings     X @@Laura I suspect that a user settings SC would not be accepted in 2.2 and would be pushed to Silver.
[RESOLUTION: add User Need: Users can see and operate all interface elements that are intended for users to see and operate. This includes when users have changed display settings such as text size, magnification, and cursor. (9 March 2016)]       X @@Laura LVTF pushed the title attribute/tooltip obscured under the screen magnifier's large cursor issue to Silver. Resources:
  • Use Case: TAGLINE: Difficulty reading tooltips for icons, which are obscured under the screen magnifier's large cursor
  • Wiki page with title attribute evidence (28 November 2016)
  • Email: Obscuring active elements and text email
  • User need 7.1 Seeing All Interface Elements (Draft Note: Possible figure to be added: hover hand obscures important tooltip text)
  • RESOLUTION: add User Need: Users can see and operate all interface elements that are intended for users to see and operate. This includes when users have changed display settings such as text size, magnification, and cursor. (9 March 2016)

Color: Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

   1.4.1 Use of Color      

Rewrap: Blocks of text rewrap so that only one direction of scrolling is needed, e.g., for left-right and right-left scripts (languages), usually vertical scrolling and not horizontal scrolling.

   1.4.10 Reflow      

Reflow: Users can set blocks of text in one continuous block, instead of in multiple columns.

   1.4.10 Reflow      

Line Length: Users can set the line length for blocks of text. Often the easiest way to do this (for developers, designers, and users) is for users to resize text areas and the text rewraps to change the line length.

   1.4.10 Reflow      

Hyphenation: Users can turn hyphenation on or off.

B - user CSS, possible UI setting

       @@Laura I suspect that a hyphenation SC would not be accepted in 2.2 and would be pushed to Silver.

Text Size: Users can change the text size (font size) of all text, without zooming the entire interface.

         @@Jim - zoom is adequate for text and text in vector images. There are issues with raster images. Also, Huge issues with Tooltips.

Font: Users can change the font face (also called font family or typeface) of all text, choosing from a wide range of fonts including sans serif and serif fonts.

 B - user CSS, possible UI setting       @@Laura I suspect that a font SC would not be accepted in 2.2 and would be pushed to Silver.
Style: Users can change the text style (underline, italic, bold) of blocks of text. B - user CSS, possible UI setting       @@Laura I suspect that a style SC would not be accepted in 2.2 and would be pushed to Silver.

Capitalization: Users can change the capitalization (all capital letters, small capital letters, sentence style) of blocks of text.

 B - user CSS, possible UI setting       @@Laura I suspect that a capitalization SC would not be accepted in 2.2 and would be pushed to Silver.

Size of All Elements: Users can change the size of all elements.

   1.4.4 Resize Text      

Line Spacing: Users can change the line spacing (leading) for blocks of text.

   1.4.12 Text Spacing      

Letter Spacing: Users can change the letter spacing (space between letters/characters) of blocks of text.

   1.4.12 Text Spacing      

Word Spacing: Users can change the word spacing (space between words) of blocks of text.

   1.4.12 Text Spacing      

Margins and Borders: Users can change the margins (blank space) and borders (including color, width, style) around blocks of text.

 B - user CSS, possible UI setting       @@Laura I suspect that a margins /borders SC would not be accepted in 2.2 and would be pushed to Silver.
Spacing Between Elements: Spacing groups related elements and separates less related elements.   1.4.12 Text Spacing      

Element-level Customization: Users can customize text differently for specific elements, such as headings, lists, paragraphs, links, <strong>, <em>, <cite>, etc.
 Users can set at least:

  • Text size
  • Text color and background color
  • Font
  • Text style (that is, turn on or off underline, italic, bold)
  • Line spacing
  • Margins
  • Borders — including border line color, width, style
 B - user CSS       @@Jim some covered in 1.4.12.

All Elements: Users can see all interface elements that are intended for users to see, including when users have changed display settings such as text size.

B

O

      @@Laura I suspect that an all interface elements SC would not be accepted in 2.2 and would be pushed to Silver.

Printing: Users can print content after customizing how the text is displayed.

 B - user CSS, possible UI setting       @@Laura I suspect that a printing SC would not be accepted in 2.2 and would be pushed to Silver.
[hover, focus...]   1.4.13 Content on Hover or Focus     @@Jim - browser exception for TOOLTIPS.