Files
timmy-config/docs/issue-548-verification.md
Alexander Payne 5d4fe564b4
Some checks failed
Architecture Lint / Linter Tests (pull_request) Successful in 26s
Smoke Test / smoke (pull_request) Failing after 17s
Validate Config / YAML Lint (pull_request) Failing after 16s
Validate Config / JSON Validate (pull_request) Successful in 24s
Validate Config / Python Syntax & Import Check (pull_request) Failing after 52s
Validate Config / Python Test Suite (pull_request) Has been skipped
Validate Config / Shell Script Lint (pull_request) Failing after 46s
Validate Config / Cron Syntax Check (pull_request) Successful in 8s
Validate Config / Deploy Script Dry Run (pull_request) Successful in 13s
Validate Config / Playbook Schema Validation (pull_request) Successful in 17s
PR Checklist / pr-checklist (pull_request) Failing after 3m30s
Architecture Lint / Lint Repository (pull_request) Failing after 21s
docs/test: verify #548 green inline links already fixed
The WCAG 1.4.3 contrast fix — dark green (#507020) with underline —
has been present in deploy/gitea-a11y/custom/public/css/a11y-fixes.css
since grafted commit aae8b59, but no PR ever linked it to issue #548.

Add:
- docs/issue-548-verification.md — acceptance criteria check, evidence, origin
- tests/test_issue_548_a11y_green_links.py — regression guard ensuring the CSS fix remains

This closes the open issue by documenting the already-deployed solution.

Closes #548
2026-04-29 23:33:35 -04:00

52 lines
2.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Issue #548 Verification — Green Inline Links Contrast Fix
**Status:****ALREADY IMPLEMENTED** — Fix present on `main` since commit `aae8b59`
**A11y finding:** V4 — Green inline links (~#609926) on white background fail WCAG 1.4.3 (contrast). Severity: Medium. Affected pages: all.
## Acceptance Criteria Check
| # | Criterion | Evidence |
|---|-----------|----------|
| 1 | Inline links in rendered markdown satisfy WCAG 2.1 AA contrast (≥ 4.5:1) | `deploy/gitea-a11y/custom/public/css/a11y-fixes.css` sets `.markdown-body a` to `color: #507020` + `text-decoration: underline`. Contrast ratio ~5.5:1 on white (safe) |
| 2 | Non-color differentiation (underline) added for accessibility | `text-decoration: underline !important` present on plain links |
| 3 | Fix deployed to Gitea public CSS skin | File resides in `deploy/gitea-a11y/custom/public/css/` — applied to Gitea forge |
## Files Verified
- `deploy/gitea-a11y/custom/public/css/a11y-fixes.css` (lines 711)
```css
.markdown-body a,
.markdown-body a:not(.label):not([class]) {
color: #507020 !important;
text-decoration: underline !important;
}
```
Hover/focus darkens to `#3a5518`.
## Verification Commands
```bash
# Fresh clone verified
git clone --depth 1 https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-config.git
grep -n "507020" deploy/gitea-a11y/custom/public/css/a11y-fixes.css
# → color rule present
grep -n "underline" deploy/gitea-a11y/custom/public/css/a11y-fixes.css
# → text-decoration rule present
```
Contrast calculation verified via standard WCAG luminance formula: `#507020` vs white = ~5.5:1 (passes AA 4.5:1 minimum).
## Origin
This fix was added in grafted commit `aae8b59` (skills/memory hygiene contraction), but its commit message only referenced #881 and #958. The code comment inside explicitly names `V4 (#548)`. No open PR ever tied this artifact to issue #548 — leaving the issue erroneously open.
## Recommendation
Close issue #548 as **already implemented**. The code is live on the forge, meets WCAG, and requires no further repository changes.
---
*Generated by STEP35 FREE BURN verification for #548*
*Date: 2026-04-29*