#108914Mark English-only table content with appropriate language attribute in TYPO3 backend
Description
Description
Certain table cells in the TYPO3 backend contain English-only content, but this content is not marked with the appropriate language attribute. As a result, assistive technologies (e.g. screen readers) may pronounce the content using the wrong language rules, and browser features such as spell-check or translation may not behave correctly. To improve accessibility and compliance with WCAG language requirements, English content must be explicitly marked as English.
Reproduction steps
1. Log into the TYPO3 backend.
2. Navigate to the view where the affected table is rendered (e.g. a module or list view containing English-only labels or values).
3. Inspect the table cells (`
4. Check the rendered HTML and verify that these elements do not have a `lang=“en”` attribute (and no other appropriate language annotation).
5. Use a screen reader or browser language tools and observe that the English content is treated as if it were in the default (non-English) language.
Target group
- Screen reader users relying on correct pronunciation and language switching.
- Users who depend on browser spell-check, translation, or reading assistance tools.
- Editors and administrators who frequently work with mixed-language content in the backend.
Severity
Medium
Core functionality remains available, but accessibility and usability for assistive technology users are negatively impacted, and WCAG language requirements are not fully met.
Frequency
Medium to High
The affected English-only table cells appear on recurring backend views and will be encountered regularly by users, especially in multilingual or international setups.
Definition of Done
- All table cells (`
- The implementation does not add `lang=“en”` to cells containing mixed-language or non-English content.
- The default document language (e.g. `lang=“de”`) remains unchanged and intact at the root/parent level.
- Screen reader tests confirm that the English content is announced with English pronunciation where `lang=“en”` is applied.
- No layout, styling, or functional regressions occur in the affected tables.
- The change is covered by at least a basic template/markup test or manual QA note (including example HTML snippet before/after).
Suggestion
- Since the affected data cells are consistently and completely in English, add `lang=“en”` directly to the `
- Centralize the language attribute logic in the template or view helper that renders the table rows to avoid duplication.
- Document in the code comments or developer documentation why `lang=“en”` is applied, so future maintainers keep the language annotation intact.
Recommended solution
- Identify the template, partial, or view helper responsible for rendering the table rows and `
- Adjust the markup so that the affected `
References / WCAG 2.2 Reference
WCAG 2.2 – Success Criterion 3.1.2: Language of Parts
WCAG 2.2 – Success Criterion 3.1.1: Language of Page
Reviews 2
Files 1
History 610
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-02-09T18:33:58+00:00" > 02/09/26, 18:33 </span> -
Garvin Hicking changed target version <span data-processor="relativetime" data-value="2026-02-09T19:42:34+00:00" > 02/09/26, 19:42 </span>
-
Jennifer Geiß commented and changed attached log_table_english.png <span data-processor="relativetime" data-value="2026-02-10T08:34:57+00:00" > 02/10/26, 08:34 </span>
This concerns the backend module ‘Log’. To my knowledge, the ‘Details’ column is always filled in English. This should be indicated as English in the html.
I hope this explanation is usefull.
Best regards
-
Gerrit Code Review pushed patch set 1 for main to change 92778 status
Needs FeedbackUnder Review <span data-processor="relativetime" data-value="2026-02-10T16:16:38+00:00" > 02/10/26, 16:16 </span> -
Gerrit Code Review pushed patch set 2 for main to change 92778 <span data-processor="relativetime" data-value="2026-02-10T16:26:23+00:00" > 02/10/26, 16:26 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 92783 <span data-processor="relativetime" data-value="2026-02-10T18:29:55+00:00" > 02/10/26, 18:29 </span>
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 92783 <span data-processor="relativetime" data-value="2026-02-10T18:33:30+00:00" > 02/10/26, 18:33 </span>
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-02-10T18:34:53+00:00" > 02/10/26, 18:34 </span>
@jgeiss Thanks for this specfication. Of course that’s MUCH MORE doable than what I was panicking about.
Well, that was a scare. :D
Regards,
Garvin -
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-02-10T18:35:08+00:00" > 02/10/26, 18:35 </span>Applied in changeset commit:25864b75b27031d69518f0af1cbcb686af3fb72a.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T08:10:57+00:00" > 03/31/26, 08:10 </span>
Could you explicitly mention an example for this?
English is used as a fallback if either a translation is missing or does intentionally not exist.
Translations are also subject to voluntary work of translators, and may not be up to date.
The way how TYPO3’s translation system is built is that it only returns the contents for a translatable label, after fallback was applied.
The inserted/returned string the does not know about its metadata or language, so we cannot know in a template what language was used for each label, which one was returned english and which one in german.
Changing the current way how translations are handled would be a massive breaking change, or a new opt in method that would take a long time until adopted (if at all).
My personal feeling is that changing this is not feasible. I’d love to hear other thoughts or possible solutions.
Just like with our system resource API we would need to replace all string-based translations with object based ones, so that metadata can be transported alongside the string. I think this would be one of the biggest changes in TYPO3 API that we’ve had so far because it would affect every fluid template, partial and PHP translation output.
So long story short – I fully understand the wish for this and it would be nice to have this, but I’m a bit panicky what this would mean :-)