Accessibility statement
Last updated 7 October 2026
In short
We want everyone to be able to use 8 Signs. We aim to meet the WCAG 2.2 AA accessibility standard on our website and web app. We are not fully there yet, and we fix problems as we find them. If anything gets in your way, email support@8signs.io and we will help.
What this covers
This statement covers our website, www.8signs.io, and our web app, app.8signs.io. It does not yet cover the 8 Signs Android app.
Our goal
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. They are the international guidelines for making websites easier to use for people with disabilities, including people who use a screen reader, a keyboard instead of a mouse, magnification or voice control.
Where we are today
We believe both sites partly meet WCAG 2.2 AA. That means some parts do not fully meet the standard yet, and the ones we know about are listed below. We check the sites ourselves and have not yet had an independent audit.
What we have done
Every page has a clear order of headings and its language set, so screen readers can move around it and pronounce it properly.
Images that carry meaning have text descriptions. Decorative images and the short feature clips are hidden from screen readers, and the text next to each one says the same thing.
Text and buttons are designed for strong contrast against the dark background.
Links, buttons and form fields can be reached and used with a keyboard.
If your phone or computer is set to reduce motion, the moving background stops and the feature clips show a still picture instead.
The feature clips have no sound, and they pause when they scroll out of view.
Form fields have labels, and text boxes in the web app are sized so that phones do not zoom in unexpectedly.
Rejecting cookies is as easy as accepting them: the two buttons are the same size and sit side by side.
Known limitations
The moving background and the looping feature clips have no pause button. They stop if you turn on reduce motion in your device's accessibility settings.
Some articles show Chinese characters next to their English names. A screen reader may read them in a different voice or skip them. The English is always there as well.
Wide tables, such as the zodiac year table and the compatibility grid, scroll sideways inside their own box on small screens, which can be awkward with magnification.
Card payments happen on a checkout page run by Stripe, and signing in with Google happens on Google's own pages. We do not control how those pages work.
Tell us if something does not work
If something is hard to use, or you need information in another format, email support@8signs.io or use our contact form. Tell us which page it was and what happened, and, if you are happy to, what device or assistive technology you use. We aim to reply within five working days.
How we check
Before new pages go live we check them ourselves: text descriptions for images, labels for form fields, a sensible order of headings, and layouts at phone, tablet and desktop sizes. We update this statement whenever the sites change in a way that affects it.
Technical details
Both sites rely on HTML, CSS and JavaScript, and are built for current versions of Chrome, Safari, Firefox and Edge.
Our policies