Open gokulkrishh opened 1 year ago
This is a general accessibility concern that tremor doesn't seem to have handled. Just to add a bit to the list, the following components have problematic styling for keyboard navigation in either Chrome or Firefox:
(sad cat 😿 indicates problem that makes keyboard interaction near unusable, usually due to removed focus indicator)
@birjj Thanks for sharing your thoughts and inputs. Having a accessible inputs should also be goal a of library imo. Lets wait for Tremor team to reply and see what they have in mind to told this problem.
Thank you for raising this concern! Also congrats to @gokulkrishh for the launch of expense.fyi ☺️
Accessibility is not covered yet as we are still in beta. We are currently incorporating it for the production-ready version that will be released soon.
Thank you for patience and using our library! 🙏
@christopherkindl thanks and glad to know that A11Y support is in roadmap. Looking forward for the production version. Tremor is awesome keep up the good work. 🫡
Yep, a lot of the points noted by @birjj will be addressed in the v2 which is supposed to be released at the end of this month. Thanks for listing these!
WIP:
Focus Styling Status: 🟢🟠🔴
+1 for tab
I saw the base is headlessui tab so you can use e.g. ⬅️➡️ arrow keys to navigate through the tabs
I am using DateRangepicker component in an app, it is focusable but there is no indicator for it like border or outline.
This is issue is request for supporting it, example i used here is DateRangepicker but ideally it should be supported by all focusable inputs, buttons etc,.
How it is now
How it can be