Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mishmanners
Copy link

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Add accessibility features based on: https://github.blog/2023-10-26-5-tips-for-making-your-github-profile-page-accessible/

Additional Changes

  • This PR modifies the API contract
  • This PR modifies the database schema
  • This PR modifies application configuration/environment variables

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

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible
  • I added a CHANGELOG entry if applicable

@mishmanners mishmanners requested a review from a team as a code owner October 30, 2023 00:43
@github-actions github-actions bot added the S-conventions-not-followed Status: This PR does not follow contributing guidelines label Oct 30, 2023
Copy link
Member

@SanchithHegde SanchithHegde left a 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! -->
Copy link
Member

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?

Copy link
Author

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.

Copy link
Member

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?

@SanchithHegde SanchithHegde added C-doc Category: Documentation updates S-waiting-on-author Status: This PR is incomplete or needs to address review comments labels Oct 30, 2023
@SanchithHegde SanchithHegde changed the title Accessibility features for README.md docs(README): improve the accessibility of README Nov 5, 2023
@github-actions github-actions bot removed the S-conventions-not-followed Status: This PR does not follow contributing guidelines label Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-doc Category: Documentation updates S-waiting-on-author Status: This PR is incomplete or needs to address review comments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants