[AXE] Announcement bar fails accessibility on every page

Open
#145 0 comments 0 reactions 2 assignees View on GitHub

Maintainers usually reply within 7 days

@matej-marcisovsky is already working on this.

Since Oct 16, 2026.

Assessment

This issue has not been assessed yet.

Description

bug

Where: every page. The purple top banner, currently "✨ Strapi MCP is now Generally Available".

What's wrong (Axe, 22 of 22 pages):

Image
  • color-contrast (serious): the link inside the banner is text-amber-200 on bg-strapi-purple-600, which is below the WCAG AA minimum of 4.5:1 for small text.
  • region (moderate): the banner is a plain <div> outside any landmark (<header>, <main>, <nav>, <aside>, …), so screen-reader users navigating by landmarks skip it.

Code: components/page-builder/components/navigation/top-banner/StrapiTopBanner.tsx

  • wrapper: <div data-top-banner className="bg-strapi-purple-600 …">
  • link color: [&_a]:text-amber-200 (hover: amber-100)

How to reproduce: run the Axe suite, or in Chrome DevTools → Lighthouse → Accessibility, open any page and look for "Background and foreground colors do not have a sufficient contrast ratio" pointing at the banner link.

Done when:

  • the banner link reaches at least 4.5:1 contrast (e.g. white with an underline, or a lighter/darker shade, checked with a contrast checker)
  • the banner is inside a landmark, e.g. the wrapper becomes <aside aria-label="Announcement"> (label from translations)
  • the Axe suite no longer reports color-contrast or region for the banner on any page

Note: one component fix removes the most frequent Axe violations site-wide.

Dominant language
TypeScript
Stars
6
Forks
5
Avg merge
5d 6h
Merged PRs (30d)
7

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from strapi/website

All issues in strapi/website

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.