-
-
Notifications
You must be signed in to change notification settings - Fork 747
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
[FEATURE] Accessibility Improvement of website #3407
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
@akshatnema I want to work on this issue. Could you please assign me this? |
@aakankshabhende are you still on it? if not I can take from here |
@TenzDelek Yes, I'm working on it. |
I'm working on this issue but currently, this issue is waiting on the design team @akshatnema |
@aakankshabhende can you please elaborate your approach |
if this issue open can i work on this |
Thanks for bringing this up and offering to work on it. Sorry for the delay in responding; I’ve been away for a bit. I agree that the website could use some accessibility improvements, and that’s part of why I’ve been working on redesigning some sections. You can check out more details here. I tried looking for the designs in the design channel, but I couldn’t find them. Would you mind dropping the link to the Figma file here? Thanks so much! I'm looking forward to reviewing your designs. |
Why do we need this improvement?
Currently, the website accessibility score is 93. By improving the colour contrast ratio and styling, we can achieve a 100 score.
How will this change help?
We need to be highly accessible for a better user experience.
Screenshots
How could it be implemented/designed?
Relates to #3186
🚧 Breaking changes
No
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: