What we built, what our build refuses to ship, and what we have not done.

Futureful is used by people looking for work, which is everyone, on every device and with every way of using a computer. This page says what we have built for that, what our own build refuses to let us ship, and what we have not done yet.

We do not claim WCAG conformance and we have not published a VPAT, because we have not had a third-party audit. A conformance badge we had not earned would be a published false statement, and it is the one claim a procurement officer can disprove in five minutes. Everything below is something you can go and check instead.

Rather than tell you we honor your display settings, here is what we can see you have set, and what we are doing about each one, in this session.

• Less motion, properly. If your system asks for reduced motion we turn animation off across the product, and each one falls back to a designed still state rather than a frozen frame. A disabled animation that leaves a control mid-transition is worse than the animation.
• Keyboard first. Every control is reachable and operable from a keyboard, with a visible focus ring built as a two-tone band so it stays visible on a dark fill, a light fill and an orange one.
• Skip to content. The app and console shells put a skip link first in the tab order, so a keyboard or screen-reader user is not walked through the navigation on every page.
• Real touch targets. On a touch device every control grows to at least 44 by 44 pixels, applied at the shared primitive rather than page by page, so a small label is still a big target.
• Inputs that do not zoom. Form fields are sized so that iOS does not zoom the page when you tap one, which is the most common reason a mobile form becomes unusable.
• Type we host ourselves. No font network, so text never sits invisible waiting on a third party and never reflows under your cursor.
• Structure that reads. Real headings in order, real landmarks, real tables with real header cells, and captions where a table needs one.

These are not intentions. Each one is a check in our build that fails the deploy, so the regression cannot reach you quietly:

• Text below the contrast floor. Body text under about 19 pixels must clear 4.5:1. The check also catches a correct color faded by a parent’s transparency, which is invisible to a check that only reads the color.
• A state carried only in color. If a screen says something is wrong, or selected, or empty, it has to say it in more than a hue. Color alone is a state a blind user does not have.
• A form field small enough to zoom the page.
• A color pairing nobody measured. Every token in our palette carries its measured ratio, and a token without one fails.
• A placeholder standing in for a label. Grey text inside a box is not a name: it is not announced as one, and it disappears the moment you start typing, so the field goes anonymous exactly when you are checking your answer.
• A decorative arrow inside a button’s name. A “go” arrow after a link’s words gets read out as part of the link, and someone driving this site by voice would have to say it. The arrow stays on the screen; it leaves the name.
• A menu row pointing at an icon that does not exist. It draws a neutral unknown mark instead, and the warning that names the mistake only appears while we are developing — so nothing tells us on the live site. This check does.

Two of those are what we call a ratchet: they fail on anything new, over a written-down list of the ones already there. When this page was last updated that list held 24 decorative arrows and 158 fields leaning on a placeholder. The number is allowed to go down and not up, and we would rather show you the number than imply it is zero.

We would rather tell you which checks exist than claim a grade. If one of them is not catching something that affects you, that is a real bug and clause 09 is how to tell us.

Signed in, under Settings, independently of anything your operating system does:

• Calm. Suppresses non-essential motion even if your system has not asked for it, because most people never find that setting.
• One thing per screen. Removes the side-by-side layouts and asks one question at a time.
• Roomier text. Larger body size and looser line height, applied through the type scale rather than by zooming.
• Plainer language. Shorter sentences and fewer idioms, where a screen supports it.

None of these is a “mode” that hides features. Every tool works the same in all of them.

Futureful is available in English, Spanish, Russian, Italian and French. These are real translations of the product, chosen from the language picker in the footer, not a machine translation layer bolted over the page.

The legal documents are the exception, and we would rather say so than let you find out. The privacy policy, the terms, this page and the sub-processor register are published in English only, and each says so. They now carry an explicit English language tag even when the rest of the site is in your language, so a screen reader pronounces them correctly and your browser still offers to translate them. Publishing an automatically translated privacy policy as authoritative would be a worse document, not a better one.

Stated plainly, because a gap you find yourself is worse than a gap we told you about:

• No third-party accessibility audit, and therefore no VPAT and no conformance claim. When we commission one, the result goes on this page whatever it says.
• No systematic screen-reader test pass across every screen. We build to the structure a screen reader needs; we have not certified the whole product against one.
• The operator consoles are desktop-first today. The job-seeker product is built for phones and desktops equally; the employer, recruiter and admin consoles are not yet, and that is owed.
• Some older pages predate the checks above and are being converted in order of how many people reach them, not all at once.

You should not have to disclose anything to use Futureful, and nothing on this page asks you to. We do not detect assistive technology, we do not record that you use it, and it never becomes a field on your profile or something an employer can see. What your browser tells every website, described in clause 02, is read in your own browser and is not sent to us.

Write to info@futureful.app and say what you were trying to do and where it stopped. You do not have to explain it well or name the standard. “The apply button does nothing with my keyboard” is a complete bug report.

If it stops you getting a job done, tell us that and we will do it with you rather than make you wait for a fix.

info@futureful.app for anything on this page, or support. The same address answers our privacy policy and terms. A real person reads it.