Blank checklist, printable form

Mobile App Accessibility Checklist

EN 301 549 Chapter 11 + WCAG 2.2 AA for Native Mobile Apps

Blank checklist for offline completion.

Tick one box per row. Add comments and evidence references in the Notes column as needed.

Screen Reader Compatibility

EN 301 549 §11.1.1–§11.4, All UI elements must be accessible to platform screen readers (TalkBack, VoiceOver).

Ref	Severity	Requirement	Status
EN 301 549 §11.5.2.3	Critical	All interactive elements have accessible names exposed to the platform accessibility API.Every button, link, input, and control must have a programmatic name, via contentDescription (Android), accessibilityLabel (iOS), or visible text.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
EN 301 549 §11.5.2.5	Critical	All interactive elements expose their role to assistive technology.Buttons must be announced as buttons, checkboxes as checkboxes, links as links. Use platform-native controls or set accessibilityRole explicitly.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
EN 301 549 §11.5.2.7	Critical	State changes (expanded, selected, checked) are programmatically exposed.When a toggle changes, a dropdown expands, or a tab is selected, the screen reader must announce the new state automatically.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
EN 301 549 §11.5.2.12	Major	Focus follows a logical reading order matching visual layout.Screen reader swipe navigation must move through elements in a logical order, top to bottom, left to right.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A

EN 301 549 §11.1.2, Touch gestures, input methods, and keyboard/switch control must be accessible.

Ref	Severity	Requirement	Status
WCAG 2.5.1	Critical	Every swipe, pinch, or multi-finger gesture has a single-tap or button alternative.Pinch-to-zoom must have +/- buttons. Swipe-to-delete must have an explicit Delete button. No functionality should require complex gestures exclusively.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 2.5.8	Critical	Touch targets meet minimum 44×44pt (iOS) / 48×48dp (Android) size.Small buttons cause motor accessibility failures. Measure rendered size on actual devices. Padding counts toward tap area.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 2.1.1	Critical	Full keyboard and switch control navigation works for all flows.External keyboard users and switch control users must be able to complete every task.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 2.5.4	Major	No functionality relies on device motion (tilt, shake) without an alternative.Shake-to-undo must have a menu alternative. Tilt-to-scroll must have button controls.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
EN 301 549 §11.7	Major	App respects platform accessibility preferences (bold text, reduce motion, increase contrast).When the OS has 'Reduce Motion' enabled, the app must reduce or remove animations. 'Bold Text' should affect app typography.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A

WCAG 1.3–1.4 applied to native mobile UI, colour contrast, text resizing, orientation.

Ref	Severity	Requirement	Status
WCAG 1.4.3	Critical	Text colour contrast meets 4.5:1 ratio (3:1 for large text).Measure against all backgrounds including gradients and images.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 1.4.11	Major	Non-text UI components (icons, borders, focus rings) meet 3:1 contrast.Button borders, input outlines, icon graphics, all must have sufficient contrast against their background.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 1.4.4	Critical	Text resizes up to 200% via system settings without loss of content.Enable system font scaling and verify all text scales correctly. No truncation, overlap, or content hidden by overflow.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 1.3.4	Major	App works in both portrait and landscape unless one orientation is essential.Content should reflow for both orientations. Only lock orientation if the content genuinely requires it.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 1.4.1	Critical	Colour is not the only means of conveying information.Error states, status indicators, and selected states must use shape, text, or icons in addition to colour.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A

Alerts, haptics, and system notifications must be accessible through multiple sensory channels.

Ref	Severity	Requirement	Status
EN 301 549 §5.1.3.1	Critical	Notifications are available in text form, not just sound or vibration.Push notifications must include readable text. Haptic-only or audio-only alerts exclude deaf and deafblind users.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
EN 301 549 §5.1.3.1	Major	Haptic feedback has a non-haptic alternative.Users who cannot perceive vibration need visual or audio confirmation for haptic events.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 4.1.3	Major	Status messages are announced by the screen reader without focus change.Toast messages, loading indicators, and form submission confirmations must use platform accessibility announcements.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A

Ref	Severity	Requirement	Status
EN 301 549 §5.3	Critical	Biometric login (fingerprint, face) has a PIN/password fallback.Not all users can use biometrics. A non-biometric path must always exist.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 2.2.1	Major	Session timeouts warn the user and allow extension.Display a warning at least 20 seconds before timeout. Allow the user to extend. Do not silently log out.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A
WCAG 3.3.8	Major	Authentication does not require cognitive function tests (CAPTCHAs) without an accessible alternative.CAPTCHAs are barriers for many users. Use alternative verification methods.	☐ Pass ☐ Partial ☐ FAIL ☐ N/A