Confluence Cloud 8.13 Editor: Inline tables missing aria-labels

Question

Goal
Ensure that screen‑reader users can reliably identify the purpose of inline tables in the Confluence Cloud 8.13 editor, and that the Content Tools menu is fully reachable via keyboard.
Constraints & Uncertainty

The editor renders tables as role="grid" elements without an aria-label, making the table’s intent invisible to assistive technology.
Alt+T opens the Content Tools drop‑down, but tabbing does not focus the first submenu item; the menu appears to be hidden from keyboard navigation.
Confluence Server 7.13 implements a different ARIA schema for tables, creating a version‑dependent accessibility gap.
It is unclear whether default labeling should be applied automatically or left to content authors.

Questions

Should Confluence automatically generate descriptive aria-label attributes for all inline tables in both Cloud and Server by default?
What changes are required to make the Content Tools menu fully focusable through keyboard navigation?
How can the editor maintain consistent ARIA behavior across Cloud 8.13 and Server 7.13 while preserving author control?

Tasadduq Burney · Answer

Answer Confluence Cloud 8.13 does not automatically add an aria-label to inline tables, so screen‑reader users cannot reliably identify their purpose. Authors must supply the label manually, and the Content Tools dropdown can be made fully keyboard‑navigable by ensuring the menu component is focusable and that the first submenu item receives focus when the menu opens. Likely explanation The inline table macro in Cloud 8.13 renders a element without an aria-label. The Content Tools dropdown is implemented as a hidden menu that only becomes visible on click; keyboard focus is not programmatically set to the first item, causing the menu to appear unreachable via Tab. Confirmed facts The editor version is 8.13 (Cloud) and uses a role=\"grid\" on tables but omits aria-label. Screen‑reader testing shows tables are announced as “grid” without context. The Content Tools menu opens with Alt+T but the first focusable element is not reached by Tab. Steps to verify and fix Open the page in edit mode and locate the problematic inline table. Switch to Show HTML (⋮⋯ → Show HTML) and confirm the

tag lacks an aria-label attribute. If the label is missing, add a wrapper

around the table or edit the table properties to set a custom label. Save the page and re‑view the source to verify the aria-label now exists. To make the Content Tools menu keyboard‑focusable, ensure the underlying dropdown component is rendered with a tabindex=\"0\" and that the first menu item receives focus on onOpen event; this may require a space‑level configuration change or a support request if the default behavior cannot be altered. Diagnostic needed Please confirm whether the missing aria-label appears on all inline tables or only on tables created after a recent theme or space setting change, as this determines if a global fix or a per‑table adjustment is required. Verification After editing, view the page source and confirm the aria-label attribute is present on the table or its wrapper. Run an accessibility audit (e.g., axe, Lighthouse) to ensure the table is announced correctly and the Content Tools menu is reachable via Tab.

Confluence Cloud 8.13 Editor: Inline tables missing aria-labels

Goal

Constraints & Uncertainty

Questions

1 answer

Answer

Likely explanation

Confirmed facts

Steps to verify and fix

Diagnostic needed

Verification

Your perspective belongs here.

1 question comment