-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
docs(README): improve the accessibility of README #2726
base: main
Are you sure you want to change the base?
Conversation
Add accessibility features based on: https://github.blog/2023-10-26-5-tips-for-making-your-github-profile-page-accessible/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer reverting all the links to reference-style links, as before. Other than that, looks good to me!
@@ -145,16 +139,14 @@ analytics, and operations end-to-end: | |||
- Custom dashboards with deep analytics, alerts, and reporting | |||
- Expert team to consult and improve business metrics | |||
|
|||
You can [try the hosted version in our sandbox][dashboard]. | |||
You can [try the hosted version in our sandbox](). <!-- needs a link here! --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We used reference-style links to avoid duplication of links and make the source content more readable. Regardless, I couldn't find any information on the linked article that discourage the use of reference-style links. Any specific reason for changing all of them to inline links?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason for inline links as when people who use accessibility settings, the audio is read out as it is. Thus the person hearing it can't just stop and "scroll" to the bottom of the page to see where/what it is linking it. Having the link directly attached to where it's referenced helps these people quickly navigate. It's up to you thought 😉 let me know what you'd like to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct me if I'm wrong, but the guidelines on the linked blog post suggests including alt text with links/images so that the rendered markdown is easy to navigate through. Keeping the links inline or in reference-style in markdown source code does not affect the rendered content, so we should be good to use the reference-style links?
What do you think, @VedantKhairnar?
Type of Change
Description
Add accessibility features based on: https://github.blog/2023-10-26-5-tips-for-making-your-github-profile-page-accessible/
Additional Changes
Motivation and Context
Accessibility is important to ensure EVERYONE can use the repo regardless of their own physical or mental circumstances.
How did you test it?
NA
Checklist
cargo +nightly fmt --all
cargo clippy