Page Comparison

...

We will add mobile components and styles to the Low Fi figma library as we go.
Whoever is working in hifi will identify component to add to the common library and publish them.
We are not careful about what is published in this common library since only one team depends on it. There is no requirement to review patterns at the Paragon Working Group meeting.
The mobile library will have its own type styles, but will inherit colors from the web Paragon library
We’ll maintain a Figma library “Supplemental Mobile Components”, named specifically to indicate our preference for native controls.

Mobile App Accessibility

...

Support platform accessibility tools
- Screen readers (VoiceOver on iOS and iPadOS, TalkBack on Android)
- OS Magnifier
- External keyboards
- Voice Input
Touchzones - anything clickable should be a minimum of 24px wide and 24px tall (white space counts, and can overlap for different targets)
Minimum font sizes - Don’t go smaller than 10pt, we have x-small at 11pt right now
Interactive items: text should be able to grow by 50% (via text size settings in the OS) without colliding with container borders. Non-interactive items: heading and paragraph text should be able to grow by 200% with orderly reflow.
Don’t make the user rotate the screen.
Headings should be marked as such, and the apps should maintain a consistent visual hierarchy
Don’t use hover behaviors on mobile since they don’t exist! Use tap instead.
[Link to any decks that have these guidelines]

...

Understanding accessibility for iOS
– Apple’s guidance on making iOS apps accessible

When the design is almost final/final, check with Jeff Witt (Deactivated) either via a quick meeting or asynchronously via Slack/email
- This should generally line up with when the design is getting reviewed with the PM partner
Continue to reinforce accessibility check during development process as well before launch

...