Understandable Techniques

• Consistent layout and navigation
  • Update understanding document - consistent layout in the understanding document for the breakpoints, orientation changes etc. - these are initiated by the user
  • G61 - update this technique
  • No new techniques
• Positioning important page elements before the page scroll
  • Best practice but scrolling is not as much of an issue anymore
  • Maybe fits better under navigation
  • No new techniques, add sentence to the note about too much content is hard for all users - hard to pick out consistent elements on the screen
  • Falls under predictability - talk to cognitive task force
• Grouping operable elements that perform the same action
  • H2 - add mobile specific language
  • Follow the standard keyboard shortcuts
• Provide clear indication that elements are actionable
  • Focus indicators don't break it - often provided by browser
  • G165, G195, G149, C15 - techniques for focus indicators
  • Touch screen you don't know that things are actionable - need a clear indication that things are actionable
  • UAAG has information for this
  • Custom controls may not have affordances - we may need a technique for this
• M5: Providing instructions for custom functions and gestures
  • Technique for adding hints for iOS applications
  • Technique for turning hints on and off
    • should also have a optional visual layer as well, as they are not only for audio
  • Technique on having a visual indicator that there is more information off screen
    • Best practice: Some designers will reveal a corner or sliver of something off screen to give people an idea there is more material available to swipe. An animation affordance hint that indicates there is more material.
    • Another example is the labels that shake when an error is made -- the shake doesn't give you any information about the error.
    • 3.3.1 Error ID
    • 1.3.3 Sensory characteristics
    • 2.1.1 keyboard -- if there is a visual indicator, then it has to be focusable
• M20: Providing instructions for form data types
  • Do not use placeholder text alone, with no label
  • Contrast minimum requirements for placeholder text
  • Ensure elements are still given an accessible name even after users start typing something into the field
    • labelFor (Jon)
  • Technique for ways of marking up groups of labels that works on mobile because that standard use of fieldset does not work in all mobile environments
    • Bug that should be filed against iOS
    • ARIA technique - rolegroup that could handle this (Jon)