Skip to main content
TruJob
  • How it works
  • Features
  • Demo
  • Guides
  • About
Back to home Join waitlist
TruJob
  • How it works
  • Features
  • Demo
  • About
Back to home Join waitlist

Accessibility

This page describes how accessible trujob.io is today, how we tested it, what we know is not right yet, and how to tell us when something does not work for you. If you hit a barrier, email hello@trujob.io.

Our commitment

TruJob exists to help people who are already in a difficult position. A tool that only some people can use is not much of a safety tool. We treat accessibility as part of the work rather than a box to tick.

We are a very small team, and that shapes what we can promise. We would rather tell you exactly where we are than publish something that sounds better than the site actually is.

Conformance status

We work to Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.

trujob.io is partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the standard is met, but some content does not yet fully conform. The specific gaps we know about are listed below.

We have not been independently certified. Everything on this page comes from our own testing.

How we tested

  • Method: self-evaluation, using automated analysis of page structure and colour contrast across every page on the site.
  • Date of last evaluation: August 27, 2026.
  • Coverage: all public pages on trujob.io.
  • Not yet done: manual keyboard testing, screen reader testing, and testing with people who use assistive technology day to day. Automated testing finds roughly a third of accessibility problems. It cannot tell us whether the site is actually usable.

What is in place today

  • Every page declares its language.
  • Every page has a "skip to content" link as the first item, so keyboard users can bypass navigation.
  • Pages use real landmark regions, so assistive technology can move between sections.
  • Images carry text alternatives. Decorative elements are hidden from assistive technology rather than announced as noise.
  • Form fields have labels.
  • Links are written to make sense out of context. We avoid "click here" and "read more".
  • Text meets the minimum contrast ratio for its size across the site.
  • Heading structure follows a logical order without skipped levels.
  • Pages do not block zoom. Text scales to 200% without losing content.
  • Nothing autoplays audio or video.
  • Our printable guides can be read without scripting, and print cleanly.

Known gaps

These are the things we know are not right yet. We would rather list them than let you find them.

  • We have not completed manual or assistive technology testing. Structure and markup have been checked. Focus order, focus visibility, and how interactive elements announce themselves have not been verified end to end.
  • Two guide pages use a slightly different page template from the rest of the site. They meet the same standard, but some conventions differ.
  • We have not had an independent audit. Treat this page as a self-assessment until we do.
  • Third-party and external content. Our cookie consent notice comes from a third-party provider whose markup we do not control. We also link out to government and nonprofit resources, and we cannot guarantee those sites meet the same standard.

What we are doing next

Our current plan, in order. We will update this page as each item is completed.

  • Keyboard-only review of every page, checking focus order and visible focus. Target: October 2026.
  • Screen reader testing across the major platforms. Target: November 2026.
  • Testing of the third-party cookie notice for keyboard and screen reader operability, and replacing it if it cannot be made accessible. Target: November 2026.
  • Bringing the two divergent guide pages into line with the rest of the site. Target: December 2026.
  • Independent third-party audit, once budget allows. Target: 2027.

These are targets, not guarantees. If one slips we will say so here rather than quietly move it.

What this page covers

This statement applies to trujob.io. The TruJob browser extension has not launched. It is being built to the same WCAG 2.1 Level AA target, with keyboard operability and screen reader support treated as requirements rather than extras. We will publish a separate statement covering it when it ships. We are not going to claim it is accessible before we have tested it.

If you cannot use this site

If any part of trujob.io does not work for you, email hello@trujob.io and tell us what you were trying to do. We will send you the information in another format, or answer your question directly by email. You should not have to fight the website to get help.

Telling us about a problem

Email hello@trujob.io. It helps if you can include:

  • The page address
  • What you were trying to do
  • Your browser, and your assistive technology if you use one

You do not need to know the technical term for the problem. "The text is too faint to read on this page" is a useful report.

We read every accessibility report and aim to reply within ten business days. We cannot always promise a fix date, but we will tell you honestly what we can do and when.

If we get it wrong

If you contact us and are not satisfied with the response, reply and say so. It will go to the founder rather than be handled as routine support.

Last updated: August 27, 2026

TruJob

From inbox to offer, we've got you covered. AI-powered job scam protection for every worker.

Product

  • How it works
  • Features
  • Newsletter

Company

  • About
  • Guides
  • Security
  • Our commitment
  • FAQ
  • If you were scammed
  • Press & media

Legal

  • Privacy
  • Terms
  • Cookie policy
  • Cookie preferences
  • Contact
© 2026 TruJob LLC™. All rights reserved.