Guidelines categorised as Must or Must not are best practices that can easily be tested with specific criteria that is not subjective and is technologically possible to achieve with current assistive technology on mobile devices.

Guidelines categorised as Should or Should Not are less testable but considered core to accessible mobile website and apps.


  1. Use platform and web standards as intended
  2. Use standard interface controls where possible
  3. Support platform accessibility

Audio and video

  1. Alternatives for audio and visual content : Must : Alternative delivery, such as subtitles, sign language, audio description and transcripts, must be provided with embedded media when available.
  2. Autoplay : Must not : Audio must not play automatically unless the user is made aware this will happen or a pause/stop/mute button is provided.
  3. Metadata : Should : Relevant metadata should be provided for all media.
  4. Volume control : Should : Separate volume controls should be provided for background music, ambient sounds, narrative and editorially significant sound effects.
  5. Audio conflict : Should Not : Narrative audio in games or interactive media should not talk over or conflict with native assistive technology.


  1. Colour contrast : Must : The colour of text and background content must have sufficient contrast.
  2. Colour and meaning : Must not : Information or meaning must not be conveyed by colour only.
  3. Styling and readability : Must : Core content must still be accessible when styling is unsupported or removed.
  4. Touch target size : Must : Touch targets must be large enough to touch accurately.
  5. Spacing : Should : An inactive space should be provided around actionable elements.
  6. Content resizing : Must : Users must be able to control font sizing and user interface (UI) scaling.
  7. Actionable elements : Must : Links and other actionable elements must be clearly distinguishable.
  8. Visible focus : Must : When focused, all actionable and focusable elements must have a visible state change.
  9. Consistency : Should : A user's experience should be consistent.
  10. Choice : Must : Interfaces must provide multiple ways to interact with content.
  11. Adjustability : Should : Interactive media, including games, should be adjustable for user ability and preference.
  12. Flicker : Must not : Content must not visibly or intentionally flicker or flash more than three times in any one-second period.


  1. Consistent labelling : Should : Consistent labelling should be used across websites and native applications as well as within websites and applications.
  2. Indicating language : Must : The language of a page or app must be specified, and changes in language must be indicated.
  3. Instructions : Should : When needed, additional instructions should be provided to supplement visual and audio cues.


  1. Focusable elements : Must : All interactive elements must be focusable and inactive elements must not be focusable.
  2. Keyboard trap : Must not : There must not be a keyboard trap.
  3. Content order : Must : Content order must be logical.
  4. Focus order : Must : Actionable content must be navigable in a meaningful sequence.
  5. User interactions : Must : Actions must be triggered when appropriate for the type of user interaction.
  6. Alternative input methods : Must : Alternative input methods must be supported.


  1. Labelling form controls : Must : All form controls must be labelled.
  2. Form inputs : Must : A default input format must be indicated and supported.
  3. Form Layout : Must : Labels must be placed close to the relevant form control, and laid out appropriately.
  4. Grouping form elements : Must : Controls, labels, and other form elements must be properly grouped.
  5. Managing focus : Must not : Focus or context must not automatically change during user input.


  1. Images of text : Should : Images of text should be avoided.
  2. Background images : Must : Background images that convey information or meaning must have an additional accessible alternative.


  1. Descriptive links : Must : Link and navigation text must uniquely describe the target or function of the link or item.
  2. Links to alternative formats : Must : Links to alternative formats must indicate that an alternative is opening.
  3. Combining repeated links : Must : Repeated links to the same resource must be combined within a single link.


  1. Inclusive notifications : Must : Notifications must be both visible and audible.
  2. Standard operating system notifications : Should : Standard operating system notifications should be used where available and appropriate.
  3. Error messages and correction : Must : Clear error messages must be provided.
  4. Feedback and assistance : Should : Non-critical feedback or assistance should be provided when appropriate.

Scripts and dynamic content

  1. Progressive functionality : Must : Apps and websites must be built to work in a progressive manner that ensures a functional experience for all users.
  2. Controlling media : Must : Media that updates or animated content must have a pause, stop or hide control.
  3. Page refreshes : Must not : Automatic page refreshes must not be used without warning.
  4. Timeouts : Must : A timed response must be adjustable.
  5. Input control : Should : Interaction input control should be adaptable.


  1. Unique page/screen titles : Must : All pages or screens must be uniquely and clearly identifiable.
  2. Headings : Must : Content must provide a logical and hierarchical heading structure, as supported by the platform.
  3. Containers and landmarks : Should : Containers should be used to describe page/screen structure, as supported by the platform.
  4. Grouped elements : Must : Controls, objects and grouped interface elements must be represented as a single accessible component.

Text equivalents

  1. Alternatives for non-text content : Must : Alternatives must briefly describe the editorial intent or purpose of the image, object, or element.
  2. Decorative content : Must : Decorative images must be hidden from assistive technology.
  3. Tooltips and supplementary information : Must not : Tooltips must not repeat link text or other alternatives.
  4. Roles, traits and properties : Must : Elements must have accessibility properties set appropriately.
  5. Visual formatting : Must not : Visual formatting alone must not be used to convey meaning.


  1. Offer a core accessible website
  2. Use progressive enhancement
  3. Link mobile and desktop sites
  4. Minimise text fields