Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cherry-pick: accessibility issue with footer buttons #13717

Merged
merged 4 commits into from
Feb 25, 2025

Conversation

jpuri
Copy link
Contributor

@jpuri jpuri commented Feb 25, 2025

Description

Fix issue with footer buttons not visible in IOS with large fonts.

Related issues

Ref: #13516

Manual testing steps

  1. In IOS device enable large fonts
  2. Go to test dapp and submit signature request
  3. Check if footer buttons are clearly visible

Screenshots/Recordings

LARGE FONTS:
Screenshot 2025-02-20 at 3 31 43 PM

SMALL FONTS:
Screenshot 2025-02-20 at 3 36 47 PM

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@jpuri jpuri added the team-confirmations Push issues to confirmations team label Feb 25, 2025
@jpuri jpuri requested a review from a team as a code owner February 25, 2025 14:50
@jpuri jpuri changed the title fix: accessibility issue with footer buttons cherry-pick: accessibility issue with footer buttons Feb 25, 2025
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@jpuri jpuri force-pushed the confirm_footer_fix branch from ad7f6ed to 43d40a5 Compare February 25, 2025 15:00
Fix issue with footer buttons not visible in IOS with large fonts.

Fixes: #13516

1. In IOS device enable large fonts
2. Go to test dapp and submit signature request
3. Check if footer buttons are clearly visible

LARGE FONTS:
<img width="394" alt="Screenshot 2025-02-20 at 3 31 43 PM"
src="https://github.com/user-attachments/assets/094f7998-885a-4247-80ce-8529ec8c7e1a"
/>

SMALL FONTS:
<img width="399" alt="Screenshot 2025-02-20 at 3 36 47 PM"
src="https://github.com/user-attachments/assets/bc2160e7-e6cd-4778-b463-aee55f16c984"
/>

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [X] I've completed the PR template to the best of my ability
- [X] I’ve included tests if applicable
- [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [X] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Remove scroll button from confirmation page as it is not part of the
designs

Fixes: MetaMask/MetaMask-planning#4277

1. Go to test dapp
2. Open any signature page with scroll
3. Ensure that scroll button does not appear

https://github.com/user-attachments/assets/d6771f31-646e-4110-926e-1bd7cfbf0891

- [X] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [X] I've completed the PR template to the best of my ability
- [X] I’ve included tests if applicable
- [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [X] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@jpuri jpuri force-pushed the confirm_footer_fix branch from 43d40a5 to 993ff66 Compare February 25, 2025 15:11
@jpuri jpuri merged commit e70519d into release/7.41.0 Feb 25, 2025
28 of 29 checks passed
@jpuri jpuri deleted the confirm_footer_fix branch February 25, 2025 15:47
@github-actions github-actions bot locked and limited conversation to collaborators Feb 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
team-confirmations Push issues to confirmations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants