Difference between revisions of "WCAG 2.1 Criteria that need to be tested on mobile devices"

From Level Access Web Labs
Jump to navigation Jump to search
(Changed "Use Case Testing" to "Use Case Scoping". This information section is true, but it must be scoped before the audit starts, not decided by testers in the middle)
(No difference)

Revision as of 22:40, 18 October 2018

Note: These are draft recommendations are provided as-is and subject to change without notice.

This page contains the WCAG 2.1 success criteria (at Level A and AA) and conformance requirements for web content that need to be tested on a mobile device. The list is limited as many criteria either can be tested on the desktop/laptop or may not be applicable -- for example SC 1.4.10 Reflow -- because mobile browsers don't support reflow.

Responsive page variations can easily be generated on desktop/laptop by changing browser zoom, user agent strings, viewport width or by using developer tools to switch to mobile view. Pages that only trigger variations based actual mobile devices that can't be simulated are rare today.

For sites with two separate code based for mobile and desktop/laptop the same principles would generally apply.

Criteria and Conformance Requirements

  • WCAG Conformance Requirement - Full Pages - page variations (when specific automatically created variations cannot be presented on desktop/laptop) (Seen by many as also applicable to WCAG 2.0)
  • WCAG Conformance Requirement - Accessibility Support - Implementation techniques that supports Assistive technology used on mobile devices such as Talkback, VoiceOver, and switch control. (Also applicable to WCAG 2.0)
  • SC 1.3.4 Orientation
  • SC 2.5.1 Pointer Gestures (only when touch gestures are offered that are different from mouse pointer gestures)
  • SC 2.5.2 Pointer Cancellation (only when touch gestures are offered that are different from mouse pointer gestures)
  • SC 2.5.4 Motion actuation
  • Any functionality that can only be tested on a mobile device -- in general services like camera, geolocation, etc. are available on desktop/laptop -- but if such service is not available then that function for SC would need to be tested on one or more mobile platforms depending on the scope of the audit.

Which SC must be tested Again on desktop/laptop when RWD is triggered

Changes in RWD are not just aesthetics and can trigger different controls, new content, hiding of certain content, different styles, etc. and all re-testing of most SC in different RWD breakpoints will be needed.

  • Essentially all other SC must be re-tested again when RWD is encountered and when SC 1.4.4 Resize Text is tested as this triggers changes that includes responsive breakpoints. Because of this requirement be initiated with SC 1.4.4 Resize Text -- this recommendation applies to WCAG 2.0 as well.

Use Case Scoping

As use case testing is focused on functional outcomes of using assistive technology -- assistive technology and browser combinations that include mobile devices should be used for WCAG 2.1 audits. In addition, when RWD versions are in scope for a WCAG 2.0 audit use cases should include mobile assistive technology and browser combinations.