Every page of ronevexa.com is built to work from a 320px phone with a keyboard alone, not just a mouse on a desktop screen.

What we are aiming at

Ronevexa treats WCAG 2.1 Level AA as the working target for ronevexa.com: enough color contrast to read type against the off-white and near-black grounds, keyboard access to every control including the mobile navigation drawer and the support chat, labels attached to every field rather than left to a placeholder, and a focus outline that stays visible against the grey palette. This is a target the site is measured against, not a certificate issued by anyone. Nothing on this page claims that any outside body has audited or certified the site.

What is actually built in

• A skip link at the top of every page jumps straight past the sidebar to the main content, and it is visible the moment it receives keyboard focus.
• Every link, button, tag and nav item has a minimum 44px tap target and its own visible text label, not an icon standing alone.
• Focus states use a solid three-pixel outline in the signal red, not a faint browser default that disappears against the grey palette.
• Every form field on the site, including the inquiry forms and the chat starter, carries a real <label> tied to its input, and an error message is announced next to the field it belongs to.
• The self-drawing process diagram on the homepage and the Scope Builder's live output both respect prefers-reduced-motion: the diagram shows fully drawn and static, and no panel relies on motion to convey information that is not also written out in text.
• Every photograph carries descriptive alt text naming what is actually in the frame, and no icon is used without an accompanying word.
• The mobile navigation drawer traps focus while open, closes on Escape, and returns focus to the toggle button that opened it.

Where we still find gaps

The support chat widget and the live figures inside the Scope Builder need JavaScript to run. Where a browser has JavaScript disabled, the chat launcher and panel do not appear at all, and every page says plainly in its footer that a scope can still be built by phone or by the plain inquiry form instead. That fallback is intentional, not an oversight, but it means those two tools are not usable by a no-script browser.

The annotated framing photograph on the homepage carries callouts positioned in CSS over the image. On very old browsers without support for modern CSS positioning, those callouts can sit slightly off their intended point; the underlying explanation is repeated in the surrounding text either way, so no information depends on the callout position alone.

How this gets checked

Pages are checked by tabbing through every control in source order and by reading each page with a screen reader with images and motion both on and off. The site is also loaded at 320px, 360px, 414px, 768px, 1024px, 1440px and 1920px to confirm nothing clips or scrolls sideways. Color combinations used for body text and button labels are checked against the 4.5:1 contrast ratio WCAG AA calls for at normal text sizes.

Tell us what does not work

If a page, a form or the Scope Builder does not work with your keyboard, your screen reader or your assistive technology, say so directly. Include the page address and what you were trying to do. Say what happened instead, and the shop will look at it.

For a request to see or delete personal data Ronevexa holds about you, use the data request page instead of this one.