Accessibility Statement

1The standard we build to

We aim for the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, on the marketing site at scailapp.com. That covers the homepage, pricing, the signup flow, the resource library, the reviews page, the downloads page and the legal pages.

This statement covers scailapp.com. The signed-in SCAIL product (the operator console and the client portal) is a separate surface and is tracked separately.

2What we do

• Every page has a language, a title, one main landmark and a “Skip to main content” link as the first thing a keyboard reaches.
• Everything you can click can be reached and used from the keyboard, and the focus ring is always visible. Menus and dialogs close with Escape.
• Text colors are set once, as shared color tokens, and are checked against the 4.5:1 contrast minimum for text (3:1 for large text and interface parts). A script fails the build if a token drops below it.
• Every meaningful image has a text description. Purely decorative images are marked so screen readers skip them. A script checks this on every build.
• Every form field has a visible label that is tied to the field in code. Buttons say what they do (for example “Email me the resource link”, not “Submit”).
• Animation is off for anyone whose device asks for reduced motion, and the page still shows its final state.
• Our downloadable resource PDFs are produced as tagged PDFs with a document title and language, and they reflow in a PDF reader. Their typefaces are embedded.

3How we test

On each release we run the axe-core engine in a real browser against every page of the site, at a desktop width and a phone width, for WCAG 2.1 A and AA rules. We also check keyboard order by hand on the homepage, signup and resource pages. Automated tools find only part of what a person can run into, so this is a floor, not a certificate. No outside accessibility audit has been done yet.

4Where we are today

Version a11y-2026-10-29, measured October 29, 2026. The latest automated results are published in our engineering report for this release; the count of serious or critical findings on the pages we scan is the number we hold ourselves to, and it is zero before a release goes out.

5Known issues

• The homepage and funding pages include animated product demonstrations. They are decorative. The same facts are in the page text, and the animation stops under reduced motion, but a screen reader user may hear less detail from the demo itself than from the surrounding text.
• The Halo voice reader reads page text aloud. It has no separate transcript, because the text it reads is already on the page.
• Some wide comparison tables scroll sideways on a phone. They can be scrolled with the keyboard, but a narrow screen may need zoom.
• Checkout is run by Stripe, and scheduling by Calendly. We do not control the accessibility of their hosted pages. Tell us if either blocks you and we will book or bill you another way.
• Older resource PDFs were produced before tagging was turned on. They are being re-issued; if one gets in your way, ask for the same content as a plain document.

6Tell us, and we will help

If something on scailapp.com is hard to use, email support@scailapp.com with the page address, what you were trying to do and the device or assistive technology you use. We answer in writing, we aim to reply within two business days, and we will give you the information or service another way while the fix is built.

SCAIL is software for credit repair business owners. Nothing here changes how the product, our Terms of Service or our Privacy Policy work.