Seven designs. One standard.
Most sites have one design to get right. This one has fourteen — seven presentations, each in light and dark — and every one is held to the same accessibility target. This page explains what we test, what still needs attention and how to tell us when something gets in your way.
OliveCore is designed and tested against WCAG 2.2 level AA, the same target neo optic applies to its wider work. The site supports keyboard operation, text enlargement to 125%, dark and higher-contrast display preferences, and reduced motion. It is currently partially conformant: our matrix testing has identified some colour combinations below the AA threshold, and we publish that plainly rather than rounding them up to a pass.
(01)What we build to
Every page targets WCAG 2.2 at level AA — the current version of the international accessibility standard. neo optic's wider approach is set out on the neo optic accessibility page. This statement concerns olivecore.net specifically.
(02)What that means in practice
On this site we aim to ensure that you can:
- operate interactive controls with a keyboard, follow a visible focus indicator and use a skip link to reach the main content;
- navigate semantic headings, landmarks, labels and accessible names that are intended to support assistive technology;
- enlarge text without important content being clipped or pushed outside the screen;
- use controls with practical touch targets on phones and tablets;
- have non-essential animation and parallax removed when your device requests reduced motion;
- and carry your light/dark, text-size and contrast preferences between the homepage and these utility pages.
(03)The settings available
The OliveCore homepage includes an accessibility panel with:
- Light or dark display — following your system on a first visit, then remembering an explicit choice.
- Three text sizes, up to 125%, in addition to browser zoom.
- Higher contrast, which strengthens supporting text and boundaries.
- Reduced motion, taken from your operating-system or browser preference.
Those choices are restored locally when you open this statement or the privacy notice.
(04)Testing fourteen presentations, not one
A change that corrects one presentation can quietly damage another at 125% text, on a narrow phone or in dark mode. Our QA process therefore drives the same structured content through all seven presentations and both colour modes, with representative and release-level combinations of text size, contrast, motion preference and viewport.
The automated harness checks for document overflow, clipped headings, disappearing controls, panels outside the viewport, keyboard focus that is not restored, incomplete testimonial cards, JavaScript errors and measurable colour contrast. It records exact states and compares approved releases against a frozen baseline. Image-backed text and real-GPU rendering still require human review; the tool labels those limits rather than pretending to measure them.
(05)What is not conformant yet
Our current matrix has identified colour contrast below the 4.5:1 AA threshold in several shared combinations:
- some primary-button labels use white against bright theme accents that need a different foreground or a darker functional colour;
- some supporting labels, dates and captions sit just below the required ratio;
- text over photography or gradients needs a separate visual check because the effective background varies with the crop.
The affected shared colour tokens are being corrected in the current assurance pass. This statement will be updated after the revised palette has been deployed and re-tested.
(06)What we do not claim
We do not claim full AAA across the whole site, and we do not claim that automated testing is sufficient. Automated geometry and contrast checks cannot decide whether a heading structure makes sense, whether an error message is genuinely helpful or whether alternative text describes the right thing. Those decisions need human review.
We also do not claim a named screen-reader test that has not been carried out and recorded. The page structure is designed for assistive technology, but a future manual test record will identify the exact browser, screen reader, tasks and outcomes rather than relying on a vague assurance.
(07)Found a barrier? Tell us
If any part of this site gets in your way, or you need information in a different format, email talk@neooptic.com or call 0800 688 9010. Tell us the page, device and what happened. We aim to reply within five working days.
(08)Enforcement
The Equality Act 2010 requires service providers to make reasonable adjustments so disabled people are not put at a substantial disadvantage. If you contact us about an accessibility problem and are not satisfied with our response, you can contact the Equality Advisory and Support Service.
If a platform offers a choice of designs, ask whether every design is included in the accessibility process or only the default shown in the demo. OliveCore's theme matrix exists so a presentation change cannot quietly lower the standard without being recorded. Ask us about the process.