Accessibility

Every storefront the Platform serves meets WCAG 2.2 AA as a floor: in the code, on every screen, for your renters and your staff. Roughly one in four US adults has a disability; a storefront they can’t rent from is lost revenue and legal exposure. ADA web lawsuits don’t warn first.

No overlay widgets, and that’s the point

We will never bolt a floating “accessibility mode” button onto your site. Overlay vendors have drawn FTC enforcement for selling exactly that illusion, and overlay-equipped sites still get sued, because the underlying code is still broken. Compliance here lives in the components themselves: invisible, testable, and on by default. There is no accessibility add-on because none is needed.

What that means in the code

Semantic structure: Native HTML landmarks, headings in order, real tables for tabular data, real buttons and links, never a div pretending. Screen readers get the same structure sighted users see.
Full keyboard operability: Every flow works without a mouse: browsing units, quoting, the entire move-in, operator dashboards. A skip-to-content link is the first element on every page; focus is always visible (2px outline, never removed).
Contrast that holds: Body text at ≥4.5:1 on every surface, verified per tint. Status colors never carry meaning alone; every state is also spelled out in text.
Forms that explain themselves: Labels always visible, errors announced and associated with their fields (aria-describedby), nothing communicated by color or placement alone.
Motion that respects settings: Animations confirm state changes in 150–250ms and zero out entirely under prefers-reduced-motion.
Touch targets that fit thumbs: Renter-funnel targets at 24px minimum (44px preferred). The move-in flow is built for one hand on a phone, mid-move.

Found a barrier?

If anything on a Platform-served page doesn’t work with your assistive technology, that’s a bug, not a feature request. Report it to tyrin@myprecisionit.com and it gets triaged like any other defect.