1945173 - [a11y] Touch target suggestion for the website URL in reader view mode

Status: NEW

(Firefox for Android :: WebExtensions, enhancement)

Description

[Delia Pop (Android QA)]

Attachment: 2af46d81-5449-454e-882d-ae21004b6630.jpg

Preconditions

Have Google Accessibility Scanner installed.

Steps to reproduce

1. Navigate to any Wikipedia article, and enable reader view.
2. Using the Accessibility Scanner, scan the article in reader view mode.

Expected behavior

No suggestions are made.

Actual behavior

The website URL is flagged: This item's height is 22/32dp. Consider making the height of this touch target 48dp or larger.

Device information

• Firefox version: Nightly 136.0a1, Beta 135.0b9 and Release 135.0 build 2
• Android device model/Android OS version: Samsung Galaxy A53 5G (Android 14)

Comment 1

[Rebeca Tudor]

The touch target issue for url is not detected only in reader mode but in normal mode as well.

Comment 2

[Anna Yeddi [:ayeddi] (Leave starting on July 3, 2026)]

It's expected that interactive target areas are to be 48dp or larger to allow users with limited dexterity and users on the go to better target and tap controls (per WCAG 2.2 Level AAA Success Criteria 2.5.5 and 2.5.8 Target Size (Enhanced and Minimum)). More details could be found in BBC Accessibility guide

That's being said, I agree that this is an enhancement, because the URL is an inline control that is limited by the line height, but its length also enlarges the total area that can be tapped by being long, so marking it as access-S4

Comment 3

[Delia Pop (Android QA)]

@Rebeca, indeed, the touch target for the URL in the address bar is flagged by the accessibility scanner in most instances: normal browsing, reader mode, pdfs, custom tabs.
Should we keep a single ticket for this issue, or file separate tickets for each screen?

Comment 4

[Rebeca Tudor]

(In reply to Delia Pop (Android QA) from comment #3)

@Rebeca, indeed, the touch target for the URL in the address bar is flagged by the accessibility scanner in most instances: normal browsing, reader mode, pdfs, custom tabs.
Should we keep a single ticket for this issue, or file separate tickets for each screen?

I think this ticket should be enough but it's helpful to have the instances where URL is displayed. Thank you Delia!

Informative note: In custom tabs, in the address bar we are displaying both the url and the title so changes to url can create differences in UI.

Comment 5

[Mira Lobontiu (Android QA)]

This suggestion is no longer reproducible on the latest Firefox for Android Nightly 149.0a1 from 1/14, nor on Beta 148.0b2, using a Samsung Galaxy S22 Ultra (Android 16).
Still reproducible on 146.0.1, and 147.0 Firefox for Android builds, with the same device.