You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the upcoming WCAG regulations that will be mandatory for all digital products in the European Union starting in 2025, it is essential for our applications to be keyboard accessible to ensure inclusivity for all users, including those with disabilities. However, the current version of Cropper.js lacks keyboard accessibility features.
Requested feature:
Tabbable Component: Enable tab navigation into the Cropper.js component for keyboard users, ensuring they can access and interact with its functionalities without relying solely on mouse input.
Arrow Key Functionality: Allow users to use arrow keys to navigate and adjust the top, left, bottom, and right boundaries of the cropping area within the Cropper.js component.
Expected outcome:
Improved accessibility for users who rely on keyboard navigation.
Compliance with WCAG regulations and enhanced inclusivity for all users.
Sources of inspiration:
The npm package react-image-crop implemented similar functionality in this PR
For a demo app implementation that meets the WCAG standards you can check this website
Note: I understand the importance of maintaining compatibility and performance while implementing these changes, and I am open to discussing potential implementation strategies or collaborating on this enhancement.
Thank in advance!
The text was updated successfully, but these errors were encountered:
Description:
As per the upcoming WCAG regulations that will be mandatory for all digital products in the European Union starting in 2025, it is essential for our applications to be keyboard accessible to ensure inclusivity for all users, including those with disabilities. However, the current version of Cropper.js lacks keyboard accessibility features.
Requested feature:
Expected outcome:
Sources of inspiration:
Note: I understand the importance of maintaining compatibility and performance while implementing these changes, and I am open to discussing potential implementation strategies or collaborating on this enhancement.
Thank in advance!
The text was updated successfully, but these errors were encountered: