Accessibility

1. What we aim for

Our target is the Web Content Accessibility Guidelines, version 2.2, level AA, across the public site, the founder dashboard and the partner portal.

That is a target we build against, not a badge we have earned. We have not been audited against it and we do not claim to conform to it. Forming a company should not depend on being able to use a mouse or see a low-contrast label, so we would rather publish an honest account than a compliance statement nobody has checked.

2. What works today

These are things we have built deliberately and can point to in the code, not aspirations:

• Keyboard operation. Navigation, the order wizard and every form work from the keyboard. Controls are real buttons, links and inputs rather than clickable shapes, and menus and the assistant panel report whether they are open.
• Visible focus. Whatever you have moved to is outlined, with a gap between the outline and the element so it stays readable. The same focus style is used across the whole site.
• A skip link. The first thing the keyboard reaches on any page is “Skip to content”, which jumps past the navigation to the main region.
• Landmarks and headings. Every page has a main region, with navigation, header and footer marked up as such, and named sections in the app and admin areas. Pages have one first-level heading and headings below it run in order.
• Labelled fields. Form fields have real labels tied to the input, hint text where a question needs explaining, and error messages shown next to the field rather than only at the top. Invalid fields are marked for assistive technology, and form-level errors are announced when they appear.
• Images and icons. Images that carry meaning have alternative text. Decorative photographs, background shapes and icons that sit beside a text label are hidden from screen readers instead of being read out as noise.
• Reduced motion. If your system asks for reduced motion, we honour it. Scroll animations, counters, carousel scrolling and autoplaying video all stop or become instant, and page-wide transitions are switched off.
• Light and dark themes. Both are fully built, and the site remembers which one you picked.
• Small screens and zoom. Layouts work down to a 400-pixel-wide phone screen, and pages never scroll sideways. Because the same responsive layout applies at any width, the page reflows rather than breaking when you zoom the browser to 200%.
• Contained tables. Wide data tables scroll inside their own container, so a long fee table cannot drag the whole page sideways.
• Language. Pages declare English, so screen readers pronounce them correctly.

3. Where we fall short

Being specific about gaps is more useful than a general promise, so here are the ones we know about:

• No independent audit. No outside specialist has assessed this site. Our checks are our own, and our own checks miss things.
• Limited screen reader testing. We have not tested with every screen reader and browser combination. Behaviour on a combination we have not tried may be worse than what we describe above.
• No systematic contrast audit. We have not measured the contrast of every piece of text and every control across both themes. If something is hard to read, tell us and we will treat it as a bug.
• Tables on small screens. Our fee and deadline tables scroll sideways on a phone. That is better than breaking the page, but comparing two distant columns on a narrow screen is genuinely awkward.
• The assistant panel. Ella answers in a panel that updates as the reply is written. We have not tested how well that reads on a screen reader, and a long streamed answer may be announced in a way that is hard to follow. Everything Ella can tell you, a person on our support email can tell you too.
• Stored documents. Documents in your account are a mix of pages we generate and scans forwarded by our US filing and registered agent partner. A scan is an image of a page and may have no text a screen reader can read.
• Documents from state agencies. Certificates, notices and forms produced by a state office or by the IRS are made by them, not by us. We cannot change their formatting or accessibility. If one is unusable for you, ask us and we will read it to you or summarise it in an email.

4. If something does not work, we will do it for you

You should not lose a filing deadline because a page will not cooperate. Email [email protected] and we will give you the information, answer the question or complete the task by email instead — including placing an order, checking a company name, telling you what a stored document says or confirming a deadline.

We aim to respond within 5 business days. There is no separate charge for this; it is the same service by a different route.

5. Telling us about a barrier

Reports of specific problems are the main way this page gets shorter. Email [email protected] with “Accessibility” in the subject line and include:

• the address of the page, or the part of the app you were in;
• what you were trying to do, and what happened instead;
• the assistive technology you were using, with its version if you know it — a screen reader, voice control, magnification, keyboard only;
• your browser, its version and your operating system.

We will acknowledge your message within 5 business days and tell you what we found, whether we can fix it, and when. If a fix will take a while, we will say so and offer a way around it in the meantime rather than leaving you waiting.

6. Keeping this honest

Accessibility fixes ship with our normal releases rather than waiting for a dedicated project. We update this page whenever something material changes — when a gap above is closed, when we find a new one, or when a feature launches that changes the picture. The date at the top shows when it last changed.

Our terms of service cover everything else about using the service.

7. Contact

Quick LLC, 30 N Gould St Ste R, Sheridan, WY 82801, USA. Accessibility questions, barrier reports and requests for help another way: [email protected]. A person reads every one. Other ways to reach us are on our contact page.