Legal

Accessibility Statement

Last updated: July 9, 2026 · Effective: July 9, 2026. Jobeezy is built for everyone looking for work. This statement explains the accessibility standard we aim for, where we are not there yet, and how to get help another way if any part of Jobeezy is hard to use.

Get JobeezySee it work

Last updated: July 9, 2026. Effective: July 9, 2026. This Accessibility Statement is published by Jobeezy, Inc. (“Jobeezy,” “we,” “us,” or “our”), a Delaware corporation with its principal place of business at 800 Brazos St., Suite 400, Austin, TX 78701.

The most important thing to know: Jobeezy aims to be, and is partially conformant with, the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. “Partially conformant” means most of Jobeezy meets that standard, but some parts do not fully meet it yet. Accessibility is something we keep working on, not a box we check once. If any part of Jobeezy is hard to use because of a disability, or you need something in a different format, email hello@jobeezy.com with the subject ACCESSIBILITY and we will help you get what you need another way.

Plain-language summary. We design and test the Jobeezy app and website to work with common assistive technology — things like screen readers, keyboard navigation, and screen magnification. We do not claim to be perfect. Below we explain the standard we aim for, the things we know still need work, and — most important — how a person who cannot use the normal screens can still get matched to jobs and apply, with help from us. When we help submit an application, we fill out the employer’s own website for you; those employer pages are built by the employer, not by us, so we cannot control how accessible they are. The full detail is below.

1. Our commitment

Jobeezy is built for working people — all of them. Many of the people we serve are looking for work in retail, hospitality, warehousing, the trades, healthcare support, admin, and delivery, and many face extra barriers already. We want the Jobeezy app and website to be usable no matter how you get around a screen — including if you use a screen reader, screen magnification, voice control, larger text, captions, or another assistive technology.

We treat accessibility as an ongoing effort. We build it into how we design and ship the product, we fix problems as we find them, and we ask you to tell us when something does not work for you so we can make it better.

2. The standard we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG 2.1 AA is the standard most widely used, and most widely referenced by law, to make digital services usable for people with disabilities. It is also the standard behind the European harmonised standard EN 301 549 (see the Legal basis section).

We are also adopting newer improvements from WCAG 2.2 as we go — especially the ones that make touch screens and signing in easier, which matter a lot for our audience. We do not claim full WCAG 2.2 conformance, because we have not tested against the full 2.2 standard.

3. Our conformance status

Using the terms defined by WCAG, Jobeezy aims to be, and is partially conformant with, WCAG 2.1 Level AA. “Partially conformant” means that most of the content meets the standard, but some parts of the content do not fully conform to it. We list the parts we know still need work in the Known limitations section.

We do not claim to be “fully accessible,” “100% compliant,” or “fully WCAG conformant,” and we do not hold any accessibility certification. We think it is more honest — and more useful to you — to tell you where we are, keep improving, and give you a reliable way to get help when something does not work.

4. What this statement covers

This statement applies to the parts of Jobeezy that we build and control:

  • Our marketing website at jobeezy.com (the pages you are reading now).
  • Our web app at app.jobeezy.com, where you sign in and use Jobeezy.
  • Our Android app (com.jobeezy.job).
  • The emails and documents we send you, such as a tailored résumé or cover letter.
  • Our iOS app when it launches. iOS is not yet available; when it is, it will follow the same approach, and we will update this statement.

This statement does not cover things other companies build and control, which we cannot make accessible for them. That includes employers’ own job-application websites and hiring systems, the job postings we gather from other sites, and the app-store and payment screens run by Google Play or Apple. We explain how we still try to help in the Applying on other companies’ websites and Getting help another way sections.

5. Measures we take to support accessibility

Here is what we do to work toward the standard above. These are the things we build in and design for; they describe our aim and effort, not a promise that every screen is perfect.

  • Contrast. Our design system includes color pairs that are checked against AA contrast, so text and buttons are designed to be easy to read in both light and dark themes.
  • Text size and zoom. The apps are designed to respect your device’s larger-text and display-size settings, and we do not suppress that scaling. Text is meant to grow and reflow rather than get cut off.
  • Keyboard. The web app and this website are designed to be operated with a keyboard, with a visible focus indicator. The mobile menu is designed to keep keyboard focus inside it while it is open and return focus when it closes.
  • Screen readers. Buttons, links, and images are given accessible names and roles so screen readers — like TalkBack on Android — can describe them. Decorative animation is hidden from assistive technology, and live changes (like an application’s status) are announced.
  • Motion. Animations are designed to respect the “reduce motion” setting on your device and fall back to a still presentation.
  • Touch targets. Interactive controls in the apps aim for a touch area of at least 44×44 dp, and on Android we aim for Google’s recommended 48 dp.
  • Signing in. You can sign in without solving a memory puzzle. Our sign-in (handled by our authentication provider, Clerk) is designed to work with password managers and to let you paste a one-time code, so you are not forced to memorize or retype it.
  • Less re-typing. Because Jobeezy exists to save you effort, we try not to make you re-enter information you have already given us.
  • Not color alone. Where we can, we avoid relying on color by itself to tell you something important, and pair it with text or a shape.
  • In how we build. We consider accessibility when we design and build features, and we consider accessibility in our design and code review, and use design tokens tuned for AA contrast.

6. Our mobile app

Our Android app is designed with mobile accessibility in mind. That includes support for the TalkBack screen reader, respecting your system text-size and display-size settings, aiming for Android’s recommended touch-target sizes, avoiding color-only cues where we can, and honoring your system “reduce motion” setting.

When our iOS app launches, we plan to support VoiceOver and Dynamic Type in the same spirit, and we will update this statement to cover it.

7. How we test

We assess Jobeezy’s accessibility ourselves (a self-assessment), rather than by an outside audit. We use a mix of design tokens tuned for AA contrast, internal design-system review, and manual testing — including navigating with a keyboard on the web and testing with a screen reader such as TalkBack on Android. We do not currently name a specific certifying auditor, because we do not have one; if that changes, we will say so here.

We also rely on the reports you send us (see Tell us about a problem). Real reports from real assistive-technology users often find issues that automated checks miss, so your feedback is a genuine part of how we test.

8. Compatibility

Jobeezy is designed to work with recent versions of common browsers and assistive technologies, including current versions of major browsers on computers and phones, and screen readers such as TalkBack on Android. Accessibility also depends on the technology you use, so a very old browser, operating system, or assistive technology may not work as well. If you are using current software and still hit a barrier, please tell us.

9. Technical information

Jobeezy’s accessibility relies on the following technologies working together with your browser and any assistive technology you use: HTML, CSS, JavaScript, and WAI-ARIA. Where JavaScript is turned off or not supported, some features may not work as intended. These technologies are relied upon for conformance with the standard named above.

10. Known limitations

We are honest about the fact that some parts of Jobeezy are not fully accessible yet. As of the date at the top of this page, we know about the kinds of issues below and are working to fix them:

  • Some older blog illustrations and images do not yet have rich text descriptions.
  • Some data visuals — such as a job-match Fit Score shown as a dial or chart — may not yet have a full text alternative for screen readers.
  • A few screens may have focus-order or labeling issues with certain screen readers.
  • Some generated documents (like a tailored résumé or cover-letter PDF) may not yet be fully tagged for assistive technology.

This list describes areas we are actively improving; it is not a complete inventory of every issue. If you hit a barrier that is not listed here, please tell us (see below) — that helps us find and fix it faster. This statement is a good-faith description of our ongoing work, not a warranty that Jobeezy is free of every accessibility problem.

11. Getting help another way

This is the part that matters most. If you cannot use the normal Jobeezy screens because of a disability, you do not have to go without. We will help you get the same result another way, at no extra charge.

  • We will help you complete a task. If a step in the app or website is not working for you with your assistive technology, contact us and a person will help you finish it — for example, setting up your profile, searching for jobs, or getting an application submitted.
  • We will provide information in a different format. If something we publish is hard for you to read or use, ask and we will give you the information in an accessible alternative format where we reasonably can.
  • We will work with you on a reasonable accommodation. Tell us what you need, and we will try to find a workable solution together.

