Open Bug 1949218 Opened 3 days ago Updated 3 days ago

aria-description does not auto-translate on iframe

Categories

(Firefox :: Translations, defect)

Product:
Firefox
Component:
Translations
Version:
Firefox 135
Type:
defect

Tracking

()

Project Flags:
Accessibility Severity s3

People

(Reporter: aroselli, Unassigned)

References

(Depends on 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:135.0) Gecko/20100101 Firefox/135.0

Steps to reproduce:

  1. Use a non-Dutch version of the OS and browser (I use English)
  2. Visit: https://adrianroselli.com/demos/aria-description-dutch/
  3. Inspect the rendered HTML and accTree to find all cases of aria-description
  4. Use Firefox to auto-translate the page into your language
  5. Inspect the rendered HTML for the iframe with aria-description
  6. Observe it has not translated.

Actual results:

The aria-description on the <iframe> did not auto-translate. Specifically this code:

<iframe
  title="Hoe te voldoen aan Niet-tekstuele content"
  aria-description="Engelstalige inhoud">
</iframe>

Expected results:

The aria-description on the <iframe> should have auto-translated, just as the aria-description on the link and button did.

For additional context:

  • I used the W3C Dutch translation to get that text, so it's not generated from auto-translation services.
  • The embedded iframe in the dialog probably won't load, which has no bearing on this demo.
Summary: aria-description does not auto-translate → aria-description does not auto-translate on iframe

The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Disability Access APIs
Product: Firefox → Core

Triaging as an S2 because I don't think there's a workaround here

Severity: -- → S2
Severity: S2 → --
Accessibility Severity: --- → s2
Component: Disability Access APIs → Translations
Product: Core → Firefox

I just want to chime in with a bit more context here.

We currently don't translate any <iframe> content at all (Bug 1845783).

Once Bug 1845783 is implemented, we should get this for free.

See Also: → 1845783
Status: UNCONFIRMED → NEW
Ever confirmed: true

Given we don't translate iframes yet, should we still consider this an S2 for accessibility?

Depends on: 1845783
Flags: needinfo?(jteh)

Ah. I wasn't aware we didn't translate iframes yet.

Do we translate the title attribute on <iframe> elements? If not, we shouldn't consider this an s2 currently, but it should become an s2 should we ever ship translation of iframes and this not be supported.

Flags: needinfo?(jteh)

No, we currently don't translate the title attribute either.

Severity: -- → S3
Accessibility Severity: s2 → s3

Given that the the the title and aria-description are part of the parent page (and help the user understand what the embedded page contains), it stands to reason they should be handled as any other content on the parent page.

Is there a reason to create an exception?

Would that exception apply to containers for other embedded content?

To be clear, comment 4 through comment 6 are about whether this should be considered a high severity accessibility issue. The conclusion was that it shouldn't be because attributes on iframes aren't translated for anyone at all; i.e. this isn't an accessibility specific failure. We still consider this a bug, which is why it remains open and has an s3 severity rating. It just isn't an s2 accessibility bug.

Gotcha.

You need to log in before you can comment on or make changes to this bug.