Back to all posts
Accessibility7 min read·October 25, 2026

What Accessibility Requirements Should Your App Include?

TB
ThynkBlox Apps Team
App Engineering

Mobile app accessibility design requirements should describe how each screen works with larger text, readable contrast, usable touch targets, screen readers and a clear focus order. Include an alternative for every gesture-only action, then turn those requirements into checks for complete tasks. Write them before development begins so accessibility is part of the agreed scope.

What should you decide before designing screens?

Start with the tasks people must complete: creating an account, finding an item, making a booking or changing a setting. For each task, describe what a person needs to perceive, understand and operate.

Avoid a broad instruction such as “make the app accessible”. Specify the expected behaviour, including loading, empty, error and confirmation states.

Use the same requirement format throughout:

  • Context: the screen, action and relevant device setting.
  • Expected behaviour: what remains readable or operable.
  • Acceptance check: how someone will demonstrate that it works.

Include these conditions when you scope an app MVP. Keep the feature list focused, while giving each included feature clear accessibility requirements.

What belongs in every screen requirement?

Use this table as a starting point, then add details for the actual screen.

AreaRequirement to writeAcceptance check
Text scalingDefine how content adapts to larger text settingsRead and complete the screen without clipped text or hidden actions
ContrastSet contrast criteria for text, controls and statesCheck each required colour pairing against the agreed criteria
Touch targetsDefine usable activation areas and spacingOperate adjacent controls without activating the wrong one
Screen-reader labelsSpecify names, roles, values and statesIdentify and operate controls without relying on their appearance
Focus orderDefine a meaningful navigation sequenceFollow the task without unexplained jumps or missing content
Gesture alternativesProvide another way to perform each gesture actionComplete the same task through visible controls

Record any unresolved criterion as a decision to make before approving the screen. A blank requirement should not silently become an implementation choice.

How should text behave when someone increases its size?

Require the screen to adapt to the text-size settings supported by the app. Specify the settings you will test and the expected behaviour at each.

Write requirements for buttons, forms, navigation, alerts and supporting text as well as headings. For important content, prefer wrapping, expanding containers or scrolling over cutting off words.

For example, require a booking screen to keep the service name, selected time, price and confirmation action readable at the largest agreed test setting. Allow the layout to stack vertically when necessary.

Also define exceptions explicitly. If a compact preview shortens a long description, provide a clear way to read the complete text. Do not apply that exception to instructions or errors needed to finish the task.

How should you specify contrast and visual states?

Choose a recognised accessibility reference appropriate to the platform and record the applicable contrast criteria in the design requirements. Agree those criteria before approving the colour palette.

List the combinations that need checking: body text, placeholder text, links, icons, input boundaries, selected controls and error messages. Include every supported theme and relevant background.

Require meaning to remain clear without colour alone. Pair an error colour with a written explanation. Give a selected option a visible marker as well as a colour change.

For text placed over an image, specify how readability will be preserved across different images. Review the actual screen states against the agreed criteria, rather than approving colours only as isolated swatches.

What should touch-target requirements include?

Describe the area that responds to a tap, not just the visible icon. Set minimum activation areas and spacing using the platform guidance selected for the project.

Make adjacent actions a deliberate review point. Examples include an item name beside a delete control, or a quantity control beside a checkout action.

Require the layout to preserve usable targets when text grows. Define feedback for taps and a way to recover from accidental actions where appropriate.

For custom controls, document their activation area in the screen specification. A drawing of a small icon does not tell the developer how much surrounding space should respond.

What should screen readers announce?

Specify the information needed to identify and use each control: its name, role, current value and relevant state. Define the intended announcement without prescribing one exact spoken sentence across every device.

Prefer labels that explain the action in context. “Remove saved address” is more useful than “Cross”. For repeated actions, include enough context to distinguish the item being changed.

For forms, require persistent field labels, clear instructions and errors associated with the relevant field. Define how changed values and important results become available to screen-reader users.

Mark decorative images as decorative. Give meaningful images descriptions that explain their purpose in the task. Avoid repeating nearby text unless the repetition serves a clear need.

What should happen to focus as the screen changes?

Write the navigation order in the sequence needed to understand and complete the task. Include headings, fields, supporting instructions and actions.

Specify what happens when a dialog opens, closes or reports an error. For example, require focus to enter a confirmation dialog and return to the control that opened it after cancellation.

For validation failures, make the error explanation and affected field reachable in a predictable order. Do not move focus merely because background content refreshes.

If the app supports a hardware keyboard or other focus-based input, define the relevant navigation checks separately. Verify each supported input method through the complete task.

Which gestures need another way to act?

For every swipe, drag, long press or multi-finger gesture, specify an alternative control that produces the same result.

Examples include:

  • A remove button alongside swipe-to-delete.
  • Move-up and move-down actions alongside dragging to reorder.
  • An options button alongside a long-press menu.
  • Zoom controls alongside pinch-to-zoom.

Require the alternative to be discoverable and labelled clearly. A hidden gesture explained only during onboarding is not a sufficient alternative.

Check that both methods preserve the same information, confirmation and recovery options.

What does a usable acceptance example look like?

Consider an illustrative appointment-booking screen. Its requirements could say:

  • At every agreed text-size setting, the service, time and confirmation action remain readable and reachable.
  • Each available time has a meaningful label and selected state.
  • Navigation follows the service details, date, available times and confirmation action.
  • Selecting an unavailable time produces an understandable message with a clear next step.
  • A visible date control provides an alternative to swiping between days.
  • Cancelling the confirmation dialog returns focus to the action that opened it.

These statements give design, development and testing a shared outcome. Add the chosen platform criteria and test settings before approving them.

What common mistakes should you avoid?

Treating accessibility as a final visual review. Include behaviour and acceptance checks before development, then verify the implemented screens.

Checking only the successful path. Include permission requests, unavailable options, expired sessions, validation errors and recovery.

Approving labels in isolation. Review repeated controls within the full screen so their meaning remains clear.

Using one check as proof of everything. Contrast checks, text-scaling checks and screen-reader task checks answer different questions. Keep evidence for each relevant requirement.

Promising legal compliance from a checklist. Define the accessibility scope and verification performed. Keep any legal assessment separate.

How should you verify the requirements before release?

Walk through each agreed task on the implemented app using the relevant settings and input methods. Record the screen, conditions, observed result and any unresolved issue.

Include accessibility scenarios in your Android app testing plan. Recheck affected tasks when layouts, navigation or shared controls change.

When the designs move to developers, use the mobile app design handoff checklist, and plan for multiple languages where they apply.

Keep the requirements alongside the product scope after launch so future changes have the same acceptance conditions.

Frequently asked questions

Should an MVP include accessibility requirements?

Yes. Write requirements for the tasks included in the MVP, including their errors and recovery paths. Limit features while keeping those tasks usable.

Do standard controls remove the need for testing?

Keep the same task checks even when using standard controls. Verify their labels, layout, state and behaviour within your screen.

Must every screen look identical at larger text sizes?

Allow the layout to change. Require the content, reading order and actions to remain understandable and usable.

Does meeting these requirements guarantee legal compliance?

No guarantee is made here. This article provides a planning framework for screen requirements. Obtain advice specific to your product and markets if you need a legal assessment. Shared components make these requirements easier to keep consistent; see the minimum design system for a mobile app.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.