A statement of work done, not a badge
Plenty of sites carry an accessibility page that was copied from a template and never checked against the actual build. This one works the other way around: every item in the “what is built” list below describes a feature that exists in this site’s code today and was verified in this build. Where a claim holds for the public pages but not yet for the signed-in portals, we say so rather than rounding up.
Our customers work with their hands, outdoors, in gloves, in sun glare, sometimes after an injury that changed how they use a phone. Making this site operable by keyboard, legible at a glance and quiet about motion is not charity — it is knowing the audience.
This page is reviewed and updated as the site changes. The date above is the date the statement was last checked against the build, and it moves when the site does. On October 6, 2026 the note headed “The obligatory note” stopped saying a lawyer would review this page, and the statement was checked against the build again.
The obligatory note
This is a plain-English statement published for transparency. It is not legal advice and it is not a conformance certification. Like the rest of our policy pages, it is written and reviewed by us.
If you spot a claim on this page that does not match your experience of the site, that is a bug in the page or a bug in the site — either way we want to hear about it: support@tailgateoffice.com.
WCAG 2.1 Level AA — working toward it, not claiming it
The Web Content Accessibility Guidelines are the standard almost everyone measures against. Level AA is the level that matters in practice: readable contrast, full keyboard operation, content that works when zoomed, motion that can be switched off.
We build and check against WCAG 2.1 AA. We do not claim full conformance today — a conformance claim should follow a complete audit of every page and state, and we have not finished one. The honest description of where we are: the core mechanics listed below are implemented and verified, and the known gaps are listed further down instead of hidden.
When we do claim AA conformance, it will be because the whole site has been checked against the whole standard, not because the phrase looks good on a legal page.
What is actually built into this site
Each item below is implemented and verified on this site’s public pages. No aspirational entries. The signed-in portals are newer and are covered under known limitations.
A visible keyboard focus ring on every public page
Tab through any page of this site and the focused control gets a clear ring. It uses focus-visible, so mouse users never see it and keyboard users always do — including on browsers that need the fallback.
Real keyboard menu navigation
The site menus work with the keys you would expect: arrow keys move through menu items and Escape closes an open menu instead of stranding you inside it.
A mobile menu that announces itself
The mobile menu button carries ARIA attributes that tell a screen reader what it controls and whether it is open or closed — and they are in the markup itself, so they still announce correctly if a script fails to load.
Touch targets sized for actual thumbs
On the public pages, buttons and tappable controls meet a 44-pixel minimum. Our customers operate phones one-handed on job sites; tiny tap targets fail them faster than anyone.
Contrast checked against the AA thresholds
Text color pairs across the public pages were checked against the WCAG AA contrast ratios — including the footer, and including link hover and focus states, which is where most sites quietly fail.
Reduced motion, respected
If your device is set to prefer reduced motion, the public pages honor it. Animation is decoration here, never information, so nothing is lost when it is switched off.
Alt text on every illustration
Every illustration SVG on the site carries descriptive alt text — an actual description of what the picture shows, not the word "image" or an SEO keyword sandwich.
Known limitations
The part most accessibility pages leave out. Here is what we know is not right yet.
Comparison tables stack on phones
The three head-to-head comparison tables (ResponsiBid, Podium, GoHighLevel) are wider than a phone screen. On a phone each of their rows becomes a block: the feature as its heading, then each product’s answer on its own line, named for the product, so nothing scrolls sideways and a screen reader hears each cell with its column.
Wider than a phone the table is a table. The two tables on the compare hub stack the same way. The same information is in the surrounding text of each comparison page as well.
Third-party content may vary
Where a page embeds content we did not build, the accessibility of that content is set by whoever built it, and it may not meet the bar we hold our own pages to.
We keep third-party material on this site to a minimum for exactly this kind of reason, but we will not vouch for code we do not control — and we would rather say that plainly than imply a guarantee we cannot keep.
Hit a barrier? Tell us.
If something on this site does not work with your keyboard, your screen reader, your magnifier or anything else you use, we want to know — and you should not have to fight a form to report it.
Email us or use the contact form. The answer comes back by email, not as a ticket number that goes quiet, and if you ask for a person, a person answers.
What helps us fix it fast
None of this is required — a two-line email is fine. But if you can include it, the fix gets faster:
This statement is dated on purpose
Statement date: October 6, 2026. An accessibility page that never changes while the site changes underneath it is worse than no page at all. When we add pages or rework features, this statement gets re-checked against the build and the date moves. If the date looks stale to you, treat that as a report-worthy barrier in itself — and use the contact details above.
Built to work with gloves on. And with a screen reader.
If something on this site is in your way, tell us by email or the contact form. And the trial is still 30 days, no card.