Accessibility Conformance Report
Reloc8te is committed to being usable by everyone, including people who rely on screen readers, keyboard navigation, magnification, or reduced motion. This page is our Accessibility Conformance Report — the completed VPAT®-style disclosure partners ask for during procurement.
- Product
- Reloc8te web application (reloc8te.com)
- Report date
- 24 August 2026
- Evaluated version
- reloc8te.com production, August 2026
- Standards applied
- WCAG 2.1 Level A and AA; Revised Section 508 (36 CFR Part 1194)
- Overall result
- Supports WCAG 2.1 Level AA, with the exceptions listed below
- Contact
- support@reloc8te.com
How this was evaluated
Testing combined automated and manual methods against the live production site, not a staging build or a design file:
- Automated scanning with axe-core against the WCAG 2.0/2.1 A and AA rulesets on public pages.
- Manual keyboard-only traversal of the signup, report generation, sharing, billing and settings flows.
- Computed-style contrast sampling on rendered pages, rather than reading values from the design tokens.
- Reflow and text-spacing testing at a 320px viewport with the required spacing overrides applied.
- Direct inspection of the accessibility tree for names, roles, states and live-region behaviour on authenticated dashboard and admin pages.
Automated tools alone were not sufficient and we do not present them as such. Several of the issues fixed during this cycle — motion with no keyboard-reachable pause, a progress bar with no role, status messages that no screen reader could hear, images whose empty alt text was indistinguishable from a deliberate decorative marking — produce no automated violation at all.
WCAG 2.1 Level A and AA
“Supports” means the functionality meets the criterion without known defects. “Partially Supports” means some functionality does not meet it. “Not Applicable” means the criterion has no bearing on this product.
1. Perceivable
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Supports | Decorative icons are aria-hidden. Charts carry an equivalent sr-only data table. The report map has an sr-only summary naming the origin, destinations and alternative cities. All 14 images in published articles carry alt text, and the editor now requires either alt text or an explicit “decorative” marking before an image can be left undescribed. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Not Applicable | The application contains no time-based media. Articles can embed third-party video; none is currently published. Should any be added, captioning is an editorial requirement and this row will be re-rated. |
| 1.2.2 Captions (Prerecorded) | A | Not Applicable | See 1.2.1 — no time-based media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | See 1.2.1 — no time-based media. |
| 1.2.4 Captions (Live) | AA | Not Applicable | No live media. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not Applicable | See 1.2.1 — no time-based media. |
| 1.3.1 Info and Relationships | A | Supports | Semantic headings with no skipped levels, a single main landmark per page, real table markup with header cells, and fieldset-equivalent grouping (role="radiogroup" with aria-labelledby) for radio sets. Form errors and hints are associated with their controls via aria-describedby. |
| 1.3.2 Meaningful Sequence | A | Supports | DOM order matches visual order; no CSS-reordered content that changes meaning. |
| 1.3.3 Sensory Characteristics | A | Supports | Instructions do not rely on shape, size or position alone. Report-generation step states, previously conveyed only by icon and colour, now also carry text. |
| 1.3.4 Orientation | AA | Supports | No orientation lock; content works in portrait and landscape. |
| 1.3.5 Identify Input Purpose | AA | Supports | Fields collecting the user's own identity or address carry the appropriate autocomplete token. Fields that collect information about a third party — an agent entering a client's details, an admin entering an affiliate — deliberately carry no token, because autofilling the operator's own data there would be incorrect. |
| 1.4.1 Use of Color | A | Supports | Colour is never the sole carrier of meaning. Status is reinforced with text and icon; validation errors carry text as well as a red border. |
| 1.4.2 Audio Control | A | Not Applicable | Nothing plays audio. |
| 1.4.3 Contrast (Minimum) | AA | Supports | All body and UI text meets 4.5:1 (large text 3:1), verified by computed-style sampling on the live site rather than from the design tokens. The amber “8” in the Reloc8te wordmark measures 2.34:1 and is exempt under 1.4.3 as part of a logotype. |
| 1.4.4 Resize Text | AA | Supports | Layout is fluid; text scales to 200% without loss of content or function. |
| 1.4.5 Images of Text | AA | Supports | Text is live text. Article illustrations are photographs and diagrams, not images of text. |
| 1.4.10 Reflow | AA | Supports | Verified at a 320px viewport with no two-dimensional scrolling. Three pages previously failed because long call-to-action buttons and a fixed-padding stats card had a min-content width wider than the viewport; both were fixed at the component level in August 2026. |
| 1.4.11 Non-text Contrast | AA | Supports | Interface component boundaries, focus indicators and meaningful icons meet 3:1. Low-contrast slate-300 icon buttons in the blog admin were raised in August 2026. |
| 1.4.12 Text Spacing | AA | Supports | Tested by forcing the required line-height, letter-spacing, word-spacing and paragraph-spacing overrides. No content was clipped and no new overflow appeared. |
| 1.4.13 Content on Hover or Focus | AA | Supports | No custom hover-revealed content that must be dismissed or hovered to persist. |
2. Operable
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 2.1.1 Keyboard | A | Supports | All functionality is keyboard-operable, including the what-if sliders, the report map markers, and the reviews carousel pause control. |
| 2.1.2 No Keyboard Trap | A | Supports | Focus can always leave dialogs and embedded content. |
| 2.1.4 Character Key Shortcuts | A | Not Applicable | No single-character key shortcuts are implemented. |
| 2.2.1 Timing Adjustable | A | Supports | No session timeout, form time limit, or auto-expiring content. Report generation has no user-facing deadline and the user may leave the page. |
| 2.2.2 Pause, Stop, Hide | A | Supports | The one piece of auto-starting motion — the reviews carousel — has a visible Pause/Play control, pauses on hover and on keyboard focus, and honours prefers-reduced-motion. When stopped it becomes horizontally scrollable so no review becomes unreachable. |
| 2.3.1 Three Flashes or Below Threshold | A | Supports | Nothing flashes. |
| 2.4.1 Bypass Blocks | A | Supports | A skip link is the first tab stop on every page and targets the single main landmark. |
| 2.4.2 Page Titled | A | Supports | Every route has a descriptive, distinct title. 34 routes previously inherited a single site-wide default and were given page-specific titles in August 2026. |
| 2.4.3 Focus Order | A | Supports | Focus order follows meaning. Where a view is replaced wholesale — sending a magic link — focus is explicitly moved to the new heading rather than being dropped to the document body. |
| 2.4.4 Link Purpose (In Context) | A | Supports | Link text describes its destination; icon-only controls carry accessible names. |
| 2.4.5 Multiple Ways | AA | Supports | Persistent navigation, footer navigation, in-content links, and search within articles. |
| 2.4.6 Headings and Labels | AA | Supports | Headings and labels describe topic or purpose. |
| 2.4.7 Focus Visible | AA | Supports | A 2px focus indicator is visible on every interactive element, confirmed with real keyboard traversal. (Programmatic focus does not trigger :focus-visible, so scripted checks under-report this criterion.) |
| 2.5.1 Pointer Gestures | A | Supports | No path-based or multipoint gestures are required. |
| 2.5.2 Pointer Cancellation | A | Supports | Actions fire on the up-event. |
| 2.5.3 Label in Name | A | Supports | Accessible names begin with the visible label text. |
| 2.5.4 Motion Actuation | A | Not Applicable | No device-motion or user-motion actuated functionality. |
3. Understandable
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 3.1.1 Language of Page | A | Supports | The document element declares lang="en". |
| 3.1.2 Language of Parts | AA | Supports | Content is English throughout; no untagged foreign-language passages. |
| 3.2.1 On Focus | A | Supports | Focus alone never changes context. |
| 3.2.2 On Input | A | Supports | Changing a control never submits a form or navigates without an explicit action. |
| 3.2.3 Consistent Navigation | AA | Supports | Navigation appears in the same relative order on every page. |
| 3.2.4 Consistent Identification | AA | Supports | Components with the same function are labelled consistently. |
| 3.3.1 Error Identification | A | Supports | Errors are described in text and programmatically tied to the offending control with aria-describedby and aria-invalid. Before August 2026 the error text was visually adjacent but associated with nothing; that has been fixed in the shared form components, so it holds everywhere they are used. |
| 3.3.2 Labels or Instructions | A | Supports | Every input has a persistent label. Placeholder-only fields were eliminated — a placeholder disappears as soon as the user types and cannot serve as a label. |
| 3.3.3 Error Suggestion | AA | Supports | Validation messages say what to do, not merely that something is wrong. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Supports | Purchases run through a reviewable checkout step. Destructive actions — deleting all reports or documents — require an explicit typed or modal confirmation and are reversible up to that point. |
4. Robust
| Criterion | Level | Conformance | Remarks and explanations |
|---|---|---|---|
| 4.1.1 Parsing | A | Supports | Markup is generated by React with unique ids (element ids are now generated rather than derived from label text, which previously could collide). Note this criterion is obsolete as of WCAG 2.2. |
| 4.1.2 Name, Role, Value | A | Supports | Custom controls expose correct roles, names, states and values — including aria-valuetext on the what-if sliders so amounts are announced as currency, aria-pressed on the carousel toggle, and role="progressbar" with a value on report generation. |
| 4.1.3 Status Messages | AA | Supports | Asynchronous outcomes are announced without moving focus: role="alert" for errors, role="status" for success and progress. The application previously had no live regions at all; 31 status banners were given roles in August 2026. |
Section 508 Chapter 3: Functional Performance Criteria
| Criterion | Conformance | Remarks |
|---|---|---|
| 302.1 Without Vision | Supports | All content and functionality is available to a screen reader, including charts and the map. |
| 302.2 With Limited Vision | Supports | Text meets contrast minimums, scales to 200%, and reflows to 320px. |
| 302.3 Without Perception of Color | Supports | No information is conveyed by colour alone. |
| 302.4 Without Hearing | Not Applicable | No audio content. |
| 302.5 With Limited Hearing | Not Applicable | No audio content. |
| 302.6 Without Speech | Not Applicable | No speech input is required. |
| 302.7 With Limited Manipulation | Supports | Full keyboard operation; no path-based gestures; targets are adequately sized. |
| 302.8 With Limited Reach and Strength | Supports | No sustained or simultaneous inputs are required. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | Plain-language summaries, a stepped wizard with persistent progress, no time limits, and reduced-motion support. |
Known limitations
We would rather state these plainly than let a partner discover them after signing.
Downloadable PDF reports — Supports
Every report page offers a tagged PDF export (“Accessible PDF”) alongside the styled PDF. It is rendered from semantic HTML and printed with a structure tree, so headings, paragraphs, lists and data tables (with captions and header cells) are exposed as such to assistive technology, with a document title and declared language. We verify the structure tree is present in the emitted bytes on every build. This is a tagged PDF; we do not claim certified PDF/UA conformance.
The styled PDF remains untagged — the rendering library it uses has no structure-tagging API — with the web report as its accessible equivalent: every report is available as a fully conforming HTML page inside the application, containing the same content and the same numbers, and the styled PDF points back to it. Anyone who prefers another format can contact us and we will supply the content in an accessible form.
Third-party components
Payment card entry is handled by Stripe Checkout and map tiles are served by OpenStreetMap. These are hosted by their providers and their conformance is governed by those providers’ own accessibility statements. Within our own interface, the map is supplementary: every location it plots is also given as text.
Author-generated article content
Articles are authored through our own editor, which now requires either alt text or an explicit decorative marking for every image. Should video ever be embedded, captions depend on the source platform and are an editorial requirement rather than a technical guarantee.
Tell us about a barrier
If any part of Reloc8te is difficult or impossible for you to use, we want to hear about it — a specific report is far more useful to us than an audit. Email support@reloc8te.com with the page, what you were trying to do, and the assistive technology you were using if relevant. We aim to acknowledge accessibility reports within two business days.
If you need information that is currently only available in a PDF, ask us and we will provide it in an accessible format at no cost.
This report describes the state of the product as tested on 24 August 2026. It is reviewed when significant features ship. See also our Privacy Policy and Terms of Service.