-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve accessibility #182
Comments
Can you briefly describe the problem? I am ready to fix it |
Hi @harith-hacky03 this is a general task about keyboard accessibility throughout the library. I don't believe we can easily use Bitcoin Connect without a mouse right now for example. Some good information is here: https://usability.yale.edu/web-accessibility/articles/focus-keyboard-operability |
@rolznz You need specificed action to happen when enter is pressed in keyboard right? |
@harith-hacky03 no. This is about accessibility. Maybe you could find a different issue if you would like to contribute. |
Small reminder: there is a bounty for solving this issue! Bitcoin Connect is an embeddable, open-source JavaScript library maintained by Alby that allows websites to easily integrate Bitcoin and Lightning functionalities. It provides a modal widget for user interactions, enabling seamless onboarding and transactions. Currently, the Bitcoin Connect modal widget requires a mouse for navigation and interaction, limiting its accessibility. By improving keyboard accessibility, we aim to make the library more inclusive and user-friendly for all users, including those with disabilities who rely on keyboard navigation. 💰 Bounty: 75,000 sats💰 Alby's team & community support 🔗 Links:
💡 Please Remember:
♿ #ACCESSIBILITY #OPENNESS #DECENTRALIZATION 💙 Thank you for your contributions and making Bitcoin more accessible and user-friendly for everyone! |
I am ready to fix it. Can you assign me please? |
@harith-hacky03 normally I do not assign issues to external contributors because there is no guarantee they will do it. If you are interested, could you make a pull request? |
Hey there, I've made an initial PR (#259) with mostly minor changes which enable both keyboard navigation and screen reader feedback. There's still some testing to be done and a few niggling issues with default buttons, but I'd appreciate if you could give me some feedback if I'm on the right path. |
Base element accessibilty integrations add accessibility options to components Accessibilty changes internal Accessibilty additions to components last (?) changes for Improve accessibility getAlby#182 more aria additions
Tabbing / Keyboard access should work in all places. Some elements (like the button below) should be focused by default.
The text was updated successfully, but these errors were encountered: