Accessibility

Accessibility Statement

Our commitment to WCAG 2.2 AA, and how to tell us when we fall short.

Last updated: 2026-05-25

Our commitment

APEX Basketball Performance is committed to making apexbasketballbarcelona.com accessible to all visitors, including those who rely on assistive technologies. We target conformance with the WCAG 2.2 Level AA standard published by the W3C.

Scope

This statement applies to all pages served from apexbasketballbarcelona.com and its subdomains. It does not cover third-party content embedded in our pages (such as Google Maps, Cloudflare Turnstile, or YouTube). Those vendors maintain their own accessibility statements.

Measures we take

  • Mobile-first responsive layout (320–1920+ px)
  • Keyboard navigable across every page
  • Visible focus indicators on all interactive elements
  • Minimum 44 × 44 px touch targets on primary interactives
  • Text contrast meets or exceeds 4.5:1 (normal) and 3:1 (large) on every surface
  • prefers-reduced-motion honoured site-wide, so transitions and scroll-behaviour disable when the OS requests it
  • Semantic HTML used in preference to ARIA where possible (<button>, <nav>, <main>, headings in hierarchy)
  • Skip link to main content as the first focusable element on every page
  • Form fields with explicit labels and inline error messages

Known issues

We will keep a current list of accessibility issues here as the site evolves and as they are reported. At launch:

  • Several placeholder images (coach portraits) will be replaced with real photography during the 2026–27 build-out.
  • Print stylesheet is provided but not yet visually tested across all printer drivers.

Report a barrier

If you encounter an accessibility barrier on this site, or have a suggestion for how we can do better, please email info@apexbasketballbarcelona.com. We aim to respond within 48 hours and to fix or document the issue in our next deployment.

Feedback procedure

When you contact us about an accessibility barrier please include:

  • The URL of the page where you encountered the issue
  • A short description of the problem
  • The browser, device, and assistive technology you were using (if relevant)
Apply for 2026–27