[P2] Distinguish inline documentation links without relying only on color
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp, css, html
- Domain
- accessibility, documentation
Research direction
Start with docs/css/style.css:37 and compare the prose links referenced in docs/learn.html:126 and docs/examples.html:6. Check the pages with axe's link-in-text-block rule, then verify links are distinguishable before hover and when keyboard-focused. Done when the axe checks pass and navigation and buttons remain visually coherent.
Written by the indexing model from the issue text.
Description
Audit of main at 33775b35ce39b259cc6a4ea33db6216aba19d702 on 2026-10-08. Priority P2; area: Documentation.
Problem
Inline prose links are distinguished only by a color too similar in luminance to surrounding text. Users with color-vision limitations cannot reliably discover them.
Evidence / reproduction
axe link-in-text-block flags six links on desktop learn.html and one on examples.html. The examples link has 1.21:1 contrast against surrounding text and no underline; required distinction is an additional visual cue or adequate color contrast.
Source: docs/css/style.css:37, docs/learn.html:126, docs/examples.html:6.
Suggested change
Use an underline or another persistent noncolor cue for prose links, with clear hover and keyboard-focus styles.
Acceptance criteria
- axe link-in-text-block checks pass.
- Links are distinguishable before hover and under keyboard focus.
- Navigation/buttons remain visually coherent.
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evilz/TermBlade
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
codex
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Similar issues
-
type/automation type/tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
no-stack-trace
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
v9 review: TestingOpendocs/external squad/utforming
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Altinn/altinn-studio#21041 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stryker-mutator/stryker-net#3892 ·
Maintainers usually reply within 1 day