Accessibility Test Cases

A11Y-MOB-020

Android interruption and recovery

Generated file current Authoring: Content complete
What file status means

This status reports only whether the generated procedure matches the current controlled source hash. It is not independent content verification, regulatory approval, product evidence or a conformance decision.

Recorded standards review: No optional specialist review recorded. Next review: Not scheduled.

MethodMobile accessibility journey
TesterExperienced mobile accessibility tester
Indicative effort69–100 min small scope

Checks android interruption and recovery on physical supported mobile hardware.

Available formats

Use this test in the format you need

The HTML procedure includes the working worksheet. JSON provides the structured source data. Editable Markdown files are delivered inside package downloads.

Purpose

What this test checks

Checks android interruption and recovery on physical supported mobile hardware.

What this result means: This procedure records how Android interruption and recovery behaves on android-alternative-input. It can expose evidence relevant to WCAG 1.3.4, 1.4.10, 2.1.1, 2.4.11 and 2.5.8 for the tested task and environment. Use the linked conformance procedures for WCAG 1.3.4, 1.4.10, 2.1.1, 2.4.11 and 2.5.8 to assess the complete requirements across the declared conformance scope.

Why it matters

Checks android interruption and recovery on physical supported mobile hardware. People most likely affected: disabled mobile users who rely on voice, switches, keyboards, magnification, captions, reduced motion or adapted input. The named mobile configuration may prevent task completion, error recovery or state preservation. In the recorded android-alternative-input environment, exercise the physical device in each required orientation, text size and input mode; touch geometry, on-screen keyboards, system bars and responsive state changes can expose device-only blockers.

When to use it

Apply Android interruption and recovery when the frozen mobile task executed on the named physical device and input or display configuration. The selected focus is Android interruption and recovery.

Confirm before starting

Mark it not applicable only when

Exceptions

This platform, journey, usability or quality procedure creates no additional normative exception. Apply exceptions only in the linked atomic or criterion-level conformance procedure and preserve that separate decision.

Prepare

What you need

  • The product area and test targets are agreed before testing starts.
  • The operating system, browser, viewport and input method are recorded.
  • Test data is safe to use and does not expose unnecessary personal information.

Targets and required variations

  • The selected complete task and states relevant to Android interruption and recovery on physical hardware.
  • Default, revealed, loading, empty, validation error, interruption, recovery and confirmation where meaningful.
  • Every required environment, viewport, orientation, language and authenticated state recorded in the frozen scope.

Clean state

  • Complete a known-good calibration in the same environment before product testing.
  • Start from a recorded clean or known state and preserve any prior preferences, extensions, cache or profile settings that can affect output.

Effort estimate

Setup
20 min
Per target
25 min
Evidence
12 min
Technical review
12 min

Assumptions: one short app journey on one physical device; repeat platforms, orientations and accessibility-service configurations separately

Variation: Add a new per-target execution and evidence allowance for each additional target class or state that could produce a different result. Add setup time for each distinct environment.

Excluded: Client coordination, inaccessible-environment recovery, recruitment, legal review, remediation implementation and waiting time unless the procedure states otherwise.

Execute

Test steps

Follow each action in order. The expected result is always visible; open the guidance when you need setup, tool, evidence, decision or repeat details. Step-level recording is optional while work is in progress and required only to export a completed execution.

Step 1

Prepare the scope, target and environment

Purpose: For Android interruption and recovery, prepare the named scenario: Prepare the scope, target and environment. Target: The selected complete task and states relevant to Android interruption and recovery on physical hardware. The preparation must establish this result: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.

User impact: The named mobile configuration may prevent task completion, error recovery or state preservation. This scenario isolates that risk in the action named Prepare the scope, target and environment.

Before executing Android interruption and recovery, freeze the product version and scope. Inventory each applicable target, select the required starting states, prepare safe test data and record every required environment value. Complete any named known-good calibration before attributing an observation to the product.

Expected result

The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.

Failure observation

During Android interruption and recovery, the target, starting state, environment or scope record remains ambiguous for the scenario named Prepare the scope, target and environment. The preparation result cannot be demonstrated: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.

Setup, evidence and decision guidance
Target
The selected complete task and states relevant to Android interruption and recovery on physical hardware.
Required state
For Android interruption and recovery, the product version and scope are frozen; every selected target and material starting state is uniquely identified.
Tool or command
Use the scope record and worksheet environment fields for Android interruption and recovery: operating_system, operating_system_version, browser, browser_version, viewport_css_pixels, input_method, assistive_technology, assistive_technology_version, device_model, orientation.
Record
Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.
Pass
Record passed for the Android interruption and recovery scenario named Prepare the scope, target and environment only when the evidence (Scope/version reference; target inventory; starting states; safe-data reference; every required environment value; calibration result or reason it is not required.) supports: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.
Fail
Record failed when the action is completed and this failure observation is reproduced: During Android interruption and recovery, the target, starting state, environment or scope record remains ambiguous for the scenario named Prepare the scope, target and environment. The preparation result cannot be demonstrated: The selected targets, states, test data, environment and any scope limitations are complete enough for another qualified tester to reproduce the setup.
Not applicable
The frozen mobile scope contains no task, control or media relevant to Android interruption and recovery.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
For Android interruption and recovery, correct the setup gap, preserve the original blocked record and start a new execution observation before proceeding.
Limitations
This scenario records the action named Prepare the scope, target and environment for Android interruption and recovery in android-alternative-input. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.
If you are new to this test
For Android interruption and recovery, do not begin from an undocumented browser tab, document copy, device state, participant plan or evidence set. Record the exact item you will test first.
Record this step

Step 2

During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss

Purpose: For Android interruption and recovery, execute the named scenario: During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss. Target: The selected complete task and states relevant to Android interruption and recovery on physical hardware. Compare the observation with this result: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.

User impact: The named mobile configuration may prevent task completion, error recovery or state preservation. This scenario isolates that risk in the action named During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss.

During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss.

Expected result

Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.

Failure observation

After the tester completes the Android interruption and recovery scenario named During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss, the recorded observation for the target is inconsistent with the required result: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.

Setup, evidence and decision guidance
Target
The selected complete task and states relevant to Android interruption and recovery on physical hardware.
Required state
For Android interruption and recovery, begin in the recorded task position immediately before the interruption, with recoverable input already entered; preserve the exact content, account, platform and configuration used.
Tool or command
In android-alternative-input, Use the named accessibility feature on the recorded physical iOS, iPadOS or Android device. Follow the platform's current first-party setup path and perform the exact gesture, switch, keyboard or voice command stated in the action.
Record
Success, validation error, interruption, recovery and confirmation evidence plus every fallback. Capture screen recording, displayed speech/command output or detailed contemporaneous notes and record every fallback intervention.
Pass
Record passed for the Android interruption and recovery scenario named During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss only when the evidence (Success, validation error, interruption, recovery and confirmation evidence plus every fallback. Capture screen recording, displayed speech/command output or detailed contemporaneous notes and record every fallback intervention.) supports: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Android interruption and recovery scenario named During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss, the recorded observation for the target is inconsistent with the required result: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.
Not applicable
The frozen mobile scope contains no task, control or media relevant to Android interruption and recovery.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat success, error and recovery paths without falling back to unrecorded touch or visual assistance. Repeat in portrait and landscape where supported and through backgrounding, interruption, validation and recovery states that can change the task. Preserve the first Android interruption and recovery observation when repeating.
Limitations
This scenario records the action named During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss for Android interruption and recovery in android-alternative-input. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.
If you are new to this test
For Android interruption and recovery: Record device model, operating-system version, app or browser version, orientation and accessibility-feature configuration before testing; emulators and desktop device modes are diagnostic only.
Record this step

Step 3

Repeat material variations and recovery

Purpose: For Android interruption and recovery, execute the named scenario: Repeat material variations and recovery. Target: The selected complete task and states relevant to Android interruption and recovery on physical hardware. Compare the observation with this result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

