Open Bug 2082523 Opened 1 month ago Updated 1 month ago

Localization and accessibility for the QWAC indicator

Categories

(Firefox for Android :: Settings, task)

All
Android
task

Tracking

()

People

(Reporter: lmccracken, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid][android-activation-trust])

Summary
Localize the QWAC statement and add TalkBack support for the EU trust mark

Description
The QWAC statement and EU trust mark added earlier need to work for users in every locale Firefox ships in, and for users who rely on TalkBack. This ticket covers the string setup for localization, the review of the legal wording with L10n, and the accessibility treatment of the logo and statement.

The statement, “Qualified as specified in Regulation (EU) 2024/1183.”, references a specific legal instrument. Whether it should be translated, and whether translators may adapt it, is not obvious. Official EU-language versions of the regulation may use set terminology for “qualified website authentication certificate”, and a loose translation could misstate the legal meaning. This ticket should get a decision on that before the string is exposed to translators, and set the string up accordingly.

The logo needs a content description that tells a TalkBack user what the mark is. It should not simply read the file name or repeat the statement word for word, and it should not be announced twice in a confusing way.

In scope

Moving the statement into strings.xml (ticket 9 should already use a resource; this ticket finalizes it)
Adding a translator comment explaining context, the regulation reference, and what must not change (for example “(EU) 2024/1183” stays as is)
Agreeing with L10n whether the string is localizable normally, localizable with constraints, or kept verbatim, and recording the decision in the ticket
Using a placeholder for the regulation number if L10n prefers it kept out of translated text
Content description for the EU trust mark, in its own localizable string
Deciding whether the logo and statement are exposed to TalkBack as one grouped element or two, to avoid duplicate announcements
Checking behaviour with long translations (German, Finnish and similar), large fonts and RTL languages
Checking that the regulation number and parentheses render correctly in RTL text (bidirectional text)
Unit or UI test that the strings are resolved from resources, not hardcoded

Out of scope

Building the QWAC UI
Hide logic for non-QWAC sites
Localizing the rest of the sub-page’s strings
Pref gating
Focus

Acceptance criteria

The statement is in strings.xml with a translator comment, and L10n has confirmed the approach.
The decision on translation (free, constrained or verbatim) is recorded in the ticket.
The logo has a localizable content description that TalkBack reads sensibly.
TalkBack does not announce the logo and statement redundantly, and the reading order matches the visual order.
The regulation number displays correctly in RTL layouts, with no reversed or misplaced parentheses.
The statement wraps without clipping at large font sizes and with long translations.
No QWAC-related user-visible string is hardcoded.
A test or lint check confirms the strings come from resources.

Whiteboard: [fxdroid][android-activation-trust]
You need to log in before you can comment on or make changes to this bug.