A11y Audit for Full-Page ARIA Attribute Translations
Categories
(Firefox :: Translations, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox139 | --- | fixed |
People
(Reporter: nordzilla, Assigned: isaacbriandt10, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(1 external file)
Description
At your earliest convenience, I would love for the A11y team to just do a quick audit of the translatable ARIA attributes that we handle in Full Page Translations.
In particular I would like to know:
- Are there any that we're missing that we should be translating.
- Are there any that we are currently translating that would be better if we left alone.
Thank you!
How do we test this?
No specific testing is necessary. I just want reassurance from a11y experts that we're doing the correct things.
When will this ship?
This is already in production. But that doesn't mean we can't make improvements if this review determines that any are warranted! :)
| Reporter | ||
Updated•1 year ago
|
Apologies for the delay in replying to you!
Per ARIA spec, the following attributes are expected to be translated when a page is localized:
- aria-braillelabel - keep
- aria-brailleroledescription - keep but fix the typo in the code
- aria-colindextext - add
- aria-description - keep
- aria-label - keep
- aria-placeholder - keep
- aria-roledescription - keep
- aria-rowindextext - add
- aria-valuetext - keep
- abbr on
<th>elements - alt - keep with the following additions/edits:
- we'd need to add the
<image>tag to the<img>tag too - add
<area> - I think we could remove the limit for
imagetype<input>elements only, and keep general<input>tag without conditions (per the translatable HTML spec)
- we'd need to add the
- content on
<meta>tags, per spec: "if thenameattribute specifies a metadata name whose value is known to be translatable" - add - download on
<a>and<area>- add - label - keep with the following additions:
- we'd need to add the
<optgroup>and<option>tag to the<track>tag too
- we'd need to add the
- lang on any tag, per spec: "must be "translated" to match the language used in the translation" - add
- placeholder - keep with the following additions/edits:
- we'd need to add the
<input>and<textarea>tags so we avoid checking all other tags for it, esp. when poor markup is provided by the website autors
- we'd need to add the
- srcdocs on
<iframe>, per spec: "must be parsed and recursively processed" - add - style on any tag, per spec: "must be parsed and recursively processed (e.g. for the values of 'content' properties)" - add
- value on <input> - keep:
- interestingly, per spec, only
type=buttonandtype=resetare included in the translatable properties. Submit seems to be a valid example of something that may be translated too, but the HTML WHATWG does not mention it...
- interestingly, per spec, only
I am not sure, if accessKey is localizeable, in general? The available keyboard may be different, i.e. for someone using Cyrillic or Japanese alphabets... I'd follow the L18n team guidance on this one
XUL tags - do we target those too? AFAIK they're only used in Fx chrome UI, so LMK if you'd need input for those too.
| Reporter | ||
Comment 2•1 year ago
|
||
In its current state, this will make an excellent Good First Bug for someone to try.
The location of the code changes is mentioned in the top-level description, and the instructions/analysis from Anna are extremely well laid out and clear.
Comment 3•1 year ago
|
||
I would like to give this a shot
| Reporter | ||
Comment 4•1 year ago
|
||
Please give it a try.
Feel free to reach out here, in the Matrix channel, or by submitting a work-in-progress patch via moz-phab submit --wip if you want early feedback on some code changes.
Comment 5•1 year ago
|
||
@nordzilla, I wanted to know if contributions has started for this bug, or should I pick up another bug with good first bug tag
| Assignee | ||
Comment 6•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 8•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Description
•