User impact: The named mobile configuration may prevent task completion, error recovery or state preservation. This scenario isolates that risk in the action named Repeat material variations and recovery.

Repeat the Android interruption and recovery action for each inventoried variation that can change the outcome. Include relevant default, revealed, error, interruption, recovery and confirmation states and complete the selected process from start to finish where this test can affect task completion.

Expected result

Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Failure observation

After the tester completes the Android interruption and recovery scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.

Setup, evidence and decision guidance
Target
The selected complete task and states relevant to Android interruption and recovery on physical hardware.
Required state
For Android interruption and recovery: Default, revealed, loading, empty, validation error, interruption, recovery and confirmation where meaningful. Every required environment, viewport, orientation, language and authenticated state recorded in the frozen scope.
Tool or command
For Android interruption and recovery, use the same recorded method, then change only the state, environment or recovery condition being compared.
Record
Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.
Pass
Record passed for the Android interruption and recovery scenario named Repeat material variations and recovery only when the evidence (Variation identifier; changed state or environment; start and end points; actual observation; recovery result; intervention; evidence reference and target outcome.) supports: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Fail
Record failed when the action is completed and this failure observation is reproduced: After the tester completes the Android interruption and recovery scenario named Repeat material variations and recovery, the recorded observation for the target is inconsistent with the required result: Every material variation and required recovery path has its own reproducible observation; no unexecuted state is merged into a passing result.
Not applicable
The frozen mobile scope contains no task, control or media relevant to Android interruption and recovery.
Blocked
Record blocked, not passed, when An applicable target, required state, complete process or named real environment was not executed.
Repeat or recover
Repeat this action for every required variation of Android interruption and recovery and after a material target, content, state, environment or configuration change. Preserve the original observation.
Limitations
This scenario records the action named Repeat material variations and recovery for Android interruption and recovery in android-alternative-input. It does not establish behaviour for another target, state or environment and does not set a WCAG conformance decision.
If you are new to this test
For Android interruption and recovery, change one material condition at a time where practical. Do not assume that a passing default state covers errors, overlays, orientation changes, interruptions or recovery.
Record this step

Decide

How to decide

Passed

Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.

Failed

An applicable Android interruption and recovery target has a reproducible material barrier against one or more stated expectations; identify the exact expectation, state and evidence.

Not applicable
The frozen mobile scope contains no task, control or media relevant to Android interruption and recovery.
Cannot tell
The target is applicable, but conflicting evidence or unresolved responsibility prevents a defensible expectation decision after recorded comparison.
Not tested
An applicable target, required state, complete process or named real environment was not executed.
Aggregation and reporting boundaries

Aggregation: Preserve every target/environment outcome. Any failed target prevents an overall passed procedure result. cantTell and untested remain unresolved; inapplicable is valid only when the completed inventory contains no applicable target.

WCAG decision: This specialist, platform, document, usability or quality result does not set a WCAG success criterion to satisfied or not_satisfied automatically. Use linked atomic and criterion-level procedures for that separate decision.

Automation: A checker, accessibility-tree inspection, emulator or simulated assistive technology is diagnostic evidence only. Complete every required manual, real-platform, contextual and exception check.

Record

Record the result

Record the target, state and observed behaviour. Add evidence or technical details only when needed.

Choose the option that best matches what happened to this target.

Describe the actual behaviour and why it supports the selected result.

When more than one target is recorded, the overall procedure result is calculated from all target results.

Environment: Not set.
Add evidence or details

Choose only the group needed for this record. These fields remain optional for a working draft.

Evidence references

Enter one file name, issue ID or evidence reference per line. Files stay on your device.

Test environment

Save a named profile once to reuse the same product, platform and environment details on other procedures in this browser.

Engagement and tester identifiers

Assistive-technology execution confirmation

Use these statements only for work actually performed. Simulation or accessibility-tree inspection does not count as real assistive-technology coverage.

Formal completion and limitations

Identify the frozen list or sampling record used to select every target represented by this execution.

Choose a final result before marking the execution complete. Completed records require the full environment, step, evidence and method-specific information.

Data management

Export before clearing if the record must be retained. Apply the engagement retention schedule and delete browser data when it is no longer needed.

Saved drafts stay in this browser and are not uploaded. Do not enter credentials, secrets or unnecessary personal data.

Reference

Supporting information

Standards and requirement mappings
  • W3C-WCAG22 · 1.3.4 secondary · partial

    This Mobile accessibility journey observes Android interruption and recovery in the recorded android-alternative-input environment. Use the linked WCAG 1.3.4 conformance procedure to evaluate all normative parts of WCAG 1.3.4 across the declared scope.

  • W3C-WCAG22 · 1.4.10 secondary · partial

    This Mobile accessibility journey observes Android interruption and recovery in the recorded android-alternative-input environment. Use the linked WCAG 1.4.10 conformance procedure to evaluate all normative parts of WCAG 1.4.10 across the declared scope.

  • W3C-WCAG22 · 2.1.1 secondary · partial

    This Mobile accessibility journey observes Android interruption and recovery in the recorded android-alternative-input environment. Use the linked WCAG 2.1.1 conformance procedure to evaluate all normative parts of WCAG 2.1.1 across the declared scope.

  • W3C-WCAG22 · 2.4.11 secondary · partial

    This Mobile accessibility journey observes Android interruption and recovery in the recorded android-alternative-input environment. Use the linked WCAG 2.4.11 conformance procedure to evaluate all normative parts of WCAG 2.4.11 across the declared scope.

  • W3C-WCAG22 · 2.5.8 secondary · partial

    This Mobile accessibility journey observes Android interruption and recovery in the recorded android-alternative-input environment. Use the linked WCAG 2.5.8 conformance procedure to evaluate all normative parts of WCAG 2.5.8 across the declared scope.

  • W3C-MOBILE · W3C-MOBILE platform · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • GOOGLE-ANDROID-TESTING · GOOGLE-ANDROID-TESTING platform · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

  • W3C-WCAG22-TECHNIQUES · W3C-WCAG22-TECHNIQUES platform · supporting

    This source does not override WCAG or create an additional WCAG conformance requirement.

Supporting and advisory guidance

Supporting sources are identified in the mappings and source register. They do not add conformance requirements.

Evidence specification
  • Physical device record

    Device model, operating system, browser/app, accessibility feature/input, versions, orientation and settings.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

  • Interaction sequence

    Exact command, gesture, switch, key or setting and resulting target/focus/state.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

  • Journey record

    Success, validation error, interruption, recovery and confirmation evidence plus every fallback.

    Reference or redact sensitive material. Do not store credentials, secrets, unnecessary personal data or unconsented participant data.

Worked example and outcome calibration

A11Y-MOB-020-WORKED-001: representative worked example

Context: Representative synthetic example for Android interruption and recovery on a fictional, version-frozen product target; no client or participant execution occurred.

Inspected: The tester follows S2 (During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss) using the target, required state, tool and repeat rule stated in this procedure.

Observed output: After the tester completes the Android interruption and recovery scenario named During a critical task on physical Android, background/foreground the browser, lock/unlock, receive an allowed interruption and recover after connectivity loss, the recorded observation for the target is inconsistent with the required result: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.

Evidence:

  • example-evidence-001: target and state record for The selected complete task and states relevant to Android interruption and recovery on physical hardware.
  • example-evidence-002: contemporaneous observation from the named method — Success, validation error, interruption, recovery and confirmation evidence plus every fallback. Capture screen recording, displayed speech/command output or detailed contemporaneous notes and record every fallback intervention.
  • example-evidence-003: comparison note linking the actual observation to the expected result and claim boundary

Tester reasoning: The recorded observation does not demonstrate the expected result: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry. The failed decision is limited to this synthetic target and state; unexecuted coverage is not inferred.

Decision: failed

Finding: A11Y-MOB-020-example-finding-001 — Android interruption and recovery: expected result is not demonstrated. The represented barrier may affect Disabled mobile users who rely on voice, switches, keyboards, magnification, captions, reduced motion or adapted input.

Remediation: Change the represented target or process so it demonstrates this result: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry. Then rerun the affected step and every dependent variation.

Reviewer feedback: The reviewer confirms applicability, environment, actual-versus-expected comparison, evidence references and bounded wording; unsupported product-wide or conformance language is removed.

Final client wording: Synthetic training finding: the sampled Android interruption and recovery target does not meet the procedure expectation in the recorded state. User impact and broader scope require evidence from the buyer's real execution.

Retest: Synthetic retest example: after the represented change, repeat the failed step plus material error and recovery states. Close the finding only when new evidence demonstrates the expected result; otherwise retain the non-pass outcome.

Boundary: This is a representative, synthetic worked example for training and calibration. It is not evidence from a client product, participant or real assistive-technology execution.

Outcome calibration

Passed
In android-alternative-input, the selected Android interruption and recovery target completes the recorded action and meets this expectation: Data, focus/context and accessible status recover predictably without forcing inaccessible re-entry.

The example is a calibration scenario, not an execution or approval.

Failed
An applicable Android interruption and recovery target produces a reproducible barrier during the named action, with the exact state and affected user task recorded.

A failed target remains failed even if another environment or target passes.

Not applicable
The frozen mobile scope contains no task, control or media relevant to Android interruption and recovery.

Inapplicable requires a completed inventory showing that no target matches applicability; a missing environment is not inapplicable.

Cannot tell
The Android interruption and recovery target is applicable, but conflicting product/platform evidence or missing authoritative information prevents a defensible responsibility or expectation decision.

Record the conflict, comparisons attempted and person or evidence needed to resolve it.

Not tested
The Android interruption and recovery target is applicable, but a required state, complete process or real environment was not executed.

Untested remains incomplete and cannot be converted to passed or inapplicable.

Sampling, complete processes and platform limitations

Run each selected critical journey from start to finish, including its main error and recovery paths. Record which journeys and states were included.

If this check is part of a user journey, test the selected journey from start to finish, including relevant errors and recovery. Record any path that was not tested.

  • Only the recorded physical-device execution counts. Results do not represent every device, operating-system release or accessibility configuration.
  • Check relevant browser, tool or assistive-technology release notes before assigning unexpected behaviour to the product.
  • If responsibility is unclear, record the reproducible behaviour and use cannot tell until it is resolved.
Related procedures
  • A11Y-WCAG-010
  • A11Y-WCAG-017
  • A11Y-WCAG-021
  • A11Y-WCAG-034
  • A11Y-WCAG-040
ACT rules and WCAG technique traceability

This is a project-authored manual procedure, not a W3C Approved ACT Rule. An ACT result can support only the part of this procedure covered by that rule. It does not replace the remaining manual or assistive-technology checks.

No supporting W3C Approved ACT Rule is selected for this procedure.

  • Understanding SC 1.3.4. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 1.4.10. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 2.1.1. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 2.4.11. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
  • Understanding SC 2.5.8. Techniques are examples, not extra requirements. Record any technique or common failure used, but decide the result against the success criterion.
Review history and source register
  1. 2026.08.27-rc.9 — Reworked for plain language, case-focused steps, scoped evidence and transparent draft review status.
  2. 2026.08.27-rc.9 — Migrated to professional catalogue schema v3 with separated outcomes, structured authority, applicability, evidence, decision and review records.
  3. 2026.08.27-rc.9 — Specialist procedure mapped to its task family and current first-party platform guidance and checked for internal consistency; competent review and real execution remain separate.
  4. 2026.08.27-rc.9 — Added explicit preparation and variation/recovery steps plus a bounded representative worked example for paid-template use.
  5. 2026.08.27-rc.9 — Procedure guidance and presentation simplified without changing draft governance status.

Review decision: pending. Open issues: Execute all required real environments and calibration cases.; Complete a distinct competent review and retain any unresolved material finding as blocked or cantTell.

Source historyReport an accuracy issue
WCAG
SC 1.3.4, SC 1.4.10, SC 2.1.1, SC 2.4.11, SC 2.5.8
Execution
Real device and assistive technology
Catalogue version
2026.08.27-rc.9