Repository navigation
[Feature request] Add a Mobile variant to the Checkpoints component #36
Description
Activity
@julianmka I put up a draft PR for this here if you have time to look it over 🙏🏼
Once we finalize the content in markdown, I'll build it into the Figma library.
@janmaarten-a11y started taking a look and left a few comments. I'll have to finish up later today or this weekend.
@julianmka I didn't see any comments come through yet, but looking forward to your input ❤️
We now have the first version of the Mobile checklist available in the repository as well as primer.style doc site! 🎉
I'll be making a follow-up issue for edits and improvements. This one ended up being about twice as long as the others. I'd like to figure out how to split it up for mobile designers and devs (like the web checklists), and potentially have variants for the full list vs a shorter list of high impact items. This also requires a full rebuild of the Figma component, so it's a heavier lift than just writing a markdown doc.
Reacted by Julian Kittelson-Aldred
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:
titleWhy
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.