M007 - Supporting the characteristic properties of the platform (e.g. zoom, larger font, captions)
Technique Status Category
NEW TECHNIQUE WRITTEN BY YOUR Alan Smith
LINK TO SURVEY WHEN SURVEYED BY GROUP
This technique is appropriate when developers are considering support for a device’s supported accessibility controls such as:
- Text resizing/reflowing and fonts for: 1) iOS - Dynamic Type, 2) Android - Scale-independent pixel units (SP), 3) Recommendation: text font sizing should not be hard coded
- External keyboard or other input device support
- Colors and contrasts
- Screen reader
- Speech to text
- Sound or tactile feedback of keyboard entry/link or button activation
- Touch, hold and/or tapping controls
- Assistive technology modified device gestures
- Screen or image motion controls
- Flashing/sound/vibration for alerts/notifications
- Accessibility shortcuts: Keyboard or gesture
- Braille Device support
- TTY and Video Relay Service
THE LIST OF SUCCESS CRITERIA, GUIDELINE, OR CONFORMANCE REQUIREMENT RELATED TO THIS TECHNIQUE IN THE FOLLOWING FORMAT:
- the anchor for that item. Copy the anchor from the success criterion URI address;
- the number of the item;
- the short name for the item;
- text-equiv-all: SC 1.1.1 Non-text Content
- Resize text: 1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)
- Predictable: 3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)
- G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes
- G142: Using a technology that has commonly-available user agents that support zoom
User Agent and Assistive Technology Support Notes
ANY NOTES REGARDING KNOWN LACK OF SUPPORT FOR THIS TECHNIQUE WITH USER AGENTS OR ASSISTIVE TECHNOLOGY.
MAIN TEXT OF THE TECHNIQUE. TECHNIQUES BEGIN WITH "The objective of this technique is to..." , DESCRIBES WHAT THE USER SHOULD ACCOMPLISH, THEN HOW TO ACCOMPLISH IT.
THE TECHNIQUE AND HOW IT SHOULD WORK GOES HERE.
EXAMPLES AND CODE SAMPLES.
- Google: Layout > Units and measurements>Scaleable pixels (sp): http://www.google.com/design/spec/layout/units-measurements.html#units-measurements-scaleable-pixels-sp-
- Apple: iOS 7 UI Transition Guide>Using Fonts: https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/TransitionGuide/AppearanceCustomization.html
- LIST OF RELATED TECHNIQUE NUMBERS (e.g. H30)
DESCRIPTION OF THE TEST
ANY TEST FILES GO HERE (NOTE WORKING EXAMPLES INCLUDING SOURCE CODE SHOULD BE REFERENCED IN THE EXAMPLES SECTION).