Skip to main content

Accessibility

Effective August 21, 2026

FL Permit Pay is used one-handed, on a phone, in the sun, on a roof. Building for that is most of what makes software usable for everyone, but it is not all of it. This page says what we are aiming at, what we have actually measured, what we know is still wrong, and how to tell us when something stops you.

1. Our conformance target

We are working toward Web Content Accessibility Guidelines (WCAG) 2.1, Level AA across flpermitpay.com and the FL Permit Pay application.

We do not claim to fully meet that standard today. Section 4 names the gaps we currently know about. We would rather publish a short honest list than a conformance claim we cannot stand behind.

2. How and when we test

Most recent review: August 21, 2026.

  • Automated testing against the WCAG 2.1 Level A and AA rule set, run over our highest-traffic public pages — the home page, pricing, features, how it works, contact, and guides.
  • Each page tested at a phone width (390 px) and a desktop width (1440 px), in both light and dark appearance, because a problem that only appears in one of the four is still a problem.
  • Keyboard operation of the accessibility panel described in section 5.

What we have not yet done: we have not completed a manual audit with screen readers and other assistive technology, and we have not had an independent third-party audit. Automated testing finds real defects, but it cannot tell you whether a page makes sense when it is read aloud. Both are on our list, and until they are done this page will keep saying so.

3. What works today

These are in place across the public site and the application:

  • A “Skip to main content” link as the first stop on every page.
  • Page language declared, and headings and landmarks used for their real meaning.
  • Controls that are real buttons and links, operable by keyboard, with a visible focus indicator.
  • Your operating system’s reduced motion and increased contrast settings are honoured without you having to change anything here, and the site remains readable in Windows High Contrast mode.
  • Touch targets on the public site sized for a gloved thumb rather than a mouse.

4. Known gaps

From the review dated above. Each of these is a real finding, not a theoretical one, and each is being worked on:

  • Text contrast. Some secondary text falls below the 4.5:1 ratio Level AA asks for: the card text on the guides index, the small print inside the feature detail cards, and the text you type into the contact form. The contact form is marginal (4.36:1); the guides cards are further off.
  • Keyboard access to one scrolling strip. The job-progress strip on the home page can be scrolled with a pointer but is not reachable with a keyboard.
  • Larger text is limited to the public site. The text-size control in the accessibility panel applies to these marketing and reading pages. It is deliberately not yet applied inside the signed-in workspace, because several of its record rows are still fixed-height and would clip rather than reflow at larger sizes — which would trade one accessibility failure for another. Converting those rows is the fix, and it is planned.
  • Assistive-technology testing. As stated in section 2, no manual screen reader audit has been completed yet.

5. The accessibility panel

Every public page has an Accessibilitycontrol in the footer. It opens a panel of display settings you can turn on for your own device: text size, text spacing, a wider reading typeface, a reading guide, high contrast, reduced or removed colour, highlighted links, a larger pointer, paused motion, a dictionary for our industry’s vocabulary, and read-aloud using your own browser’s voice.

This panel is an enhancement, not our accessibility claim.It is off by default, it changes nothing for anyone who does not turn it on, and a setting you have to find is no substitute for a site that works without it. It is not an accessibility overlay: it does not sit between you and the page, it does not modify the page’s structure or labels, and it does not attempt to replace or override your screen reader. Your settings are stored on your own device and are never sent to us.

6. Tell us about a barrier

If any part of FL Permit Pay stops you from doing something, we want to hear about it — including if you are a homeowner opening a contractor’s link rather than a customer of ours.

  • Email support@flpermitpay.comwith “Accessibility” in the subject.
  • Tell us the page or link, what you were trying to do, and what happened. If you know what you are using — a screen reader, magnification, voice control, keyboard only — that helps us reproduce it.
  • We aim to acknowledge every accessibility report within three business days and to tell you what we are going to do about it and when.

If something is blocking you right now, say so and we will get you the information or complete the task another way while we fix the page.

7. Keeping this page true

We re-run the review above when we make a significant change to the public site, and we update the date, the gap list and the method here at the same time. If this page and the product disagree, the product is what counts and the page is wrong — please tell us.

Related: our Privacy Policy and Terms of Service.