WCAG 2.5.7: Dragging Movements
WCAG 2.5.7: Dragging Movements (Level AA)
The WCAG 2.1 Success Criterion 2.5.7, „Dragging Movements,” requires that if a user interface component or functionality relies on a dragging movement for its operation, an alternative method must be provided to achieve the same outcome without dragging. This criterion aims to ensure that users who cannot perform precise dragging gestures due to motor impairments or other factors can still interact with the content effectively.
Why This Criterion Matters for Accessibility
Dragging movements, while intuitive for many users with a mouse or touchscreen, can pose significant barriers for others. This criterion addresses a range of accessibility challenges:
By providing non-dragging alternatives, we create a more inclusive and usable experience for a much wider audience, enhancing the overall flexibility and robustness of the user interface.
Understanding Success Criterion 2.5.7 Requirements
The full text of Success Criterion 2.5.7 states:
„Dragging Movements: All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the function is determined by the user agent and not modified by the author.”
Let’s break down the key terms:
Practical Guidelines for Compliance
To comply with WCAG 2.5.7, focus on providing robust and equivalent alternatives:
Examples of Correct and Incorrect Implementations
Scenario: Reordering Items in a List
A common use case for dragging is reordering elements in a list or grid.
Incorrect Implementation (Dragging Only)
This example only allows reordering by dragging, making it inaccessible for many users.
Correct Implementation (Dragging with Alternative Controls)
This example provides visible 'Move Up’ and 'Move Down’ buttons for each item, allowing reordering without dragging. The dragging functionality is still available as an enhancement.
Scenario: Resizing a Window/Panel
When providing resizable panels or windows within a web application.
Incorrect Implementation (Resizing Only by Dragging)
A panel that can only be resized by dragging its border.
Correct Implementation (Resizing with Input Fields)
The panel can be resized by dragging OR by entering specific pixel values into input fields. Both methods are synchronized, and the resize handle is keyboard operable.
Best Practices and Common Pitfalls
Best Practices
Common Pitfalls
Conclusion
Adhering to WCAG 2.5.7 „Dragging Movements” is crucial for creating truly inclusive web experiences. By offering flexible interaction methods that go beyond single-mode dragging, we empower a broader range of users, including those with motor impairments, to fully participate in and benefit from digital content. This criterion not only improves accessibility for specific groups but often enhances usability for all, making interfaces more robust and adaptable to various user preferences and situations.
Related posts
- WCAG 5.2.3: Complete processes
- WCAG 5.2.4: Only Accessibility-Supported Ways of Using Technologies
- WCAG 5.2.5: Non-Interference
- WCAG 5.3.1: Required elements of the conformity declaration
- WCAG 5.3.2: Optional Components of a Conformance Claim
Still looking for answers?
Ask our experts using online chat