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

GitHub links fail accessibility guidelines because they rely on colour #2125

Closed
andrewhick opened this issue Jun 9, 2022 · 1 comment
Closed
Labels
Stale Automatically marked as stale.

Comments

@andrewhick
Copy link

andrewhick commented Jun 9, 2022

Issue

The default link format on GitHub appears to fail Web Content Accessibility Guideline (WCAG) criterion 1.4.1 Use of Colour (level A). This is because without hovering, the only way of identifying these links is by being able to distinguish blue and dark grey text. This is therefore likely to make it harder for people with low colour vision to identify links.

To Reproduce

  1. Go to a standard GitHub README or wiki page, such as https://github.com/github
  2. Check the formatting of any links
  3. Using Chrome dev tools, the link colour appears to be: --colour-accent-fg: #0969da
  4. The surrounding text colour appears to be: --color-fg-default: #24292f
  5. Using colour contrast analyser, the contrast ratio between these 2 colours is around 2.8:1.

Expected behaviour

To meet WCAG level A, links should have a way other than colour (hue) to help identify them, such as underlining them. Alternatively, the contrast ratio between the colours of the links and surrounding text should be at least 3:1 to meet the standard required by WCAG.

Desktop

  • OS: Windows 10 Pro
  • Browser: Chrome
  • Version: 102.0.5005.63
  • Default display settings

Additional context

We are using the GitHub wiki to publish Government Digital Service guidance on accessibility but would like the platform itself to meet the standards we refer to.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 6, 2022

Hi! This issue has been marked as stale because it has been open with no activity for 180 days. You can comment on the issue or remove the stale label to keep it open. If you do nothing, this issue will be closed in 7 days.

@github-actions github-actions bot added the Stale Automatically marked as stale. label Dec 6, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale Automatically marked as stale.
Projects
None yet
Development

No branches or pull requests

1 participant