# Innovations24 Accessibility Conformance Report

## WCAG Edition

(Based on VPAT® Version 2.5Rev)

**Name of Product/Version:** innovations24.us, the Innovations24 for Government website: the November 2026 release (commit 347553a), as tested on 2026-11-02 (UTC).

**Report Date:** November 2026

**Product Description:** The public website of Innovations24 for Government, the government brand of Innovations24 LLC: 21 pages (home, services and one page per service, offers, how we work, regulations, state and local, how to buy, past performance, bid and proposal toolkit, about, contact, accessibility and site map) plus a not-found page, a contact form and downloadable documents. Static HTML and CSS with one small script for the phone menu, the copy buttons and the contact form, served by Cloudflare Workers.

**Contact Information:** [info@innovations24.us](mailto:info@innovations24.us) · [+1 (832) 775-8397](tel:+18327758397) · [https://innovations24.us/contact](https://innovations24.us/contact)

**Notes:**

- Scope: the 21 pages in the site's sitemap (/, /services, /services/ai-and-agents, /services/data-and-commercial-platforms, /services/erp-and-business-applications, /services/cloud-ot-and-digital-twins, /services/self-funding-ai, /services/portfolio-and-capital-governance, /services/enterprise-strategy-and-architecture, /services/physical-ai, /offers, /how-we-work, /regulations, /state-and-local, /how-to-buy, /past-performance, /bid-toolkit, /about, /contact, /accessibility, /site-map) and the not-found page, including the contact form up to sending a message.
- Third-party components are outside this report: Cloudflare Turnstile, the spam check inside the contact form (it runs in its own frame), and the Calendly scheduling page that "Book a Discovery Session" opens on calendly.com. Next to both, the site offers email and phone as alternatives. External links lead to government and vendor sites that are outside this report.
- Documents offered for download are not covered by the tables below. Their PDF properties at the time of testing: Innovations24_Capability_Statement (tagged, language set, title set); Innovations24_Corporate_Brochure (tagged, language set, no document title); Innovations24_Overview (tagged, language set, title set). Any document is available in another format on request ([info@innovations24.us](mailto:info@innovations24.us)).
- The site is designed and tested to WCAG 2.1 Level AA (see the accessibility statement at [innovations24.us/accessibility](https://innovations24.us/accessibility)). This report also answers the criteria that WCAG 2.2 adds.
- Fixed before this release, from the first test pass: the form-field borders were darkened to at least 3:1 against their background (WCAG 1.4.11); a site map page was added so that every page can be reached in two ways (WCAG 2.4.5); and the group labels of the regulation map became row-group headers (WCAG 1.3.1).
- Tested by: the test specialist (a role), on 2026-11-02 (UTC), with the methods under Evaluation Methods Used.
- Review and sign-off: Pending sign-off by the accountable architect, who checks every row against the test evidence.
- This is the first report for this site. A revised report will change the report date and explain the revision here.
- Prepared by Innovations24 LLC. VPAT is a registered service mark of the Information Technology Industry Council (ITI).

**Evaluation Methods Used:**

- Automated: axe-core 4.14.0 in headless Chrome 155.0.8059.80 with the WCAG 2.0, 2.1 and 2.2 Level A and AA rules, the best-practice rules and the label-in-name rule, on every page at 1440, 390 and 320 CSS px wide: 66 runs, 0 violations. Items axe-core could not decide (color-contrast 600, th-has-data-cells 3) were reviewed by hand; the text-contrast items were measured from screenshots (400 measurements).
- Scripted and manual: a keyboard-only Tab pass through every page at 1440 and 390 CSS px (3338 focus stops: reach, visible focus, focus not hidden by the sticky header, no trap); reflow at 320 CSS px and at 200 percent zoom (640 CSS px); the WCAG 1.4.12 text-spacing overrides at 1440 and 390 CSS px; a landscape phone viewport; page language, titles, headings, landmarks and the skip link; the phone menu; the contact form's error handling; status messages; consistent navigation and help across pages; the ways each page can be reached; the contrast of form-field borders, outlined buttons and the focus outline.
- Assistive technology: this release was not tested with a screen reader (NVDA, JAWS, VoiceOver or Narrator). Names, roles and states were checked with axe-core and the browser's accessibility properties instead; a screen-reader pass is part of the next revision.
- Testing was done for Innovations24 LLC by the test specialist (a role), who knows the site's content and functions, with the test scripts kept in the site's source repository (tools/acr) and the results kept with this report.

*Innovations24 for Government · Capex-to-Cash AI Transformation, measurable by milestone.*

## Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |

## Terms

The terms used in the Conformance Level information are defined as follows:

- **Supports:** The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- **Partially Supports:** Some functionality of the product does not meet the criterion.
- **Does Not Support:** The majority of product functionality does not meet the criterion.
- **Not Applicable:** The criterion is not relevant to the product.
- **Not Evaluated:** The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

## WCAG 2.x Report

Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

### Table 1: Success Criteria, Level A

| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | The footer logo has the text alternative "Innovations24"; the header logo stands next to the visible wordmark and is hidden from assistive technology, as are the icons, whose meaning the adjacent text carries. The regulation map marks each cell that applies with a symbol and the equivalent hidden text (for example "Applies to AI & Agents"). axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). The spam check in the contact form is a third-party component (see Notes); email and phone are offered as alternatives next to the form. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The site has no audio or video content. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | The site has no video content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | The site has no video content. |
| 1.3.1 Info and Relationships (Level A) | Supports | Landmarks (banner, navigation, main, contentinfo), one h1 per page and heading levels without gaps on every page; lists, data tables with row and column headers and captions, and labelled form fields. On phones the stacked tables keep their table roles. axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). The regulation map, a wide table whose header-to-cell relationships axe-core flagged for review, was checked by hand: every rule has a row header, every service a column header with marked cells below it, the rules are grouped in row groups whose labels are row-group headers, and the rows that apply to all services span all columns. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | The reading order of the markup is the visual order; the style sheet does not reorder content. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Instructions name the control or section they refer to; none rely on shape, color, size, position or sound. |
| 1.4.1 Use of Color (Level A) | Supports | Links in running text are underlined or otherwise distinguished without color alone; required form fields say "(required)" in their labels, and errors are stated in text. axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). |
| 1.4.2 Audio Control (Level A) | Not Applicable | The site plays no audio. |
| 2.1.1 Keyboard (Level A) | Supports | A keyboard-only pass with Tab through every page at 1440 and 390 CSS px reached every link, button and form field (3338 focus stops, none missed). The phone menu opens with Enter and closes with Escape; the copy buttons and the contact form work from the keyboard. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Focus moved through and out of every page with Tab; no element held focus. The spam-check frame in the contact form is a third-party component (see Notes). |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Supports | The site defines no single-character keyboard shortcuts. Escape closes the open phone menu. |
| 2.2.1 Timing Adjustable (Level A) | Supports | The site sets no time limits. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | There is no moving, blinking, scrolling or auto-updating content. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | There is no flashing content. |
| 2.4.1 Bypass Blocks (Level A) | Supports | A "Skip to main content" link is the first focusable element on every page and moves to the main landmark; the pages also use landmarks and headings. |
| 2.4.2 Page Titled (Level A) | Supports | Every page has a title that names the page and the site, and the 21 titles are unique. |
| 2.4.3 Focus Order (Level A) | Supports | Focus follows the reading order. After Escape closes the phone menu, focus returns to the Menu button; after a form error, focus moves to the first field to correct. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Link text names the destination, alone or with its sentence or card; "Read more" links include the service name in their accessible name; links that open a new tab say so to screen-reader users. axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Supports | No function needs a multipoint or path-based gesture. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Supports | Links and buttons are standard HTML controls that activate on release. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Supports | Accessible names contain the visible label text (axe-core rule label-content-name-mismatch enabled). axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Supports | No function is operated by device motion. |
| 3.1.1 Language of Page (Level A) | Supports | Every page declares English (lang="en"). |
| 3.2.1 On Focus (Level A) | Supports | Moving focus does not change the context. |
| 3.2.2 On Input (Level A) | Supports | Choosing a topic or typing in the contact form does not submit it or change the context; the form is sent only with its Send button. |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | The footer of every page gives the company phone number, the email address and a link to the contact page, in the same order; the contact page lists the same direct lines. |
| 3.3.1 Error Identification (Level A) | Supports | When the contact form is sent with missing or malformed entries, an alert states the problem in text, the fields in error are marked invalid, and focus moves to the first of them. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Every form field has a visible label, and the labels say which fields are required and which are optional. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Not Applicable | The site has no multi-step process; the contact form is a single step. |
| 4.1.1 Parsing (Level A)<br>WCAG 2.0 and 2.1 – Always answer ‘Supports’<br>WCAG 2.2 (obsolete and removed) - Does not apply | Supports | For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. In WCAG 2.2 the criterion is obsolete and removed. |
| 4.1.2 Name, Role, Value (Level A) | Supports | Controls are standard HTML elements with accessible names; the phone Menu button reports its state (aria-expanded), and the current page is marked in the navigation (aria-current). axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). Names, roles and states were checked with axe-core and the browser's accessibility properties, not with a screen reader (see Evaluation Methods). |

### Table 2: Success Criteria, Level AA

| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | The site has no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | The site has no video content. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | Supports | The layout is not locked to an orientation; every page was checked in a landscape phone viewport (844 by 390 CSS px) without loss of content. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Supports | The contact form fields that ask for information about the user carry autocomplete values: name, email and organization. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). The 400 text items axe-core could not decide automatically (text over a gradient, an image or an overlapping element) were measured from screenshots against the darkest and lightest background pixel behind them; the lowest ratio was 6.25:1, at or above the minimum for its text size. |
| 1.4.4 Resize Text (Level AA) | Supports | At 200 percent zoom (a 640 CSS px wide viewport at 1280 px) every page reflows to one column without loss of content or function. |
| 1.4.5 Images of Text (Level AA) | Supports | Text is real text. The only image containing text is the logo, which is exempt. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Supports | At 320 CSS px every page reads in one column without horizontal scrolling of the page. Wide data tables (Company verification data; Standards for robot and machine safety; Regulation and service map) scroll horizontally inside their own region, which takes keyboard focus, as the exception for data tables allows. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Supports | Form-field borders measure at least 4.79:1 against their background, and the focus outline measures at least 3:1 against the colors next to it on every focus stop of the keyboard pass (lowest 5.84:1; on gradients, against every gradient color). Buttons are identified by their text labels; icons are decorative. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | With line height 1.5, paragraph spacing 2 times the font size, letter spacing 0.12 and word spacing 0.16 applied to every page at 1440 and 390 CSS px, no text was clipped or overlapped and no page scrolled sideways. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Supports | No additional content appears on hover or focus. |
| 2.4.5 Multiple Ways (Level AA) | Supports | Every page can be reached in at least two ways: the main or footer navigation or links from related pages (for example the services overview and the cards on the home page), and the site map, which lists every page and document and is linked from the footer of every page. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings describe the section they introduce, and form labels describe the information asked for. |
| 2.4.7 Focus Visible (Level AA) | Supports | Every one of the 3338 focus stops in the keyboard pass showed a visible focus outline. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | The sticky header never hid a focused element: page anchors and scrolling leave room for the header, and every focus stop of the keyboard pass was in view (checked once with reduced motion and once with smooth scrolling on two long pages, 246 stops). |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Supports | No function needs dragging. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | Buttons and stand-alone links are at least 24 by 24 CSS px or meet the spacing exception; links inside sentences are exempt. axe-core 4.14.0 found no violations of this criterion in 66 runs (21 pages and the not-found page, at 1440, 390 and 320 CSS px). |
| 3.1.2 Language of Parts (Level AA) | Supports | All content is in English; there are no passages in another language. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | The main navigation and the footer navigation repeat in the same order on all 21 pages. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Components with the same function have the same label on every page (for example the "Book a Discovery Session" button and the capability statement download). |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages say how to correct the entry, for example "Please check the email address." |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Not Applicable | The site takes no legal commitments or financial transactions and changes no stored user data; the contact form sends a message. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Not Applicable | The site has no login or other authentication. The contact form's spam check is not an authentication step (see Notes). |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | The copy buttons announce their result through a polite live region without moving focus. Contact-form errors are announced through an alert region; the confirmation after sending is a status region whose heading receives focus. |

### Table 3: Success Criteria, Level AAA

Not included in this report (Level AAA: No).

## Legal Disclaimer (Innovations24)

This report describes the website as tested on the date and release stated above. It is provided for information about the accessibility of the website; it is not a warranty, a certification or legal advice.