Supplemental Guidance List

This page is outdated. Current information is linked from the sections below.

Purpose, Audience, Scope, etc.

See Supplemental Guidance Requirements Analysis

Format/Template

Updated Template Sections comparison

Options:

1. WCAG Techniques / Understanding WCAG — draft content template (in wiki page for now) , Technique example (design is draft in progress) , Understanding example (design is draft in progress)
   • Pros:
     • ...
   • Cons:
     • ...
2. COGA Design Pattern — COGA example (design is draft in progress)
   • Pros:
     • ...
   • Cons:
     • ...

Other Potential Topics

The new list is in the Supplemental Guidance Table 

• Proximity of information (currently this is an advisory technique) to make sure fields and labels are in same magnified viewport and in predictable locations such as checkbox to left of label.
  • This may also include proximity of on-screen keyboard to input field - e.g. Desmose on iPad where these two things are not near each other.
• Providing icons for disabled UI interface elements (AG GitHub Issue 661 and suggested 2.2 SC.)
• sticky headers - % of viewport available for main content
• page refresh (suggested 2.2 SC)
• Affordance and contrast (e.g., on information separators)
• Feedback within viewport
• LV access to alt text (UAAG?)
• Printing customized text
• large headings and responsive design reducing amount of content on screen taking away context and surrounding context.
• Seas of white space - need for condensed spacing
• Text that aligns to left side of screen making it difficult to read first characters and thus first word.
• Situations where a passive cookie notice doesn't obstruct access to a site when not zoomed in but obstructs site when zoomed in - but the notice can be accepted. This isn't so much as fail under current requirements as it can be accepted and dismissed but requiring low vision users to accept something that a non-disabled user can choose not to seems un equal.
• Input fields and other content areas that when zoomed are very short - for example that only show less than 3 lines of content but when not zoomed show many lines.
• Chunky text that is too bold and affects reading/recognition of characters/words
• Use of thin stroke fonts
• Ability to change fonts without font icons disappearing (while we do have role img techniques that can be used this is not addressed adequately.
• Support for high contrast/dark mode and alternative themes
• Disambiguating icons
• Text that becomes smaller when you zoom in
• Panels that take up valuable real estate but can't be collapsed/closed.

old links

• Old Template: Supplemental Guidance Template
• Old Example: Supplemental Guidance: Text Justification can be used as an example of the type of information to include