Skip to content
bnsmag

Legal

Accessibility Statement

The web should be readable by everyone. Here is what we've done, where we fall short, and how to tell us when something blocks your way.

Last updated · May 1, 2026

Our promise

bnsmag aims to meet WCAG 2.2 Level AA across every page on bnsmag.com. Accessibility is treated as a requirement, not a feature, meaning a page that does not meet our baseline does not ship.

Standards we follow

  • WCAG 2.2 Level AA, the current international baseline.
  • Semantic HTML for every interactive element (no <div> buttons).
  • Keyboard navigation for every interaction. Try it: Tab through any page.
  • Visible focus rings on every focusable element.
  • Color contrast ratios of at least 4.5:1 for body text, 3:1 for large text and UI.
  • prefers-reduced-motion respected on all decorative animation.
  • Alt text on every editorial photograph, written by the author of the piece.

What we've built in

  • A logical heading hierarchy on every page (one <h1>, descending).
  • Skip-to-content link on every page (press Tab on arrival).
  • Form fields with explicit labels and error messages.
  • Live regions for status messages (subscribe confirmation, search results).
  • Captions for every gallery image, not just alt text.
  • Tested with VoiceOver (macOS), NVDA (Windows) and TalkBack (Android) before each major release.

Known issues

We are not perfect. Currently, we know about the following gaps:

  • The map embed on beach review pages comes from a third party (Google Maps / OpenStreetMap) and inherits their accessibility limits. We expose the same data (coordinates and a directions link) as text alternatives.
  • The image lightbox does not yet support pinch-zoom on touch devices. On the backlog for the next release.
  • Some legacy articles from before May 2026 may have missing alt text. We are backfilling.

Report a barrier

If anything on the site is difficult to use, keyboard, screen reader, low-vision, cognitive, motor, please tell us. We treat accessibility reports the same as factual corrections: triaged within two business days, fixed as quickly as possible, with a reply.

Email hello@bnsmag.com with "Accessibility" in the subject line. Include the page URL and a sentence on what's broken. If your assistive technology has a version number, that helps too.

We aim to acknowledge within two working days and ship a fix as soon as we can.

All legal pages

Questions? Write to hello@bnsmag.com.