Legal

Accessibility Statement

Last updated: May 2026

Our commitment

SimplyNickish is committed to ensuring our platform is accessible to as many people as possible, regardless of ability or technology used. We aim to build to a standard of at least WCAG 2.1 Level AA across simplynickish.com and all associated apps.

This is an ongoing effort. We actively work to identify and fix accessibility issues as the platform grows.

Measures we take

To support accessibility, we:

  • Use semantic HTML elements to communicate meaning to assistive technologies
  • Provide ARIA labels and roles where native HTML semantics are insufficient
  • Ensure interactive elements (buttons, links, form fields) are keyboard-navigable and focusable
  • Use sufficient colour contrast ratios for text and UI elements
  • Support system-level font size preferences
  • Provide descriptive alt text for images that convey information
  • Use focus indicators so keyboard users can see where they are on the page
  • Ensure modals and popups trap focus correctly and are dismissible by keyboard

Known limitations

As SimplyNickish is currently in early access, some pages and features are still being built. Known accessibility limitations at this stage:

  • Some broadcast tool pages (Simply Cast, Simply Ops) are complex real-time UIs which may have incomplete ARIA live region support
  • Overlay widgets are designed for display screens and may not translate meaningfully for screen readers
  • Some third-party embed content may not fully meet accessibility requirements

We are actively working to address these during the early access phase.

Feedback and contact

We welcome feedback on the accessibility of SimplyNickish. If you experience any barriers, or need content in a different format, please contact us:

Email: simplynickish@gmail.com

We aim to respond to accessibility feedback within 5 working days and will do our best to resolve the issue or provide an accessible alternative.

Technical information

SimplyNickish is built with Next.js and rendered as HTML. It relies on the following technologies for conformance:

  • HTML5 semantic elements
  • CSS (media queries for reduced motion, high contrast support)
  • WAI-ARIA where required
  • JavaScript for dynamic interactions (non-essential JS is designed to degrade gracefully)

Enforcement

If you are not satisfied with our response to an accessibility complaint, you can contact the Equality Advisory and Support Service (EASS) in the UK at equalityadvisoryservice.com.