Accessibility

Last updated: September 6, 2026

What we are aiming for

We want Void to be usable by as many people as possible, including people who use a screen reader, navigate by keyboard, need larger text, or find movement on screen distracting or painful. We are working toward WCAG 2.2 level AA on this website.

This is a small independent project, so we would rather tell you plainly where we are than claim we are finished. The list of known problems below is real, not a formality.

What is in place

• Reading settings on the blog. Every article has a "Reading" control in the navigation and again in the footer. It offers a light or dark theme, three text sizes, extra space between lines, and a switch to stop the page moving. Your choice is remembered on your device and applied before the page draws, so you never see the wrong version flash first.
• Reduced motion is respected by default. If your device is set to reduce motion, we honour it without asking you a second time. The site setting can only add more stillness, never cancel what your device asked for.
• Text scales with your browser. Type is set in relative units, so browser zoom and your own default font size work normally. Browser zoom is usually the better tool, and nothing here tries to replace it.
• Colour contrast. Body text is checked against the WCAG AA thresholds in both the light and dark themes.
• Keyboard access. Controls are reachable and operable by keyboard, with a visible focus outline. The reading panel closes with Escape and returns you to the button you opened it from.

Known problems

These are the things we know are not good enough yet.

• The main page has no reading settings. The reading control lives on the blog only. The home page is dark and cannot be switched to a light theme yet, and it has no text-size or motion control of its own. Your motion choice still applies there: the home page follows your device setting, and it follows the choice you make in the blog's reading panel. This is a real limitation, not an oversight, and it is on the list.
• The main page has no text-size control. Some headings there are sized to the width of the window, so they do not respond to a text-size setting the way body text does. Browser zoom does work.
• Animation on the main page. The home page uses moving backgrounds. Setting "reduce motion" on your device, or in the blog's reading panel, CALMS them rather than stopping them: the backgrounds keep drifting slowly, and what we switch off is the movement tied to your scrolling, which is the kind that causes trouble. If you need a page that is completely still, we are not there yet.
• We have not tested with every screen reader. We test with VoiceOver. We have not yet tested with JAWS or NVDA.
• No formal audit. Nobody independent has audited this site. Our checks are our own.

Deliberate choices

We do not use an accessibility overlay or a third-party accessibility widget. Those products claim to fix a site automatically, and the people they are meant to help have said clearly and repeatedly that they do not work and often get in the way. We would rather fix the site itself and be honest about what is left.

For the same reason, the reading panel offers only settings that genuinely change something. We have left out options that sound helpful but are not supported by evidence, such as a "dyslexia font", and options your own device already does better, such as cursor size and text-to-speech.

Tell us what is broken

If something here blocks you, please tell us. A short description of what you were trying to do, and what happened instead, is enough. If you use assistive technology, telling us which one helps us reproduce the problem.

Email: info@voidmind.app

We read everything and will reply. If a fix is going to take a while, we will say so rather than go quiet.

Contact

Or Ben David (developer of Void)
Email: info@voidmind.app