Skip to content

[Feature request] Add a Mobile variant to the Checkpoints component #36

@janmaarten-a11y

Description

@janmaarten-a11y

Description

The toolkit currently includes a checklist component for verifying accessibility considerations, but it is oriented toward desktop experiences. Mobile interfaces have their own set of accessibility concerns, such as touch target sizing, gesture alternatives, screen reader rotor navigation, and orientation support.

Requested change

Add a mobile-specific variant of the checklist component that covers accessibility considerations unique to the mobile context. This could include items such as:

  • Each screen having a maximum of one title
  • Every touch interaction can be also accessed with a keyboard
  • Focus order is annotated and matches the intention of the design. Avoid focus that jumps back and forth across the screen to reach items visually out of order.
  • Touch target minimum sizes (per WCAG 2.2 Success Criterion 2.5.8 Target Size)
  • Availability of gesture alternatives for complex interactions
  • Support for both portrait and landscape orientations
  • Screen reader compatibility for mobile-specific UI patterns (e.g., bottom sheets, swipe actions)
  • Support for platform accessibility features like Dynamic Type / text scaling

Why

Mobile annotation is an increasingly common need as teams design responsive and native mobile experiences. Having a dedicated mobile checklist helps designers verify that accessibility requirements specific to smaller screens and touch interactions are accounted for during the design phase, rather than discovered later in development or testing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIdeas for additions or changes to the main libraryplannedThis issue is on the roadmapset:mobile-annotationsAnnotation components for mobile platforms including iOS and Androidset:utilitiesAnnotation components for Legends, checklists, title cards, labels, flows, and more

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions