Accessibility Statement

Last updated October 16, 2026

Rubyy is built to be usable by as many people as possible, regardless of how they navigate the web. This page describes the accessibility features we have built into rubyy.com, the limitations we are aware of, and how to tell us when something is broken.

Conformance target

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This is the level most jurisdictions reference for public-facing websites (the EU's Web Accessibility Directive, the UK's PSBAR, the US Section 508 refresh, the ADA's commonly-cited bar). We test against AA on every release of the marketing site; some areas exceed AA where it was easy to do so, and a few known gaps fall short. Both lists are below.

The full Rubyy product (the platform itself) is in pre-launch development. When the product ships we will publish a separate accessibility statement covering the dashboard and the storefronts our customers build with it.

What we have built

• Keyboard navigation. Every interactive control on the site can be reached and activated with Tab, Shift+Tab, Enter, Space, and Escape. The first focusable element on every page is a Skip to main content link that jumps past the header.
• Visible focus indicator. A 2-pixel outline appears around any element under keyboard focus, in both light and dark mode.
• Semantic landmarks. The page is structured with <header>, <main>, <nav>, and <footer> regions so assistive tech can jump between them. Heading levels are logical (one <h1> per page, no skipped levels beneath).
• Forms. Both the launch-list signup and the contact form have visible labels, mark required fields with aria-required, surface error messages tied to the input via aria-describedby, toggle aria-invalid on the offending field, and announce submission status through a polite live region. The submit button is disabled until you focus a field, and the form sets aria-busy while the request is in flight.
• Carousel. The featured-product carousel announces slide changes via a polite live region, has labelled previous / next buttons, and dot navigation reads "Go to slide N of M" in your locale. The track also responds to native swipe / arrow scrolling.
• Country picker. The header's country dropdown is a labelled <nav> of links; the active locale is marked with aria-current="true". For multilingual countries (Belgium, Canada, Switzerland, Finland, Luxembourg) each language is its own focusable link.
• Reduced motion. If your operating system has Reduce Motion enabled (macOS / iOS Accessibility, Windows Settings → Accessibility → Visual effects), we disable the gem-shimmer animation, the divider drift, the cookie-banner slide, and the carousel auto-pulse. The site stays static.
• Contrast. Body text and primary actions clear AA contrast in both light and dark mode. Eyebrow labels and link colours flip to a lighter ruby shade in dark mode so they retain contrast against dark cards.
• Alt text. Every meaningful image on the site (product screenshots, audience icons, the OpenGraph cover) has descriptive alternative text. Decorative gems and divider lines are marked aria-hidden so screen readers do not announce them.
• Self-hosted fonts. Pacifico and Poppins are served from the same origin as the rest of the site, so they load even when third-party font CDNs are blocked by privacy tools.
• Language attribute. The page's lang attribute matches the active locale, so screen readers pronounce text with the right voice. The picker lists 41 country / language pairs and remembers your choice for one year.
• Cookie banner. The banner is a labelled region, can be reached via Tab from anywhere on the page, and the Cookie preferences link in the footer re-opens it directly into the per-category settings panel and moves focus there. Reject is one click on the first-time banner, equally prominent with Accept.
• Countdown timer. The visible digit cells update every second but are hidden from screen readers; an off-screen summary is exposed instead and updated once per minute, so assistive tech does not read every tick.
• Status messages. Errors and successes are announced via role="status" live regions, not by colour alone.

Known limitations

We are open about the gaps we have not closed yet. If any of these block your use of the site, please tell us.

• Maltese translation review pending. The Maltese (mt) translation was an initial draft that has not yet been reviewed by a native speaker. If you spot awkward phrasing, please email us.
• Iceland and Luxembourg. Stripe Connect (which we use for payouts) does not localize for Icelandic or Luxembourgish, so visitors from those countries are served English (Iceland) or French / German (Luxembourg). Once Stripe adds those locales we will follow.
• Carousel arrow keys. The carousel responds to clicks, taps, and swipes, but does not currently rotate via keyboard arrow keys when focus is inside the track. Prev / next buttons fully cover the same functionality.
• Cookie-banner first-paint focus. When a first-time visitor lands on the site, the cookie banner is rendered at the bottom but focus stays on the document body so we do not interrupt reading. To reach it via keyboard, tab past the page; or use the Cookie preferences footer link, which moves focus into the banner.

Browsers and assistive technologies

We test the site against:

• Chrome and Firefox on Windows 11 and macOS Sonoma
• Safari 17 on macOS Sonoma and iOS 17 / 18
• Microsoft Edge on Windows 11
• VoiceOver on macOS Sonoma and iOS, NVDA on Windows, TalkBack on Android
• Chromium-based browsers in Windows High Contrast mode

Older browsers and assistive technologies may render parts of the site differently; we will fix specific issues you report.

How to report a barrier

If something on this page does not work for your assistive technology, or you find a contrast / keyboard / screen-reader issue we have missed, email [email protected]. Please include:

• The page URL where you ran into the issue
• What you were trying to do
• The assistive technology / browser you were using
• What happened (and what you expected instead)

We will acknowledge your message within two business days and tell you when we expect to ship a fix.

Formal complaints

If you are based in the EU and we are not able to resolve your complaint, you can escalate to the supervisory authority for accessibility in your member state. UK visitors can refer to the Equality and Human Rights Commission. US visitors can file with the Department of Justice under the ADA.

Changes to this statement

We will update the "last updated" date above whenever we ship accessibility-relevant changes. Significant additions (a new feature on the site, a new locale, a fix to a documented limitation) will also be summarised here.