Tracking Implementation Issues (Understanding Docs updates)

From Low Vision Accessibility Task Force

This page is used to track the completion of updating Understanding Documents per issue comments and teleconference minutes.

In general, the Understanding Documents need the following:

  • Non-Text - call out infographics, photographs (essential), text cursor as indicator of focus, 3:1 form controls (border contrast) more visible, if graphic is explained in text - no longer essential,
  • Reflow - explain non-reflowable content, css pixels, go to moble view from anywhere, vertical text example, complex apps,
  • Text Spacing - how to test, resources/tools, Stylish, call out captions & images of text, internationalization, explain font size,
  • Hover - avoid popup content on hover/focus, address persistance,

NOTE: For Implementations please add the URL of the site/page that works. Include any notes as appropriate immediately following the URL in the Implementation cell.

Non-Text Contrast

Comment or Minutes with relevant links Understanding Completed Implementation Notes
721 Non-text - SC title change YES    
709 Non-text - call out infographics in Understanding. YES   proposal done, waiting on feedback from A. Arch
628 Non-text - more examples      
549 Non-text - photographs as part of the "essential" exception, and will clarify this in understanding YES    
522 Non-Text - more "essential" exception examples (screen shots, photos, paintings, etc) no    
437 Non-Text - text cursor (uaag def) as aspect of focus indication no   Caret colour can be changed: https://developer.mozilla.org/en-US/docs/Web/CSS/caret-color
436 Non-text - more specifics (examples) making controls and focus visible to 3:1 YES    
181 Non-Text - add - 'flags' as excepted by both 'logotypes' and 'essential', add - graphic is no longer essential for understanding if the content is explained textually elsewhere YES
minute 2 Non-text - border contrast (form controls) YES

Reflow

Comment or Minutes with relevant links Understanding Completed Implementation Notes
721 Reflow - more examples for responsive design. explain more about non-reflowable content (e.g. videos) YES    
708 Reflow - call out CSS pixel with examples in Understanding need def and picture    
694 Reflow - clarify that a mechanism needs to be available for a user to go to mobile view from desktop no - should be a technique    
674 Reflow - add examples of vertical text (perhaps a video) no    
467 Reflow - Perhaps -explain in Understanding how complex apps could meet this(?) no note any failure of complex applications.  
415 Reflow, 414 Reflow, - PDF. Perhaps - add statement about making "pdf-ua compliant" PDFs(?) no - technique? need PDF failure examples  

Text Spacing

Comment or Minutes with relevant links Understanding Completed Implementation Notes
721 Text spacing - testing, resources. bookmarklet not working. add Stylish to resources in Understanding. YES Added Stylish and Alastair's Bookmarklet to Resources Section. Testing via Bookmarklet and Stylish procedures are in Allowing for Spacing Override Technique as the Understanding Doc template states "examples should stay high-level and not get into code specifics, which is for techniques." Technique is linked from the Understanding Doc.  
710 Text Spacing - testing tools. Add tool/procedures Understanding. YES Added Stylish and Alastair's Bookmarklet to Resources Section. Testing via Bookmarklet and Stylish procedures are in Allowing for Spacing Override Technique as the Understanding Doc template states "examples should stay high-level and not get into code specifics, which is for techniques." Technique is linked from the Understanding Doc.  
576 Text spacing, 551 Text Spacing, 469 Text Spacing - N/A Note any failures of sidebar, side nav, etc blocks of text was tabled pending further testing.
438 Text spacing, Minute 3 Text spacing - address captions and images of text YES Added captioning info per John Foliot. Linked to "Images of Text" definition.

"Examples of text that are typically not affected by style properties and not expected to adapt are:

  • Video captions embedded directly into the video frames and not provided as an associated caption file Images of text"
  • Images of Text"
  
Minute 3 Text spacing - internationalization (scripts) YES Added Jim's Internationalization content from Issue 677 comments 358383565 and 358393936 It reads:

"Roughly 480 different languages and scripts have been tested. Maximum spacing adjustments allowed by the SC were set on the following 3 pages:

  1. Languages in their own writing systems
  2. Online Encyclopedia of writing systems and languages – language names
  3. Universal Declaration of Human Rights (Article 1)

Results

No adverse effects occurred. The following are the specific findings:

  • Character Spacing - Individual characters in words remained in tact though they were spaced a bit further apart.
  • Word Spacing - Words were spaced farther apart. In languages that do not have words (e.g. Japanese) applying work spacing had no effect. This is expected.
  • Line Height - Changing line height did not separate diacritics from characters, nor did it adversely impact ascenders or descenders.

As previously discussed, the ability to read text with adjusted spacing is a user responsibility. This is true no matter the language.

The SC's exception addresses cases where a text style property is not used in a language or script. In such cases, authors are only required to ensure relevant properties do not break the layout."

Minute 4 Text Spacing - explain more font size YES Added that PWD "may need to change font family (e.g. to a wider one) than the author has set to effectively read text."

Hover

Comment or Minutes with relevant links Understanding Completed Implementation Notes
439 Hover - clarify author not encourage to create pop content. no    
minute 1Hover - persistance in Understanding? no
Retrieved from "https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/index.php?title=Tracking_Implementation_Issues_(Understanding_Docs_updates)&oldid=3472"