Skip to content

Improve agent profile contrast and page metadata - #295

Merged
Exzentttt merged 1 commit into
mainfrom
fix/profile-accessibility
Nov 2, 2026
Merged

Exzentttt merged 1 commit into
mainfrom
fix/profile-accessibility

Conversation

@Exzentttt

@Exzentttt Exzentttt commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

Public agent profiles inherited the leaderboard page title, and their breadcrumbs and empty-biography text were difficult to read on the dark background. This change raises those three text treatments to the existing neutral-400 color and gives profiles their own localized title, description, canonical URL and language alternates. The leaderboard title stays unchanged.

The production audit measured the former text contrast at approximately 2.53:1. In the local standalone build, the changed text measured at least 7.53:1 across 18 computed-foreground and adjacent screenshot-background samples, covering English and Russian at 1440, 768 and 390 CSS pixels. Existing layout, collapsed technical details and unrelated copy are preserved.

Validation:

  • 50 focused locale/dictionary tests passed; full frontend suite: 1,016 tests across 84 files passed.
  • TypeScript, scoped ESLint, production build and diff checks passed.
  • Six isolated Chromium scenarios against the local standalone build passed: localized profile titles, no horizontal overflow, breadcrumb keyboard focus and keyboard activation of technical details. Genuine screenshots and recordings were captured; recording contact sheets were reviewed at 2 fps.
  • Independent source and UI delta reviews reported no findings.

Public evidence is available in the pinned v4.3.0-rc.1 candidate. All 12 asset downloads returned HTTP 200 without authentication and matched their uploaded sizes and SHA256 digests.

These final fixture captures show a local production-mode build, not production-after installation. The two live-before screenshots in the bundle use different real data and are illustrative, not a pixel-identical comparison. WebM links are downloads; inline playback is not guaranteed. Frontend rollout remains pending.

Limits: titles identify a public AI agent profile generically; they do not include the agent name. Browser scenarios use synthetic anonymous public API fixtures, with analytics writes blocked. They do not verify production backend behavior, authenticated flows, cross-browser rendering or WCAG conformance. No media files are added to the repository.

@Exzentttt
Exzentttt marked this pull request as ready for review November 2, 2026 13:22
@Exzentttt
Exzentttt merged commit 7093a54 into main Nov 2, 2026
5 checks passed
@Exzentttt

Copy link
Copy Markdown
Member Author

Installed and verified on production on 2026-11-02, 13:40 UTC. Frontend source is the reviewed tree 0b08032f132574d3a5bf152bad5a15ac72c2f23d, merged in 7093a541a4612d7cd90636466bebfd8781044dbc; installed image is sha256:0f4a752c7d9ff19ccd5acb8abd3725ab4fec9bb1290c5d3dbf99ea7b9b8178e0.

One frontend-only switch succeeded. Fresh post-switch verification passed configured-hostname readiness and preserved the other 20 containers, all nine volumes, bindings and semantic network aliases. Backend, worker and Caddy were not replaced.

Six real anonymous Chromium scenarios passed: English and Russian at 1440, 768 and 390 CSS pixels. Localized titles/canonical URLs, corrected breadcrumb styling, no horizontal overflow and keyboard interaction passed; all six live screenshots were visually inspected. These live checks are separate from the earlier synthetic standalone recordings.

All eight new live-after asset downloads returned HTTP 200 without authentication and matched SHA256. Existing candidate assets remain unchanged. Authenticated behavior and complete WCAG conformance are outside this verification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant