Accessibility Statement

Our commitment

We want everyone to be able to read, watch and listen to OCXLY. The site is built to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and accessibility is treated as a requirement of every release, not a follow-up.

What we have done

• Semantic HTML with a logical heading structure, landmarks and a skip link on every page.
• Full keyboard operability, including the menu, search, audio player and all dialogs, with visible focus indicators.
• Text contrast of at least 4.5:1 against its actual background, including on translucent surfaces.
• Long-form text on a stable, non-transparent background at a comfortable measure and line height.
• Text that scales to at least 200% and layouts that reflow down to 320 px wide without horizontal scrolling.
• Touch targets of at least 44×44 CSS pixels for interactive controls.
• Respect for the prefers-reduced-motion setting: ambient animation is disabled and transitions become instant.
• Descriptive alternative text for meaningful images; decorative graphics are hidden from assistive technology.
• Transcripts for audio episodes and captions on video where the platform supports them.
• Forms with visible labels, clear error messages and no time limits.

Known limitations

• Videos are hosted on YouTube; the embedded player's own controls are provided by YouTube.
• Some older audio episodes may be published before their transcript is complete. The episode page says so when that is the case.
• Glass surfaces rely on backdrop-filter; browsers without it receive a solid fallback background, so contrast is preserved either way.

Testing

Every build runs automated checks with axe-core on desktop and mobile viewports. We also test with keyboard-only navigation, screen readers and browser zoom before significant changes ship.

Tell us about a problem

If anything on this site is difficult or impossible for you to use, please tell us and we will fix it as a priority. Email hello@ocxly.com or use the contact form and choose "Accessibility problem". Include the page address and what happened. We aim to reply within five working days.