Robust Techniques

Robust Techniques

• Set the virtual keyboard to the type of data entry required
  • should be moved to 3.3, Input Assistance
  • while it is an improvement for people with mobility issues, it can add to barriers for blind users using older smartphone with rubber overlays marking the keyboard.
  • sometimes the developer narrows the input, without being aware of all the possibilities of the variety of input being used.
  • [Technique] Authors should be aware of the variety of information types that can be entered in a text field, and not restrict the type of data with an HTML5 input attribute.

• Provide easy methods for data entry
  • [Technique] When possible, users should be able to chose their data from a picker rather than from data entry. Note: Keep in mind the variety of input methods, because speech users can not use a picker in iOS, but that should not keep authors from using pickers, as the lack of a picker is a bug in the platform or browser, and not an author problem. .

• Support the characteristic properties of the platform
  • Important for mobile app - support the settings but may not be practical in all scenarios
    • Text size - think about the text size that makes sense to enlarge other areas. Text resize reflows. Some items may not look right such as tabs.
  • Mobile web should not suppress settings
  • There are techniques that we could add but don't fully meet (used in conjunction with another technique)
  • More native app techniques that could be listed here

• • ARIA does not work well with certain controls on mobile. For example items that require arrow keys. A slider control is an issue both on Android and iOS.
    • may work for a keyboard but users should not be required to use it
    • keyboard commands need to be swipe accessible