hotfix: fix category badge contrast in BlogPostCard component

[baezor]

Summary

The previous contrast fix (#49) updated .category-badge in the blog index pages but missed BlogPostCard.astro, which is the component used on the homepage. Lighthouse was still flagging the homepage badges at 3.85:1 contrast.

• Changed badge text from var(--color-accent) to var(--color-text) in BlogPostCard.astro
• Added aria-label to read-more links in the same component

Test plan

• npm run build passes
• 40/40 visual regression tests pass
• CI checks pass
• Lighthouse color-contrast audit passes on homepage

[cloudflare-workers-and-pages]

Deploying baezor with    Cloudflare Pages

Latest commit:	dcddc32
Status:	✅  Deploy successful!
Preview URL:	https://d701f994.baezor.pages.dev
Branch Preview URL:	https://hotfix-fix-blogpostcard-badg.baezor.pages.dev

View logs

[claude]

Code Review

Summary

This hotfix correctly addresses the missed contrast fix in BlogPostCard.astro and adds an aria-label to read-more links. Both changes are good improvements. However, there are a few issues worth addressing.

---

Issues

1. Incomplete aria-label fix — other listing pages are missing it

The aria-label was added to BlogPostCard.astro, but the same generic read-more link (without aria-label) still exists in several inline listing pages. The blog.readMore.aria key already exists in src/i18n/ui.ts, so these should be updated for consistency:

• src/pages/tag/[tag].astro
• src/pages/category/[category].astro
• src/pages/es/tag/[tag].astro
• src/pages/es/category/[category].astro

2. Verify category badge contrast in remaining pages

The badge contrast fix has now been applied to blog/index.astro (PR #49), es/blog/index.astro (PR #49), and BlogPostCard.astro (this PR). But .category-badge is also defined in:

• src/pages/tag/[tag].astro
• src/pages/category/[category].astro
• src/pages/es/tag/[tag].astro
• src/pages/es/category/[category].astro
• src/layouts/BlogPost.astro

Please verify these files also use color: var(--color-text) and not var(--color-accent) for the badge text color, otherwise those pages will have the same 3.85:1 contrast issue.

3. Branching strategy mismatch

Per CLAUDE.md, hotfix/* branches should branch from main for urgent production fixes and merge back to both main and develop. This PR branches from develop and targets develop only.

Since this is a missed fix from PR #49 (not an urgent production-only issue), using fix: as the commit type and a fix/ branch prefix would be more appropriate. If it truly needs to go straight to production, the full hotfix GitFlow workflow should be followed.

---

Positive

• The contrast change from var(--color-accent) to var(--color-text) is correct — #b5532f on the tinted background fails at 3.85:1; var(--color-text) resolves it cleanly.
• The aria-label approach reuses the existing blog.readMore.aria translation key rather than hardcoding strings, consistent with the i18n pattern used in blog/index.astro.
• Visual regression tests all pass (40/40) per the test plan.

---

Verdict: Request changes — The contrast fix is correct and the PR is on the right track, but the aria-label accessibility fix and badge contrast fix should be applied consistently across all listing pages before merging.