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.

Sign up for GitHub

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

Jump to bottom

[Toolbar design][Accessibility] Accessible name of tabs icon button should match annotations #23518

Open
natastro opened this issue Dec 2, 2024 · 0 comments
Open

[Toolbar design][Accessibility] Accessible name of tabs icon button should match annotations #23518

natastro opened this issue Dec 2, 2024 · 0 comments
Labels
access Relates to a11y features for users, such as Voice Over, Dynamic Type, Constrat, Readability, etc. access-s3 Accessibility issues that should be done after access-s2 are addressed Bug 🐞 This is a bug with existing functionality not behaving as expected

Comments

@natastro
Copy link

natastro commented Dec 2, 2024 •
edited by data-sync-user
Loading

Prerequisites

  • Turn on VoiceOver
  • Turn on treatment-a of the New Toolbar iOS experiment
  • Found on Firefox Beta iOS app 134.0

Steps to reproduce

  1. Open Firefox Beta iOS app
  2. Move VoiceOver focus to the bottom navbar and navigate to the tabs icon button. Observe VoiceOver output

Expected behavior / Actual behavior

The expectation is that the accessible name should follow what's in the accessibility annotations in Figma. At this time, VoiceOver says 'Show tabs, 12, button'

Device & build information

  • Device: iPhone 15, iOS 18.1.1
  • Build version: Firefox Beta 134.0
  • First seen version: First time I've seen this issue

Notes

Attachments:

ScreenRecording_12-02-2024.15-57-21_1.MP4

┆Issue is synchronized with this Jira Task
@natastro natastro added Bug 🐞 This is a bug with existing functionality not behaving as expected access Relates to a11y features for users, such as Voice Over, Dynamic Type, Constrat, Readability, etc. access-s3 Accessibility issues that should be done after access-s2 are addressed labels Dec 2, 2024
@PARAIPAN9 PARAIPAN9 mentioned this issue Dec 3, 2024
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
access Relates to a11y features for users, such as Voice Over, Dynamic Type, Constrat, Readability, etc. access-s3 Accessibility issues that should be done after access-s2 are addressed Bug 🐞 This is a bug with existing functionality not behaving as expected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@natastro