Accessibility
Accessibility conformance report
awesomecause.com · WCAG 2.2 edition, in the VPAT® 2.5 format · Report date October 10, 2026
Public agencies ask their vendors for an accessibility conformance report (ACR), usually written on the VPAT template. This is ours, for our own website. It covers every WCAG 2.2 success criterion at Levels A and AA, says how we tested each one, and lists what we still have to fix. Where we have not tested something, we say so rather than claim it.
For the plain-language version, read our accessibility statement. If you need this report in another format, email hello@awesomecause.com.
Report details
| Product | The awesomecause.com website, as published on the report date. |
|---|---|
| Report date | October 10, 2026 |
| Description | The marketing website of Awesome Cause LLC: static pages, a mobile menu, an ADA Title II notice bar, and a contact form in a dialog. The form uses Cloudflare Turnstile to stop spam. |
| Contact | hello@awesomecause.com |
| Scope | Twelve pages: home, ADA Title II, websites, AI rollout, web applications, mobile and desktop apps, government, nonprofits, leadership, accessibility statement, privacy notice, and the page-not-found page. On every page: the ADA Title II notice bar, header, mobile menu, footer, and the contact dialog with its form, error messages and confirmation. This report and the pages added on the report date (pricing, the ADA Title II readiness checklist, and the resource library with its guides and planning tools) were checked with the automated tools and the reflow and text-spacing tests. |
| Evaluation methods |
|
Standards and terms
This report covers the Web Content Accessibility Guidelines (WCAG) 2.2, Levels A and AA. It does not cover Level AAA. WCAG 2.1 Level AA, the standard the ADA Title II rule names, is a subset of WCAG 2.2 Level AA: every 2.1 success criterion is in the tables below, plus the ones 2.2 added (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7 and 3.3.8).
- Supports: the site meets the criterion without known defects, or meets it with equivalent facilitation.
- Partially Supports: some of the site does not meet the criterion.
- Does Not Support: most of the site does not meet the criterion.
- Not Applicable: the site has no content the criterion applies to.
Summary
No criterion is rated Does Not Support. One Level AA criterion is Partially Supports; its remark says where and why.
| Conformance level | Level A (32) | Level AA (24) |
|---|---|---|
| Supports | 24 | 16 |
| Partially Supports | 0 | 1 |
| Does Not Support | 0 | 0 |
| Not Applicable | 8 | 7 |
Table 1: Level A success criteria
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text content | Supports | The logos and the “Made in the USA” mark have text alternatives. The illustrations are decorative and have empty alt text, and the inline icons are hidden from assistive technology. Icon-only buttons (menu, close) have accessible names. |
| 1.2.1 Audio-only and video-only (prerecorded) | Not Applicable | The site has no audio or video. |
| 1.2.2 Captions (prerecorded) | Not Applicable | The site has no video. |
| 1.2.3 Audio description or media alternative (prerecorded) | Not Applicable | The site has no video. |
| 1.3.1 Info and relationships | Supports | Landmarks (banner, navigation, main, footer, and a labelled complementary region for the notice bar), one h1 per page with nested headings, real lists, labelled form fields, and a named group for the checkboxes. Required fields carry the required attribute. Checked with axe and the accessibility tree; not yet with a screen reader. |
| 1.3.2 Meaningful sequence | Supports | Reading order follows the source order, which matches the visual order at every width we tested. |
| 1.3.3 Sensory characteristics | Supports | No instruction depends on shape, color, size, position or sound. |
| 1.4.1 Use of color | Supports | Links in text are underlined. The current page in the navigation is marked with an underline and aria-current. Form errors are a written message with an icon, not just a red border. |
| 1.4.2 Audio control | Not Applicable | Nothing plays sound. |
| 2.1.1 Keyboard | Supports | Every link, button, menu and form control works from the keyboard, including opening and closing the menu and the contact dialog. |
| 2.1.2 No keyboard trap | Supports | The contact dialog makes the page behind it inert while open, as a modal should, and closes with Esc or its Close button. Focus then returns to the button that opened it. |
| 2.1.4 Character key shortcuts | Not Applicable | The site has no single-key shortcuts. |
| 2.2.1 Timing adjustable | Not Applicable | The site sets no time limits. The form’s spam check renews itself if it expires. |
| 2.2.2 Pause, stop, hide | Supports | Nothing moves on its own for more than five seconds. The few short animations play once (or only while the form sends) and are off when the device asks for reduced motion. |
| 2.3.1 Three flashes or below threshold | Supports | Nothing flashes. |
| 2.4.1 Bypass blocks | Supports | A “Skip to main content” link is the first tab stop on every page, and every page has landmarks. |
| 2.4.2 Page titled | Supports | Every page has a unique title that describes it. |
| 2.4.3 Focus order | Supports | Tab order follows the visual order. The dialog takes focus when it opens and gives it back when it closes, including when it was opened from the mobile menu. |
| 2.4.4 Link purpose (in context) | Supports | Link text describes its destination on its own or with its sentence. Card links are named by the card’s title. |
| 2.5.1 Pointer gestures | Not Applicable | Nothing uses multipoint or path-based gestures. |
| 2.5.2 Pointer cancellation | Supports | Controls act on release (standard click), not on press. |
| 2.5.3 Label in name | Supports | Accessible names match or begin with the visible label. |
| 2.5.4 Motion actuation | Not Applicable | Nothing responds to device motion. |
| 3.1.1 Language of page | Supports | Every page declares lang="en". |
| 3.2.1 On focus | Supports | Focusing a control never changes the page or moves focus. |
| 3.2.2 On input | Supports | Changing a form field never submits the form or changes the page. Choosing an organization type only changes the email field’s example text. |
| 3.2.6 Consistent help | Supports | Our email address and the “Tell us about your project” link are in the footer of every page, in the same order, and in the call-to-action band above it on every page that has one. |
| 3.3.1 Error identification | Supports | A missing or invalid field gets a written message, is marked invalid (aria-invalid) and is linked to its message (aria-describedby). Focus moves to the first field to fix. Errors the server returns are shown the same way. |
| 3.3.2 Labels or instructions | Supports | Every field has a visible label. Required fields are marked with an asterisk and the required attribute; we plan to add a note explaining the asterisk. |
| 3.3.7 Redundant entry | Supports | The form is one step and never asks for the same thing twice. What you typed stays in place after an error. |
| 4.1.1 Parsing | Supports | WCAG 2.2 removed this criterion as obsolete and treats it as always satisfied. For WCAG 2.1 reviews: html-validate reports no errors on any page. |
| 4.1.2 Name, role, value | Supports | Native HTML controls throughout. The menu button reports expanded or collapsed (aria-expanded), and the contact form is a native modal dialog named by its title. Checked with axe and the accessibility tree; not yet with a screen reader. |
Table 2: Level AA success criteria
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (live) | Not Applicable | The site has no live audio or video. |
| 1.2.5 Audio description (prerecorded) | Not Applicable | The site has no video. |
| 1.3.4 Orientation | Supports | Pages work in portrait and landscape; nothing locks the orientation. |
| 1.3.5 Identify input purpose | Supports | The name, email and organization fields have autocomplete values (name, email, organization). |
| 1.4.3 Contrast (minimum) | Supports | Every text and background pair in our design system is at least 4.5:1 (3:1 for large text), including hover states. axe found no contrast failures; text over the star pattern on dark sections was reviewed by eye. |
| 1.4.4 Resize text | Supports | At 200% browser zoom no text is cut off or lost; window title bars wrap instead of truncating. Text sizes are set in pixels, so browsers’ text-size-only settings (as opposed to zoom) may have no effect. |
| 1.4.5 Images of text | Supports | Text is real text. The only images of text are the logos and the “Made in the USA” mark. |
| 1.4.10 Reflow | Supports | Every page, the mobile menu and the contact dialog reflow to 320 pixels with no sideways scrolling and nothing cut off: buttons, window title bars and long headline words wrap. The two tables in this report scroll sideways inside their own labelled region, which the criterion allows for data tables. |
| 1.4.11 Non-text contrast | Supports | Field borders, checkboxes and buttons have black keylines. The focus ring is at least 3:1 against every background it was measured on (navy on light grounds, mustard on dark ones). |
| 1.4.12 Text spacing | Partially Supports | With the WCAG spacing override, nothing is lost at 320, 390 or 1280 pixels on any page. One exception, at about 640 pixels wide only: the footer’s email address runs past its column. |
| 1.4.13 Content on hover or focus | Not Applicable | Nothing appears on hover or focus. The mobile menu opens on click and closes with Esc. |
| 2.4.5 Multiple ways | Supports | Every page can be reached from the footer on every page, and from links in the header, the home page and related pages. |
| 2.4.6 Headings and labels | Supports | Headings and form labels describe their content. |
| 2.4.7 Focus visible | Supports | Every tab stop we tested shows a 3-pixel focus ring 2 pixels outside the control. |
| 2.4.11 Focus not obscured (minimum) | Supports | The sticky header never covers the focused element; the page scrolls focus clear of it. If you tab out of the open mobile menu, it can cover what has focus behind it; Esc closes it without moving focus, which WCAG allows. We plan to close the menu when focus leaves it. |
| 2.5.7 Dragging movements | Not Applicable | Nothing needs dragging. |
| 2.5.8 Target size (minimum) | Supports | Every target is at least 24 by 24 pixels or meets the spacing exception; most are 44 or more. A few are smaller than our own 44-pixel goal: the dialog’s close button (36), and the header buttons, skip link and form chips (40 tall). |
| 3.1.2 Language of parts | Not Applicable | All content is in English. |
| 3.2.3 Consistent navigation | Supports | The header, menu and footer are the same on every page, in the same order. |
| 3.2.4 Consistent identification | Supports | Controls that do the same thing have the same name on every page. |
| 3.3.3 Error suggestion | Supports | Error messages say how to fix the problem, for example “Check the email address; it looks incomplete.” |
| 3.3.4 Error prevention (legal, financial, data) | Not Applicable | The site makes no legal or financial commitments and changes no stored data for you. |
| 3.3.8 Accessible authentication (minimum) | Not Applicable | The site has no sign-in. The contact form’s spam check (Cloudflare Turnstile) is not authentication; it is invisible unless Cloudflare needs a click, and it asks no puzzle. You can always email us instead. |
| 4.1.3 Status messages | Supports | When the form sends, focus moves to the “Thanks” message, and errors in fields are announced as focus moves to them. If sending fails, the “That didn’t send” message is an alert (role=“alert”), so screen readers announce it without moving focus. |
What we’re fixing
- Keep the footer’s email address inside its column at about 640 pixels wide with wider text spacing.
- Close the mobile menu when focus leaves it, explain the required-field asterisk, and bring the last few targets up to 44 pixels.
- Test with screen readers, voice control and forced colors, then update this report.
Legal disclaimer
This report describes awesomecause.com as we tested it on the report date. It is our own evaluation, not a third-party certification. Pages and features added later will be covered when we update it. VPAT is a registered trademark of the Information Technology Industry Council (ITI).
Let's talk about your project!
Send a short note about what needs to change. We’ll reply personally, talk through scope and budget, and arrange a conversation if it would help.
Tell us about your projectPrefer email? hello@awesomecause.com
