Fixing Display Zoom on Android

[kellylein]

Project Status Overview

Project Objective:

On Android devices, there are settings for both font size and display size. The font size setting works as expected (when we prevent fonts from scaling, those fonts are unaffected by the font size setting). However, the display size setting scales everything on the screen, including fonts which shouldn't scale, like in the header.

This issue is isolated to Android devices specifically and can result in word breaks that have the potential to cause accessibility issues due to broken words, dates, etc.

Current Dependencies / Blockers

Blockers

|Blocker | Team / Owner | Est to Resolution | |-------|---------|-------| | Project not prioritized | PO | TBD | | | | | | |

Project Timeline

Milestones

|Step | Timing | |-------| ---------| |Sprint 0 - Discovery | | |Step 1 - Strategy | | |Step 2 - Design | | |Step 3 - Building / Implementing | | | 100% Release | | |Step 4 - Post Verification| |

Monthly Update

Updates

|Month| Project Health | Progress & Key Accomplishments| Issues/Risks/Blockers| |-------| ---------|--------|---------| |Sep '23| Epic created and updated; project in discussion for Q4 prioritized | Work not prioritized | |Oct '23|

Detailed Project Scope

Problem Statement

On Android devices, there are settings for both font size and display size. The font size setting works as expected (when we prevent fonts from scaling, those fonts are unaffected by the font size setting). However, the display size setting scales everything on the screen, including fonts which shouldn't scale, like in the header.

This issue is isolated to Android devices specifically and can result in word breaks that have the potential to cause accessibility issues due to broken words, dates, etc.

Assumptions

Risks

• Additional updates / expanded features by Android developers that may alter the way that display zoom currently functions could pose challenges if altered in the future.
  • To help circumvent this issue, we could continue to research potential changes made to Material Design so that these challenges are anticipated prior to implementation into the Android OS.

Definition of Done

Following needs to be true

|Item | Completed | |-------| ---------| | | | | | |

Project Scope

Items in and out of scope

|In Scope | Out of Scope| |-------| ---------| | | | | | |

Important Project Links

Links

- [Github ticket #4936](https://app.zenhub.com/workspaces/va-mobile-frontend-60f1a34998bc75000f2a489f/issues/gh/department-of-veterans-affairs/va-mobile-app/4936) - [Slack thread pertaining to this issue](https://adhoc.slack.com/archives/C0212B872MT/p1678123871103429) - [How iOS display zoom issues manifest](https://app.zenhub.com/workspaces/va-mobile-qa-638781293f91d46e66b4a935/issues/gh/department-of-veterans-affairs/va-mobile-app/5106) (different than how it impacts Android) - [Github](url) - [Product Brief](url) - [Product Canvas](url) - [Sprint 0](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-mobile-app/features/Display%20Zoom%20on%20Android/displayZoomOnAndroid.md) - Design - [Discovery](url) - [Mockups](url) - [Final Design](url) - [Figma File](url) - Research - [Document 1](url) - [Document 2 ](url) -Analytics - [Document 1](url)

Team Members

Contact List

- **OCTO Product Leads:** Rachel Han and Ryan Thurlwell - **Ad Hoc PM:** - **Engineering:** - **Design:** - **External Team 1 & Role:** - **External Team 1 & Role:**

Questions

Open Questions

- How are other apps handling this issue when display zoom is at the maximum setting? - Are there any ways to override display zoom? - Is there any information within [Material Design](https://m3.material.io/) or in conversations amongst developers about this issue?

OKR and Analytic Metrics

Metrics

|What we are measuring | Why | Event Name |-------| ---------| ----- | | | | | | | | |

Checklist

Toggle Product Checklist

**Project Kickoff & Requirements Gathering** - [ ] Project Kickoff session - [ ] Initiative Scope finalized - [ ] Link Product Brief - [Sprint 0 ](https://docs.google.com/document/d/1WHDJ1iCt9J-acLx8_DSL4tkRKoVYqJGaRUqXuFf7ceg/edit# ) - [ ] Link to Implementation Strategy - Implementation Plan - UAT Plan - Release Plan - Metrics Identified (what metrics are we capturing, how do they tie into stakeholder OKRs, etc) **Pre-Production Readiness** - [ ] Associate Readiness - [ ] Update product guide - [ ] Coordinate with contact center support teams - [ ] What’s New Content - [ ] App Store/In App messaging (if applicable) - [ ] Coordinate with Release coordinator - [ ] App store Content changes required? Y/N - [ ] App store images needed? Y/N - [ ] QA Signed off - [ ] UAT complete - [ ] Obtain Go/No Go decision **Feature Go Live** - [ ] Ensure Waygate/Feature toggle release ticket submitted w/engineering & QA - **Template: Turn on Waygate/Turn off feature flag** - [ ] Coordinate with content & release coordinator if what’s new in app is required

Toggle Team Collaboration Checklist

- [ ] Design Intent & Feasibility discussions - [X] Research needed? No - [ ] UAT Needed? Yes/No - [ ] Ticket creation - [ ] Demo feature (mid check, end of development)

Toggle Design/UX Checklist

- [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to product brief - [ ] Add research links to product brief - [ ] Document high-level research/design plans - [ ] Create lo/hi fi wireframes & user flows if applicable - [ ] Add links to Epic & applicable GitHub folders - [ ] Socialize designs - [ ] Sign off received - [ ] Complete Design QA - [ ] Does it require component review? - [ ] Accessibility review needed?

Toggle Content Checklist

- [ ] Review product brief and surface any questions, assumptions & risks - [ ] Participate in project discovery and kickoff activities/ceremonies - [ ] Complete comparative analysis/content research activities for net-new content - [ ] Review current content and determine where app may need to differ and potential improvements to share with web - [ ] Review past VA research and decisions documentation - [ ] Support Research & UX Design in research sessions and synthesis - [ ] Make content recommendations for lo-/hi-fi wireframes in collaboration with UX Design - [ ] Collaborate with Sitewide Content team for alignment, improvements, and sign-off - [ ] Participate in FE hand off - [ ] Complete content QA - [ ] Write copy for What's New In App - [ ] Write copy for app stores' What's New sections. - [ ] Write copy for updated screenshots in app stores

Toggle Engineering Checklist

- [ ] Are UI designs/ specs available/ready? If yes, they should be attached to attach specs. (We are assuming the design specs have been approved) - [ ] Are there any deadlines that need to be met? - [ ] What is the roll out plan? (Do we need a feature toggle? is this going to be available to every user immediately or do we want to roll out to a few users first) - [ ] Does this project require api integration? if yes, what api endpoint are we integrating with and what is the expected response body? - [ ] Do we want to capture analytics for this projects (i.e. update GA, add logs to grafana/datadog etc)?If yes, what metrics would we like to capture?

Toggle QA Checklist

- [ ] Create test plan - **Template: QA Test Plan** - [ ] Identify test data needs - [ ] Gotten & incorporated test plan review - [ ] QA Complete - [ ] Waygate tasks complete - [ ] Added new feature cases to the RC in TestRail - [ ] Added feature cases to appropriate section of active cases in TestRail - [ ] Spun up a (future) UI automation ticket for new feature

[bischoffa]

Bug ticket but solution for this bug is larger than a bug ticket and requires a project / epic for the work to be done

[bischoffa]

Was reviewed for Q4 projects but was not prioritized by POs