Modal dialogs versus inline panels for table editing accessibility in Confluence

Direct answer

Use an inline editing panel as the primary pattern for Confluence table editing, not a modal dialog, provided every panel control is keyboard-reachable and focus returns to the originating table cell when the panel closes. A modal is a secondary fallback only when reliable inline focus management cannot be implemented, because context switching increases disorientation risk for screen-reader users even when role='dialog' and aria-modal='true' are present.

Confirmed facts versus likely explanation

Confirmed: WCAG 2.1 AA requires keyboard operability for all functions, visible focus, and predictable announcements for dynamic changes.

Confirmed: Inline panels preserve visual context but can hide focus state or produce ambiguous announcements during cell selection if live regions are missing.

Confirmed: Modal dialogs give consistent landmark announcements when focus is trapped and restored, yet escape handling and focus return are common failure points.

Likely explanation: Confluence's native table controls depend on mouse interaction, so the barrier is operability and focus management rather than panel placement.

Steps for this case

1. Confirm the Confluence Server/Data Center version; versions before 8.5 are assumed to lack native table-editing keyboard shortcuts and may require custom plugin work.
2. Make every inline panel control reachable with Tab and Shift+Tab, and activate row or column actions with Enter or Space.
3. Apply visible focus indicators to all interactive elements.
4. Announce panel open, panel close, and row or column changes through a polite live region.
5. Restore focus to the table cell that had focus before the panel opened.
6. Verify with keyboard alone, then with NVDA, JAWS, or VoiceOver, and scan with axe-core or WAVE.

Missing diagnostic detail

Which Confluence Server/Data Center version and build are you running? This determines whether native keyboard shortcuts exist or custom development is required.

Assumption: native table shortcuts are unavailable before Confluence 8.5. Treat this as requiring verification against your release notes before implementation.