The Global Berean is built to meet WCAG 2.2 Level AA. This page describes what’s in place today and how to reach us if something doesn’t work the way it should — accessibility is an ongoing commitment, not a one-time checklist, and we expect this statement to keep changing as the site grows.

What’s implemented

• A skip link at the top of every page to jump straight to the main content.
• Semantic landmarks and a single, logical heading hierarchy on every page.
• Full keyboard operability, including a / shortcut to open search and Esc to close it.
• Visible focus outlines on every interactive element, in a color that meets contrast requirements in both light and dark mode.
• aria-expanded and other ARIA states kept in sync on menus, the mobile navigation, and disclosure controls.
• Support for prefers-reduced-motion — animations and transitions are disabled for readers who’ve requested that at the system level.
• A color palette, in both light and dark themes, where body text exceeds a 4.5:1 contrast ratio.

Known limitations

The article body editor used by our writers currently supports plain-text paragraphs only, so some inline emphasis in older articles may not carry semantic markup. We’re aware of this and treat it as a gap to close, not a design decision.

Reporting an issue

If you use assistive technology and hit a barrier anywhere on this site, please tell us — what page you were on, what you were trying to do, and what happened instead is the most useful report you can send. Contact accessibility@theberean.example (replace with a real inbox before launch). We aim to acknowledge accessibility reports promptly and treat them as a priority, not a queue.