TYPO3 Accessibility Finding to Developer Ticket
TYPO3 accessibility findings often sit between content, templates, extensions, and editorial workflows. This example turns one finding into a ticket that a developer and content owner can both act on.
Use this as practical remediation wording, not as legal advice or a complete audit result.
Typical TYPO3 finding
Finding: Accordion headings on product-support pages are visually styled as section headings, but the clickable trigger is a generic button with no descriptive accessible name. Page type: TYPO3 content page using reusable accordion content element Evidence: Screen reader announces several controls only as “button, collapsed”. Keyboard users can open them, but cannot identify which topic they control.
Developer-ready ticket
# [High] TYPO3 content element: accordion buttons do not expose topic names ## Summary for product / content owner Screen reader users can reach the accordion controls, but the controls are announced without the visible topic text. This makes the support content difficult to navigate and can hide help information behind unnamed buttons. ## Developer ticket **Area / flow:** TYPO3 product-support content page **Component:** Reusable accordion content element / Fluid template **Assistive technology context:** NVDA / VoiceOver **Suggested severity:** High **User impact:** Causes serious confusion or high effort ### Expected behavior Each accordion trigger exposes the visible topic text as its accessible name and announces expanded / collapsed state. ### Actual behavior The controls are announced only as generic buttons. Users hear “button, collapsed” repeatedly without knowing which section each button opens. ### Evidence - Finding source: manual screen reader test - Affected template: reusable TYPO3 accordion content element - Example announcement: “button, collapsed” instead of “Shipping options, button, collapsed” ### Likely WCAG references to verify - 1.3.1 Info and Relationships - 2.4.6 Headings and Labels - 4.1.2 Name, Role, Value ### Acceptance criteria - Each accordion trigger has an accessible name matching the visible topic text. - Expanded / collapsed state is programmatically exposed. - The keyboard focus order stays on the trigger and does not skip newly revealed content. - A new accordion instance added by editors inherits the same accessible markup. ### Fix direction Update the Fluid partial / content element template so the button contains or references the visible heading text. Keep the native button element, expose aria-expanded, and connect the trigger to the controlled panel with stable IDs.
Why this wording helps
- It names the TYPO3 layer likely to need a fix: a reusable Fluid/content-element template.
- It avoids blaming editors for a template-level accessibility bug.
- It includes regression criteria so future editor-created accordions stay accessible.