Legal
Accessibility statement
What this site was built to, how it was tested, what is still planned, and how to tell us when something does not work for you.
Last updated: 14 October 2026
ProLevelUp is a product of Galaxian Inc. This statement applies to the ProLevelUp website at prolevelup.app and the ProLevelUp services. In this statement, "ProLevelUp", "we", "us" and "our" mean Galaxian Inc.
Please note: this is a draft prepared for review by the company's attorneys. It has not been approved for publication and it is not legal advice.
Our commitment
Galaxian Inc. wants this website to be usable by as many people as possible, including people who use a screen reader, navigate with a keyboard only, rely on magnification or high contrast, or need motion reduced.
That matters here more than on an ordinary marketing site. People arrive on these pages because a car has broken down, a treatment plan costs more than expected or a pet needs care today. A page they cannot operate is a page that fails them at a bad moment.
We also want to be honest about where we are. This statement says what the site was built to, how we tested it, and what we have not done yet.
The standard this site was built to
This website was built to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That standard was the design and build target for every page, in both English and Spanish.
Building to a standard and being measured against it by an independent assessor are two different things. We have not had an independent audit, so this statement says what was built and tested rather than making a claim about the result.
What was done
- Semantic markup. Pages are built from real headings, lists, tables and landmarks, in a logical order, with one H1 per page, so that a screen reader can announce the structure and a user can skip through it.
- A visible focus indicator. Whatever has keyboard focus is clearly outlined, and the outline is never removed.
- Keyboard operation throughout. Every link, button, form field, menu, accordion and the cookie banner can be reached and operated with a keyboard alone, with no keyboard trap.
- Text contrast of at least 4.5 to 1 against its background for body text, with larger text and interface components meeting their own thresholds.
- Labelled form fields. Every field has a visible label that stays visible, help text where the question needs it, and error messages that are tied to the field they belong to and named in words, not only in colour.
- Alternative text on meaningful images. Images that carry information have alternative text; decorative images are hidden from assistive technology. Where the client has not yet supplied photography, the placeholder carries the alternative text that the final image will use.
- Layout that holds up. Pages remain usable at 200% and 400% zoom and at a viewport 320 pixels wide, with no loss of content and no two-directional scrolling.
- Respect for reduced-motion settings. If your device asks for reduced motion, animation and transitions are reduced or removed.
- Touch targets of at least 24 by 24 pixels, with spacing, so that controls can be hit reliably on a phone.
How it was tested
Automated accessibility scanning with axe-core runs on every page of the site, in both English and Spanish, at desktop, tablet and phone widths, as part of the release process. A page that fails a scan does not ship.
Automated scanning is good at finding missing labels, contrast failures, broken heading order and invalid markup. It cannot judge whether a page makes sense when it is read aloud, whether a keyboard path is sensible, or whether alternative text describes the right thing.
What is still outstanding
We want to be plain about this rather than leave it out.
- Manual keyboard testing of every page and form by a person working without a mouse is planned. It has not been done.
- Screen-reader testing by a person who uses assistive technology day to day is planned. It has not been done.
Until that testing is complete, the strongest honest statement we can make is the one above: this site was built to WCAG 2.2 Level AA and is scanned automatically on every release. If either of these tests finds a problem, we will fix it and record it in the known issues below.
The accessibility preferences widget
This site includes a small preferences widget that lets you adjust text size, spacing, contrast and motion for yourself. Your settings are stored in your own browser and never sent to us.
It is a comfort tool, and that is all it is. The widget is not the basis of any accessibility claim on this site, and it is not a substitute for the site being built properly. Every page is expected to work with the widget switched off, with your own operating-system settings, and with your own assistive technology. If a page only works once you have adjusted the widget, that is a fault in the page and we would like to hear about it.
Third-party content
Some things on or near this site are not built by us: the spam protection on the forms, the customer portal on the ProLevelUp platform, and each financing provider's own website, which a customer may be taken to.
We do not control how those are built, but we do not treat that as the end of the matter. If something a third party supplies is a barrier on our site, that is still our problem to solve — by fixing it, replacing the component, or offering another way to do the same thing. Tell us and we will deal with it.
Known issues
[KNOWN_ISSUES]
No accessibility issues are recorded at the time of writing. That reflects what the automated scans have found, not the result of the manual and screen-reader testing listed above as planned. This section is where any issue we know about will be listed, with what we are doing about it.
How to report a barrier
If any part of this site is hard or impossible for you to use, please tell us. You do not need to know why it is happening or to use any particular words for it.
Email info@prolevelup.app with "Accessibility" as the subject line, and include whatever of this you have to hand:
- the web address of the page, or a description of where you were;
- what you were trying to do, and what happened instead;
- the browser and device you were using; and
- any assistive technology you use, if you are comfortable telling us.
We aim to reply within [REPLY_DAYS] business days. If a fix will take longer than that, we will tell you what we are doing and offer another way to get what you needed in the meantime.
If what you need is to complete something on the site — a demo request, an application to join, a complaint — say so in your email and we will take the information from you directly instead.
This statement and its review
This statement was prepared on the date shown at the top of this page, and it describes the site as it stands on that date.
We review it at least once a year, and sooner when the site changes in a way that affects accessibility, when manual or screen-reader testing is completed, or when someone reports a barrier.
How to contact us
Questions about this statement? Email info@prolevelup.app. To report a barrier, use the same address with "Accessibility" in the subject line.