To ask for help this way, email hello@jobeezy.com with the subject ACCESSIBILITY, or write to us at Jobeezy, Inc., 800 Brazos St., Suite 400, Austin, TX 78701, USA. We aim to respond within 5 business days and to work with you on a solution or an alternative way to get what you need. This help pathway is separate from the general bug-report channel, so please use the subject line so we can route your request quickly.

12. Applying on other companies’ websites

When Jobeezy helps submit an application, it fills out the employer’s own website or hiring system on your behalf, only after you approve that specific job. Those employer pages are built and controlled by the employer, not by Jobeezy, so we cannot guarantee how accessible they are, and this statement does not cover them.

Our accessibility work covers the Jobeezy app and website that you use directly. If an employer’s application page or a step in the process is a barrier for you, contact us at hello@jobeezy.com and we will help you get that application in another way where we can (see Getting help another way). Jobeezy’s help with applications is convenience automation you approve for each job — it is not an assistive technology or a substitute for the employer’s own accessibility duties.

13. Tell us about a problem

If any part of Jobeezy is hard to use with assistive technology, that is a bug and we want to know. Email hello@jobeezy.com with the subject ACCESSIBILITY and, if you can, tell us:

  • What you were trying to do, and the page or screen where it happened.
  • The device, browser, and assistive technology you were using (for example, an Android phone with TalkBack, or a laptop with a keyboard and screen reader).
  • What went wrong.

We aim to reply within 5 business days and we treat accessibility fixes as a priority alongside other bugs. You do not need to know the technical words — just describe what happened in your own words.

14. If you are not satisfied

If you contact us about an accessibility problem and you are not happy with how we responded, you can ask us to escalate it by replying to us and asking for your report to be reviewed again. We will take another look and get back to you.

If you are in the European Union and you are still not satisfied after contacting us, you can raise the matter with the accessibility enforcement authority in your country under the European Accessibility Act (see the Legal basis section). Each EU member state names its own enforcement body. If you tell us which country you are in, we will do our best to point you to the right authority.

We write this statement with several accessibility frameworks in mind. This is general information, not legal advice, and naming a law here is not an admission that a particular law applies to Jobeezy in your situation.

  • United States — Americans with Disabilities Act (ADA), Title III. Title III addresses accessibility for businesses that serve the public. Courts and settlements commonly use WCAG 2.1 AA as the practical benchmark for websites and apps, which is the standard we aim for.
  • California — Unruh Civil Rights Act. In California, accessibility barriers can be raised under the Unruh Civil Rights Act, which is one more reason we work toward WCAG 2.1 AA and keep improving.
  • European Union — European Accessibility Act. The European Accessibility Act (Directive (EU) 2019/882) has been in force since 28 June 2025. Where it applies to a service we offer to consumers in the EU, we aim to meet the accessibility requirements set out in the harmonised European standard EN 301 549, which is based on WCAG 2.1 Level AA, and to provide the feedback and escalation routes described above.
  • United Kingdom — Equality Act 2010. In the UK, service providers have a duty to make reasonable adjustments for disabled people. WCAG 2.1 AA is the common reference point there too.

16. About this statement

  • Prepared: This statement was prepared on July 9, 2026.
  • Last reviewed: July 9, 2026.
  • How we prepared it: by our own review of Jobeezy against WCAG 2.1 Level AA (a self-assessment), not an outside audit.
  • Review cadence: We review this statement and our accessibility work regularly, and again after significant changes to the app or website.

17. Changes to this statement

We may update this statement as Jobeezy changes, as we fix known issues, and as our testing improves. When we do, we will change the “Last updated” date at the top of the page. This statement should be read together with our Privacy Policy, our Terms of Service, and our AI transparency notice. If you have any question about accessibility at Jobeezy, email hello@jobeezy.com.