Skip to content

mobile-accessibility-reviewer

Review mobile React Native UI and federated modules for accessibility labels, roles, hints, states, focus handling, announcements, disabled/loading/error states, dynamic text scaling, design-token contrast, keyboard and screen reader behavior, and approved accessibility package usage. Use when reviewing mobile UI, forms, navigation, modals, cards, buttons, or federated UI surfaces.

active
IDE:
codex
Version:
1.0.0
Owner:optum-tech-compute
mobile
accessibility
react-native
a11y
review

Mobile Accessibility Reviewer

Use this skill to review mobile UI changes for screen-reader clarity, state communication, focus behavior, and accessible interaction patterns.

Workflow

  1. Inspect the UI flow, not just individual components: entry point, loading, empty, error, disabled, success, modal, and navigation states.
  2. Check labels, roles, hints, accessibilityState, accessibilityValue, hit targets, focus order, and announcements for dynamic changes.
  3. Check whether custom controls behave like native controls for screen readers and keyboard/switch access where applicable.
  4. Check contrast and text scaling against design tokens and platform accessibility expectations.
  5. For UHC Mobile federated modules, prefer approved @uhg-uhc-mobile/accessibility utilities when the package provides the needed helper.
  6. Report blocking accessibility defects first, then usability improvements and test gaps.

Review Focus

  • Missing or misleading accessibilityLabel, accessibilityRole, accessibilityHint, accessibilityState, or accessibilityValue.
  • Focus not moved or restored after modal, validation, navigation, loading, or async state changes.
  • Dynamic updates not announced where screen-reader users need confirmation.
  • Disabled, loading, empty, and error states that are visual-only.
  • Custom touch targets that are too small or do not expose control semantics.
  • Hard-coded colors or text sizing that bypass design tokens and scaling.

Output

  • Lead with findings ordered by severity, with file and line references when possible.
  • Separate blocking issues from high, medium, and low priority recommendations.
  • Explain impact in mobile-user terms: security exposure, broken rollout, jank, inaccessible flow, analytics drift, build/runtime failure, or maintainability risk.
  • Include specific remediation guidance. Keep code snippets small unless the user asks for an implementation.
  • If no issues are found, say so clearly and note any meaningful test or verification gaps.

References

  • references/review-guide.md: Migrated detailed review guide from the original mobile-ai-skills agent definition. Read it when you need the full checklist, example report shape, or grep patterns.

Related Assets

react-native-performance-review

active

Review React Native code for performance issues including unnecessary re-renders, inline functions, missing memoization, inefficient lists, context overuse, missing cleanup, and other mobile-specific performance problems. Use when asked to check performance, optimize React Native code, reduce jank, or review performance-critical mobile changes.

codex
react-native
mobile
performance
review
uhc-mobile

Owner: optum-tech-compute

react-native-security-review

active

Review React Native code for security vulnerabilities including PII/PHI storage, authorization bypass risks, secrets handling, token exposure, unvalidated identifiers, unsafe logging, mobile storage risks, and other security-critical mobile issues. Use when asked to check security, sensitive data handling, authentication, authorization, storage, logging, or network-related React Native changes.

codex
react-native
mobile
security
hipaa
review
+1

Owner: optum-tech-compute

dependency-management-reviewer

active

Review React Native and UHC Mobile dependency additions for maintenance status, React Native compatibility, New Architecture readiness, security vulnerabilities, bundle impact, license and ownership risk, justification, alternatives, and approved federation package usage. Use when package.json, lockfiles, native modules, or third-party package choices change.

codex
react-native
uhc-mobile
dependencies
security
review

Owner: optum-tech-compute

file-structure-auditor

active

Review React Native and UHC Mobile code for file structure, file naming, related-file grouping, folder organization, modal placement, utility extraction, and package boundary standards. Use when asked to audit directories, organize components, review screen/package layout, or clean up UHC Mobile file structure.

codex
react-native
uhc-mobile
file-structure
review
maintainability

Owner: optum-tech-compute

uhc-analytics-reviewer

active

Review UHC Mobile analytics implementations for .analytics.ts isolation, track-prefixed functions, Adobe payload casing, analytics constants, screenNameMapEntries updates, route mapping, A/B test tracking, event placement, and federated analytics events. Use when adding or changing mobile analytics, tracking hooks, navigation tracking, or Adobe payloads.

codex
uhc-mobile
analytics
adobe
react-native
review

Owner: optum-tech-compute

uhc-code-organization-auditor

active

Audit UHC Mobile code organization, naming conventions, file structure, import/export patterns, component section ordering, selector and analytics naming, feature-flag naming, and module boundaries before feature merges or cleanup work. Use when reviewing UHC Mobile React Native packages for maintainability and repository convention drift.

codex
uhc-mobile
react-native
code-organization
review
maintainability

Owner: optum-tech-compute