← All articles 9 Mobile App Section 508 Rules You Must Meet How-to

9 Mobile App Section 508 Rules You Must Meet

Quick Summary

Yes, section 508 mobile apps are covered when a federal agency builds, buys or uses them. The standard applies by technology, not device, so native iOS apps, Android apps and mobile web pages all fall under the same accessibility requirements.

  • Covered apps include those built for agency staff or the public, plus apps licensed from a vendor.
  • Native, hybrid and progressive web apps must all meet the same accessibility outcomes.
  • Touch targets should meet platform minimums of 44x44 points on Apple and 48x48 pixels on Android.
  • Every swipe or pinch gesture needs a single-pointer button alternative.
  • Run manual screen reader tests every sprint, because automated scanners miss gestures and status announcements.
Need a Section 508 mobile app?Tech Ahir builds fixed-scope mobile and SaaS products with accessibility tested from day one.
Talk About Your App

Table of Contents

What Section 508 Requires for Software and ICT

Last Updated: November 12, 2026

Yes, when a federal agency builds, buys or uses them.

Section 508 sets technical standards, not a design style. Agencies must make software usable by people who rely on screen readers, screen magnifiers, voice input and keyboard-only navigation. Enforcement runs through federal procurement, so vendors selling to agencies must prove conformance.

The current technical baseline points to WCAG 2.0 Level AA. The same success criteria that guide accessible websites also guide accessible software.

  • Software must work with assistive technology
  • Interfaces must offer keyboard and touch access
  • Content must be perceivable, including text alternatives for images
  • Agencies typically document conformance in a Voluntary Product Accessibility Template (VPAT)

Watch out: a VPAT that claims conformance without test evidence will not survive an agency review.

Does Section 508 Apply to Mobile Applications?

Yes. Section 508 applies to mobile apps built for or used by federal agencies. Its scope is defined by the technology, not the device, so a native iOS app, an Android app or a mobile web page falls under the same requirements when an agency procures or deploys it.

The question is less whether mobile is covered than how the standard maps to small screens and touch input. Many teams assume a responsive website is enough, but it rarely is: native platform controls, gestures and screen reader behavior differ from a browser.

A practical way to frame it:

  • Covered: apps built for agency staff or the public
  • Covered: apps an agency licenses from a vendor
  • Covered: mobile web pages used as agency services
  • Often missed: internal tools that employees access on company phones

Native, Hybrid, and Web Apps Under the Rule

The rule does not favor one architecture. A native app, a hybrid app built with a framework like React Native or Flutter, and a progressive web app each have to meet the same outcomes. What changes is where the accessibility work happens.

Native apps expose platform accessibility APIs directly, giving strong screen reader support when built correctly. Hybrid apps depend on a bridge between web code and native controls, so testing the bridge matters. Web apps inherit browser support but still need custom gesture handling. Choose the architecture your team can test thoroughly; a faster build that cannot be verified will fail a federal review.

Section 508 Mobile App Requirements You Need to Meet

Section 508 mobile app requirements come down to concrete checks, and most failures stem from a short list of issues.

  1. Provide text alternatives for images, icons and buttons that carry meaning.
  2. Label every form field so screen readers announce what each input is for.
  3. Support dynamic text sizing so content reflows when users increase font size.
  4. Keep touch targets large enough to tap reliably, with comfortable spacing between them.
  5. Maintain sufficient color contrast for text and essential graphics.
  6. Announce status changes such as errors, loading states and success messages.
  7. Allow alternatives to gestures so a swipe or pinch has a button equivalent.
  8. Keep focus order logical when a user moves through screens with assistive technology.
  9. Avoid time limits that cannot be extended or turned off.
  10. Document conformance with an accurate VPAT that reflects actual test results.

WCAG for Mobile Apps: Mapping the Standard to Touch Interfaces

WCAG was written for the web, so mapping it to mobile requires interpretation.

Touch target size (2.5.5 Target Size, Level AAA; 2.5.8 Target Size Minimum, Level AA in WCAG 2.2). WCAG 2.0 AA has no target-size criterion, which surprises teams. Meet the platform minimums, which exceed the WCAG 2.2 floor: Apple's Human Interface Guidelines call for a 44x44 point hit area, and Google's Material guidance calls for 48x48 density-independent pixels. WCAG 2.2 sets a 24x24 CSS-pixel floor, but a federal reviewer testing on a phone will notice a 24-pixel button immediately. Build to the platform number, not the legal floor.

Pointer gestures (2.5.1). Functionality operated by a path-based or multipoint gesture must also work with a single pointer without an ambiguous path.

Orientation (1.3.4). Content must not restrict display to a single orientation unless a specific orientation is essential.

Status messages (4.1.3). Errors, loading states and success confirmations must be announced to assistive technology without moving focus.

Name, role, value (4.1.2). Every custom control needs an accessible name, the correct role, and its current state exposed.

Focus and reading order (2.4.3). Accessibility focus order must follow a logical sequence.

Section 508 Mobile App Testing Step by Step

Testing is where most mobile projects stall, and where the SERP is thinnest: competitors describe the law and stop. The process below is built for mobile specifically and feeds a repeatable pipeline rather than a one-time audit.

QA engineer testing a tablet with a screen reader for section 508 mobile compliance in a bright office.
QA engineer testing a tablet with a screen reader for section 508 mobile compliance in a bright office.
  1. Inventory screens and flows, not just screens. List every screen plus every reachable state: sign-in, empty, error, permission prompts, settings and modals. A screen that passes in its default state can fail in its error state, where status-message failures cluster.
  2. Run automated scans first, then treat them as a floor. Automated scanners and platform accessibility tools catch missing labels, low contrast and small touch targets quickly. They do not catch gesture-only interactions, focus order or unannounced status changes. Budget manual time for those three categories.
  3. Test with a screen reader, task by task. Use VoiceOver on iOS and TalkBack on Android. Complete each core task with the screen reader on and the screen off, logging every point where you had to guess. This is the highest-yield mobile test and the one most teams skip under schedule pressure.
  4. Test dynamic text at the system maximum. Set the largest accessibility text size, not a moderate bump, and check every screen for clipping, overlap and truncated labels. Repeat at 200 percent zoom for web views inside the app.
  5. Test switch control and keyboard where supported. iOS supports Full Keyboard Access and Switch Control; Android supports Switch Access. Confirm focus is visible and the order is logical.
  6. Audit gestures against 2.5.1. For every swipe, pinch, long-press or drag, confirm a single-pointer alternative exists and is discoverable. Log the alternative, not just the defect.
  7. Log each defect with the criterion, device, OS version and reproduction path. Include the assistive technology and version used. A defect without a reproduction path gets argued about instead of fixed.
  8. Assign severity against release risk. A missing label on a decorative icon is low; an unannounced error on a payment form is a blocker. Severity drives whether the build ships and lets an accessibility owner actually block a release.
  9. Retest against the original defect and record the result. Keep the evidence attached to the release record, because agencies ask for it during procurement and audits.

Folding Testing into CI/CD

This is the part competitors miss. A mobile app ships continuously, so a launch-time audit decays within a few sprints. Run automated accessibility checks on every pull request that touches UI code, fail the build on new critical findings, and schedule manual screen reader passes for each sprint that changes a core flow.

Two mobile-specific traps deserve their own gate. First, third-party SDKs, analytics, chat, payment, and ad libraries, inject UI you did not build and cannot easily fix, so review each SDK's accessibility behavior before adoption and pin versions. Second, OS updates change accessibility APIs yearly; test on the current and previous major OS versions, because a control that announced correctly last year may not this year.

Watch out: a VPAT updated only at launch will drift out of accuracy within a few releases, and an inaccurate VPAT is worse than a thin one during an agency review.

A QA engineer testing a tablet app with a screen reader enabled, hands resting on a laptop beside the device in a bright office

The article breaks mobile Section 508 testing into concrete steps, each with the tool or frequency it calls for.

Step What to do Frequency or tool
Inventory screens and flows List every screen and reachable state, including error and permission prompts Once per build scope
Run automated scans Catch missing labels, low contrast and small touch targets Floor only, not sufficient alone
Screen reader testing Complete each core task with VoiceOver or TalkBack Highest-yield mobile test
Dynamic text testing Check every screen at the largest system text size System maximum
Gesture audit Confirm a single-pointer alternative for each gesture Against criterion 2.5.1
Defect logging Record criterion, device, OS version and reproduction path Every defect
Retest and record Verify the fix and attach evidence to the release record Every release

Using a 508 Compliance Checklist for Mobile Releases

A 508 compliance checklist turns the standard into a release gate. Run it before every production build, not just at launch.

  • Every image and icon has an accessible name
  • All form fields have visible, programmatic labels
  • Screen reader announces errors and success messages
  • Text reflows at the largest system font size
  • Touch targets meet platform minimum sizes
  • Color contrast meets WCAG AA for text and key graphics
  • Every gesture has a button alternative
  • Focus order matches the visual order
  • No time limits without an option to extend
  • Test evidence is attached to the release record

A checklist does not replace testing. It makes sure testing happens every time.

Keeping Your Mobile App Compliant After Launch

Compliance is not a one-time project. Each OS update, new screen and third-party SDK can break accessibility, and many teams pass a launch audit then drift out of conformance within a few releases.

Build the checks into your pipeline. Run automated accessibility scans on every pull request and schedule manual screen reader tests for each sprint that touches the UI.

Plan for OS changes. Apple and Google update accessibility APIs each year, and a feature that worked on last year's OS may behave differently now.

Assign an owner. Someone on the team should be responsible for accessibility, with the authority to block a release that fails the checklist.

Scoping Your Next Accessible Mobile Build with Tech Ahir

Building an accessible app is easier when accessibility is part of the plan from day one. At Tech Ahir, we build mobile and SaaS products for enterprise leaders and government contractors.

If you are scoping an accessible mobile app, book a free discovery call to walk through your requirements and a delivery timeline. If you need a working product quickly, see how our software factory approach works. You can also meet Manoj Ahir to learn about the engineering background behind our work.


Ready to talk about your application? Tech Ahir can help you scope, build and test a compliant mobile product that is ready for federal review.

Frequently Asked Questions

Does Section 508 apply to mobile applications?

Yes, when a federal agency develops, procures, maintains, or uses a mobile application, Section 508 of the Rehabilitation Act generally applies. The standard is technology-neutral, so native, hybrid, and web-based apps are all covered when they are part of federal electronic and information technology. Agencies and their contractors typically meet the requirement by conforming to the WCAG 2.0 Level AA success criteria, along with the functional performance criteria in the standard. Compliance should be verified through testing with assistive technology before release.

Is Section 508 compliance mandatory for federal agencies and contractors?

Section 508 compliance is mandatory for federal agencies when they develop, procure, maintain, or use electronic and information technology. Contractors who deliver ICT to federal agencies must provide products that meet the standard, and procurement teams often require a Voluntary Product Accessibility Template (VPAT) as evidence. Requirements can also flow down to subcontractors. Teams should confirm the specific contract language, because obligations depend on the scope of the work.

What should a Section 508 mobile app checklist include?

A useful 508 compliance checklist for mobile apps covers screen reader labels for all interactive elements, sufficient color contrast, touch target sizing, support for dynamic text scaling, keyboard or switch access where applicable, captions for audio and video, and clear focus order. It should also include testing on current iOS and Android versions with VoiceOver and TalkBack, plus documentation of any remaining issues. Reviewing the checklist at each release keeps compliance from drifting over time.

GoogleAdd techahir.com as a preferred source on Google →