Accessibility conformance report
Last updated September 27, 2026. This is EveryRamp's own accessibility conformance report, in the style of a Voluntary Product Accessibility Template (VPAT®) 2.5 WCAG edition, for our own website and the pages we deliver to customers (test reports, fix packs, and rebuilt PDFs). It says the same thing about our own product that we say about yours: we report what our automated tests find, and we are honest about what they cannot check.
Product and contact information
| Name and version | everyramp.com, the EveryRamp website and product, as of September 27, 2026 |
|---|---|
| Report date | September 27, 2026 |
| Product description | An automated WCAG 2.1 AA accessibility testing and remediation service: a marketing and ordering website (everyramp.com), private test-report and fix-pack pages, and rebuilt PDF documents delivered to customers. |
| Contact | hello@everyramp.com |
Evaluation methods used
We tested our own website the same way our product tests yours: an automated scan using the axe-core testing engine, plus our own keyboard-only pass (Tab through every page) and a manual visual-contrast check of our color tokens (see the comment at the top of styles.css). We did not run a session with an assistive-technology user, and we say so rather than imply we did — the same limit our reports name for every customer.
Applicable standards
Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the same standard both federal web-accessibility rules point to, and the standard we test every customer's site against.
Terms used in the tables
- Supports: the criterion passes our automated and keyboard-only tests, or does not apply to any content we publish (for example, we have no audio or video).
- Partially Supports: most content meets the criterion; a specific, named gap remains.
- Does Not Support: the criterion is not met.
- Not Applicable: the criterion has no relevant content on this product (for example, there is no audio-only or video-only media anywhere on everyramp.com).
WCAG 2.1 Level A
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Every image carries a text alternative or is marked decorative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | No audio-only or video-only media on this product. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded video with audio on this product. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded video on this product. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML headings, lists, labels and landmarks; verified by our own automated tests. |
| 1.3.2 Meaningful Sequence | Supports | Reading and navigation order follows the visual layout. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not depend only on shape, position or color. |
| 1.4.1 Use of Color | Supports | Color is never the only way information is conveyed. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically on this product. |
| 2.1.1 Keyboard | Supports | Verified by our own keyboard-only pass across every page. |
| 2.1.2 No Keyboard Trap | Supports | Verified by our own keyboard-only pass. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character keyboard shortcuts anywhere on this product. |
| 2.2.1 Timing Adjustable | Not Applicable | No time limits on any page. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | No moving, blinking or auto-updating content. |
| 2.3.1 Three Flashes or Below Threshold | Supports | Nothing on the site flashes. |
| 2.4.1 Bypass Blocks | Supports | Every page has a "Skip to main content" link. |
| 2.4.2 Page Titled | Supports | Every page has a descriptive, unique <title>. |
| 2.4.3 Focus Order | Supports | Focus order follows reading order; verified by our keyboard-only pass. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text describes its destination; no bare "click here" links. |
| 2.5.1 Pointer Gestures | Not Applicable | No multipoint or path-based gestures anywhere on this product; every control works with a single tap or click. |
| 2.5.2 Pointer Cancellation | Supports | Actions fire on release, not on initial press, for every control. |
| 2.5.3 Label in Name | Supports | Visible button and link text matches each control's accessible name. |
| 2.5.4 Motion Actuation | Not Applicable | No motion-activated controls. |
| 3.1.1 Language of Page | Supports | Every page declares lang="en". |
| 3.2.1 On Focus | Supports | Moving focus never triggers a change of context. |
| 3.2.2 On Input | Supports | Changing a form field never triggers an unexpected change of context. |
| 3.3.1 Error Identification | Supports | Required-field and format errors are described in text, not by color alone. |
| 3.3.2 Labels or Instructions | Supports | Every form field has a visible, programmatically associated label. |
| 4.1.1 Parsing | Supports | Verified by our own automated tests; no duplicate IDs or unclosed elements. |
| 4.1.2 Name, Role, Value | Supports | Standard HTML controls throughout; verified by our own automated tests. |
WCAG 2.1 Level AA
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live audio or video on this product. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | No prerecorded video on this product. |
| 1.3.4 Orientation | Supports | No view is locked to one screen orientation. |
| 1.3.5 Identify Input Purpose | Partially Supports | Common fields (email, organization name) use autocomplete; not every field has a mapped purpose. |
| 1.4.3 Contrast (Minimum) | Supports | Text and background colors are chosen for at least 4.5:1, documented in the comment at the top of styles.css, in both light and dark mode. |
| 1.4.4 Resize Text | Supports | Text is sized in relative units and reflows up to 200% browser zoom. |
| 1.4.5 Images of Text | Supports | Headings and body text are real text, not images of text. |
| 1.4.10 Reflow | Supports | The layout works at 390px wide with no horizontal scrolling. |
| 1.4.11 Non-text Contrast | Supports | Focus outlines and form-field borders meet 3:1 against their background. |
| 1.4.12 Text Spacing | Supports | No fixed heights or clipped containers that would break with wider text spacing. |
| 1.4.13 Content on Hover or Focus | Not Applicable | No content appears only on hover or focus. |
| 2.4.5 Multiple Ways | Supports | Every page is reachable from the main navigation and the footer, and most from the sitemap. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | Supports | A visible focus outline on every interactive element, in both light and dark mode. |
| 3.1.2 Language of Parts | Not Applicable | No content in a language other than the page's own. |
| 3.2.3 Consistent Navigation | Supports | The header, footer and navigation are identical across pages. |
| 3.2.4 Consistent Identification | Supports | The same control (for example the "Free scan" button) is labeled the same way everywhere it appears. |
| 3.3.3 Error Suggestion | Partially Supports | Browser-native validation messages suggest a fix for most fields; not independently authored per field. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | The order form requires an explicit confirmation checkbox before submission. |
| 4.1.3 Status Messages | Partially Supports | Key form-submission outcomes are announced; not every dynamic status update on the site uses an ARIA live region yet. |
Honest limits of this report
This report describes our own website's markup and our own automated and keyboard-only testing. It is not a substitute for testing with real assistive-technology users, and we say the same thing to every customer about their own report. "Supports" here means the same thing it means in your report: it passes our automated tests, not that a court, regulator or disabled visitor would agree with every judgment call a human reviewer might make differently.
The private test-report and fix-pack pages we deliver to customers, and the tagged PDFs we rebuild, are built to the same standard and the same templates described in our testing guide; we have not run a separate, itemized ACR against every one of those page types, and we say so here rather than imply otherwise.
This page is general information, not legal advice, and not a certification of compliance with any law.