-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Page - Editor - Cloud
-
Severity 3 - Minor
-
Accessibility
Issue Summary
The row/column insert controls do not meet the minimum target size of 24×24 CSS pixels.
Steps to Reproduce
- Open the Confluence Cloud home page.
- Create a new page or edit an existing page, then insert a table and set it to 6 × 2.
- Observe the table that is created and fill the cells with sample data so the grid looks like a realistic table.
- Move the pointer to the top edge of the table between two columns to reveal the “insert column” handle (tiny dot that shows a “+” icon).
- Move the pointer to the left edge of the table between two rows to reveal the “insert row” handle (tiny dot that shows a “+” icon).
- Observe that both of these controls are very small and difficult to target precisely with a pointer.
- Inspect these elements in the browser dev tools and verify that the pointer target size for these controls is less than 24 × 24 CSS pixels.
Screenshot
Actual Results
The target size of the “Insert column” and “Insert row” controls used to add columns and rows in tables is 16 × 16 CSS pixels, which is below the specified minimum requirement of 24 × 24 CSS pixels. Because these controls are undersized and do not provide sufficient adjacent spacing, they are harder to activate accurately.
As a result, users with dexterity limitations or other mobility impairments may find it difficult to interact with these small targets using a mouse or other pointing device.
Expected Results
Interactive elements on a Confluence page, such as the “insert column” and “insert row” controls in tables, should have sufficient size and spacing for users to interact with them comfortably. It prevents accidental activations and improves the accuracy of interactions, particularly on small touchscreens for users with motor disabilities and users with limited dexterity.
In this case, the controls should be updated so that each input target either meets the minimum size requirement or has sufficient clear spacing around it to support accurate and reliable activation.
Apply the following changes ->
- Specify input targets with a minimum size of 24 by 24 CSS pixels. As a best practice provide the size of 44 by 44 CSS pixels.
Code Snippet:
button{
display: inline-flex;
min-height: 24px;
min-width: 24px
}
Note: This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.
For more information, please refer : https://www.w3.org/WAI/WCAG22/Techniques/css/C42.html
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
Environment
MacBook Pro (16 inch, 2021)
macOs 26.3 (25D125)
Windows - 11 pro
Chrome - Version 145.0.7632.76 (Official Build) (arm64)
Safari - Version 26.2 (21623.1.14.11.9)
JAWS - Version 2025
NVDA - Version 2024.4.2.35031
Voiceover - Version Latest
