castomUI
Open castomUI

Accessibility

What this site does,and what has not been checked.

An accessibility statement that lists only achievements is marketing. This one lists what was built, what was assessed and how, and — the part that is actually useful to you — what nobody has verified yet.

Last reviewed: 20 September 2026. Applies to castomui.com, every page, in every language it is published in.

The standard we are aiming at

This website is built to target WCAG 2.1 level AA. That is a statement of intent and a description of measures, not a certificate: the site has not been independently audited, and no external accessibility expert has signed anything off. What follows is a self-assessment by the people who built it, which is worth exactly as much as you would expect that to be worth.

We are a private company rather than a public body, so nothing obliges us to publish this page. We publish it because a reader deserves to know what to expect before they spend twenty minutes finding out the hard way.

What this statement covers

The marketing website at castomui.com — every page, including this one. It does not cover the editor at castomui.com/editor, which is a different piece of software with its own interface, its own windows and controls, and its own assessment. Nor does it cover the websites people build with castomUI: how accessible those are depends on the components, colours and content chosen for them, and on the people who chose them. Where the product falls short for you, the address at the bottom of this page still reaches the right people.

What is built in

A reader's control panel
The person icon in the header opens settings that change the page immediately and are remembered on your device: four colour schemes (system, light, dark and high contrast), three text sizes, wider letter, word and line spacing, and reduced motion.
High contrast, in both directions
The high-contrast setting follows whether your system is light or dark, giving black on white or white on black, with heavier rules and no decorative colour.
Motion that can be switched off
The animation in the header illustration and the smooth scrolling both stop — either from the panel, or automatically if your operating system already says you prefer reduced motion. We do not require you to ask twice.
Read aloud
The Listen button reads the page's text, block by block, highlighting where it is. It uses your own device's voice, so nothing is sent anywhere. This is not a screen reader and is not offered as a substitute for one; it is for people who find long reading tiring. If you use a screen reader, it stays out of your way.
Keyboard
Everything is reachable and operable by keyboard. The menus are native <details> elements, so they open with Enter and close with Escape whether or not JavaScript is running. Focus is always visible — a three-pixel outline that is never removed, only ever restyled.
Structure and language
One <h1> per page, headings in order, landmarks for the header, navigation, main content and footer, a skip link as the first focusable element, and a language declared on every page and on individual phrases in another language.
Typography and targets
Nothing is set below 14px. Interactive controls are at least 44px tall. Text reflows to a single column without horizontal scrolling; wide content scrolls inside its own box rather than pushing the page sideways.
No icon fonts, no emoji as icons
Every icon is an inline SVG marked decorative, so a screen reader announces the label rather than reciting a character name. An icon never carries meaning on its own.
It works without JavaScript
With scripts blocked, the page is complete and legible: menus open, links work, the content is all there. Scripts add the reader's panel, hover-opening menus, the read-aloud button and sending the contact form — they do not gate the content, and the contact page gives an e-mail address for when the form cannot be sent.

What has not been verified

Being specific here is the point of the page:

  • No independent audit. No third party has tested or certified this site.
  • No published screen-reader test report. The site was built following the practices above, but we have not run and published a structured test with NVDA, JAWS or VoiceOver, and we are not going to imply that we have.
  • No testing with users with disabilities. This is the gap that matters most, and it is the one we would most like to close.
  • Colour contrast is designed but not exhaustively measured. The palette was chosen with contrast in mind, but not every state in every theme has been measured with a tool.
  • The read-aloud feature depends on your device. Voice quality, and whether a voice exists at all for the language you are reading, is your operating system's business rather than ours.

Tell us when it fails you

If something here is hard or impossible to use, we want the specific case — the page, what you were using, and what happened. Write to hello@castomo.com with "accessibility" in the subject.

We reply within 14 days. We will tell you honestly whether it is something we can fix quickly, something that needs rebuilding, or something we are not going to be able to do — rather than acknowledging your message and quietly doing nothing, which we are aware is the industry norm. If our answer does not satisfy you, you can take the matter to the authority responsible for accessibility supervision in your country.

One thing we will not do is add an overlay widget — the sort that promises instant compliance from a single line of script. They are broadly disliked by the people they claim to help, and they would also be a script from another company on a site whose privacy position is that its scripts come only from Castomo's own servers. A company that sells a website builder should know better than to bolt one on.

How this site was assessed

By manual review during construction: keyboard-only walkthroughs, all four themes checked at three text sizes, the page read with scripts disabled, and layout checked from 320px upwards. Automated checking covers the stylesheet — every colour must be defined in every theme — and the HTML, where an unresolved template placeholder or a dead internal link stops the build rather than shipping.

This statement was written on 14 September 2026, by the people who built the site, on the basis of that review. None of it substitutes for a real audit. It is what we did.

Illustrations by GetIllustrations.com (Ghost pack).