Accessibility
affirmark.com is built and verified to WCAG 2.1 Level AA, the technical baseline Section 508 of the Rehabilitation Act sets for U.S. federal technology. This statement and the self-assessed conformance report below reflect the site as of 10 June 2026.
The bar
The target bar is WCAG 2.1 Level AA across the whole site: the homepage, the changelog, this page, and the error page. The 2018 Revised Section 508 Standards harmonize the federal procurement floor to WCAG Level AA, so meeting the target bar means meeting the legal floor. Affirmark itself is not for sale; we hold the site to this bar because the reader we built it for works in places where Section 508 is not optional.
The method
Verification is continuous, not point-in-time. Every proposed change to this site runs an axe-core scan against the WCAG 2.1 A and AA rule set on every page, plus an automated reflow assertion at a 320 CSS-pixel viewport. Any violation blocks the change from merging.
Automated tooling covers roughly half of the AA success criteria, so a manual checklist covers the rest: a keyboard walkthrough of every page, focus-visibility verification at every stop, a 200 percent zoom spot check, and review of any new media or figures. The manual pass runs on every release and whenever the page structure changes, and each pass is recorded in a dated audit log. The most recent pass completed 10 June 2026.
In place
Keyboard navigation throughout, with a skip-to-content link and instant, visible focus indicators on every interactive element.
Motion that respects prefers-reduced-motion: scroll animations render static and the walkthrough video never autoplays for users who ask for reduced motion.
Semantic HTML: one h1 per page, ordered headings, landmark regions, and native elements for every interaction.
A color palette verified against WCAG contrast thresholds for text and for interactive and graphical elements.
Full-text alternatives on every informational image, figure, and the silent walkthrough video.
The record
Self-assessed, in the conformance vocabulary federal buyers expect. "Supports" means the criterion is met and verified by the method in the notes.
WCAG 2.1 A and AA (automated rule set)
SupportsVerified by axe-core on every change, across every page of this site. Zero violations is a blocking gate: a change that introduces a violation cannot merge.
1.4.10
SupportsAutomated assertion on every page: no horizontal scrolling at a 320 CSS-pixel viewport. Blocking in CI alongside the axe scan.
1.4.4
SupportsRelative (rem-based) type scale throughout. Manual spot check at 200 percent zoom per release, with the automated reflow gate as a continuous proxy.
2.1.1, 2.1.2
SupportsEvery interactive element is native HTML: links, a details/summary disclosure for the mobile menu, and a standard video element. Full keyboard walkthrough per release confirms order and the absence of traps.
2.4.3, 2.4.7
SupportsDocument order matches visual order on every page, beginning with a skip-to-content link. Focus indicators are visible at every stop and appear instantly.
2.2.2, 2.3.3
Supportsprefers-reduced-motion is respected: scroll animations render static and the product walkthrough video does not autoplay. The video carries standard controls so playback can always be paused.
1.2.1
SupportsThe walkthrough video is silent. Equivalent information is carried by its accessible name, its caption, and the surrounding chapter copy.
1.4.1, 1.4.11
SupportsInformational figures differentiate by pattern as well as color (the timeline's pending track is dashed, not merely recolored) and carry full-text alternatives. Interactive and graphical elements meet the contrast thresholds.
3.3.1, 3.3.3, 4.1.3
Not ApplicableThis site has no forms and no dynamic status regions. Contact is a standard email link.
Honest gaps
The product screenshots and the walkthrough video show the CMMC Level 2 surfaces of a synthetic demonstration tenant. Their text alternatives describe those captures accurately. We know of no other conformance limitations; if you find one, we want to hear about it.
If any part of this site is difficult to use with assistive technology, email dayel.ostraco@accelerasolutions.com with the page address and a description of the issue. Accessibility failures are treated like any other release-blocking defect.
Report an accessibility issue →