Accessibility Statement

RC Studio Holdings LLC ("TailRoster," "we," or "us") is committed to making the TailRoster platform — the marketing site, the operator application, the pet-parent portal, and the facility websites we generate for operators — usable by everyone, including people with disabilities.

1. Our target

We work toward the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. That standard is our design and engineering target for new work and for remediation of existing surfaces. We have not yet completed a full independent WCAG audit of every surface, so we do not claim certified conformance — see "Known gaps" below for the honest picture.

2. What we do today

Measures currently built into the platform include:

• Keyboard access — a "Skip to main content" link on every page, semantic landmark regions (banner, navigation, main, contentinfo), and visible focus styles.
• Keyboard parity on interactive boards — the lodging board's drag-and-drop works without a mouse: focus a stay, press Space or Enter to pick it up, move it with the arrow keys, drop with Space or Enter, and cancel with Escape.
• Screen-reader support — semantic HTML, labeled controls, and validation messages announced via ARIA live regions, with no color-only error signaling.
• Tap targets — interactive controls meet a 44×44px minimum target size across the parent portal and marketing surfaces.
• Color contrast — text contrast is gated in continuous integration: our test suite computes WCAG relative luminance for the design tokens and fails the build below the 4.5:1 AA threshold for normal text.
• Automated rendered scans — key components from the five highest-traffic app surfaces (dashboard, lodging, reservations, services, sign-in) are rendered and scanned with axe-core in CI; serious or critical violations fail the build.
• Motion sensitivity — decorative animation honors the operating system's reduced-motion preference.
• Consent without dark patterns — the analytics cookie banner presents Accept and Decline with equal visual weight; both are one click.
• Generated facility websites — the sites TailRoster generates for operators are server-rendered, semantic HTML with labeled form fields and no required client-side JavaScript, so they work with screen readers, keyboard-only navigation, and assistive technology out of the box.

3. Known gaps

Accessibility is ongoing work, and some surfaces may not yet meet WCAG 2.1 AA — in particular older operator-dashboard views and third-party embeds outside our control (payment iframes, map widgets). We fix reported barriers in our normal development cycle and prioritize anything that blocks a core task (booking, payments, account access).

Our automated scanning has honest limits. The axe-core rendered-scan suite runs in jsdom, which has no layout engine, so two axe rules are disabled there: color-contrast (jsdom cannot measure rendered colors — contrast is instead covered separately by the token-level 4.5:1 gate described above) and page-has-heading-one (components are scanned as fragments, without the page shell that carries the <h1>). We have not yet completed a full independent WCAG audit of every surface.

If you hit a barrier, tell us: support@tailroster.com. Include the page URL and a short description of what went wrong. Every report is read by a human and routed to the engineering team. If you need information from any page in an alternative format, we will provide it.

4. Enforcement and review

This statement is reviewed at least every six months — the next scheduled review is January 2027 — and updated whenever a material accessibility change ships. If you are not satisfied with our response to a barrier report, escalate to legal@tailroster.com and it will be reviewed by company leadership.

5. Facility websites we host

Operators publish their own content on the facility websites TailRoster generates (business copy, photos, hours). We control the underlying templates — which follow the measures above — but not the content operators add. Accessibility concerns with a specific facility's content are best raised with that facility; concerns with the templates themselves come to us at the address above.

6. Feedback and contact

See also: Privacy Policy · Terms of Service.