Accessibility & VPAT
Voluntary Product Accessibility Template (VPAT 2.4 Rev 508) — Section 508 and WCAG 2.1 Level A & AA conformance report for SHIELD/ATLAS public-facing surfaces.
Conformance Summary
The public surfaces in scope substantially conform to WCAG 2.1 Level A and AA. Specific gaps and partial-support items are identified honestly in the criterion-by-criterion tables below. ISS LLC will address identified accessibility issues as they are reported, without publishing a vendor-pursued certification roadmap.
| Standard | Conformance Level | Remarks |
|---|---|---|
| Revised Section 508 — Functional Performance Criteria (Chapter 3) | Supports | Without vision, with limited vision, without perception of color, without hearing, with limited reach/strength, and with limited cognition criteria all addressed; specifics in tables below. |
| Revised Section 508 — Software (Chapter 5: Web) | Supports | Adopts WCAG 2.0 AA criteria; SHIELD/ATLAS is evaluated against the more current WCAG 2.1 AA. |
| Revised Section 508 — Hardware (Chapter 4) | Not Applicable | SHIELD/ATLAS is web software, not hardware. |
| Revised Section 508 — Support Documentation (Chapter 6) | Partially Supports | HTML pages conform. PDF artifacts (whitepaper exports, capability statement) are not yet tagged for full PDF/UA conformance — HTML equivalents are linked from each PDF download. |
| WCAG 2.1 Level A | Supports | All Level A success criteria are supported on in-scope surfaces. |
| WCAG 2.1 Level AA | Supports | Level AA supported with the partial-support items noted in the criterion table below. |
| WCAG 2.1 Level AAA | Not Evaluated | Not in scope for this report. |
WCAG 2.1 Level A Criteria
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Decorative SVG icons carry aria-hidden="true"; meaningful images carry text alternatives. The home page contains zero static <img> tags — visual content is rendered via inline SVG or system fonts. |
| 1.2.1–1.2.3 Time-based Media | Not Applicable | No pre-recorded audio or video content is presented on in-scope surfaces. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML5: <main>, <nav>, <footer> with appropriate roles; lists, headings, and tables use native elements. |
| 1.3.2 Meaningful Sequence | Supports | Reading order in the DOM matches visual order; no reliance on CSS positioning for content sequence. |
| 1.3.3 Sensory Characteristics | Supports | Instructions reference content by name and position; not by shape or color alone. |
| 1.4.1 Use of Color | Supports | GREEN/AMBER/RED status tags include both color and text labels; status pills use both color and text. |
| 1.4.2 Audio Control | Not Applicable | No auto-playing audio. |
| 2.1.1 Keyboard | Supports | All interactive elements are reachable and operable with the keyboard. The PWA install banner, dismiss buttons, and navigation menu are all keyboard-accessible. |
| 2.1.2 No Keyboard Trap | Supports | No modal or interactive component traps keyboard focus. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character shortcuts on public surfaces. |
| 2.2.1 Timing Adjustable | Not Applicable | No time limits on public marketing surfaces. |
| 2.2.2 Pause, Stop, Hide | Supports | Animated background orbs are decorative and respect prefers-reduced-motion; the install banner is dismissible. |
| 2.3.1 Three Flashes or Below | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | "Skip to main content" link is the first focusable element on every in-scope page. |
| 2.4.2 Page Titled | Supports | Each page has a unique, descriptive <title>. |
| 2.4.3 Focus Order | Supports | Tab order follows reading order; no positive tabindex values. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text is descriptive of the destination; ambiguous "click here" patterns are not used. |
| 2.5.1–2.5.4 Pointer / Motion | Supports | No path-based gestures or motion-actuated functions on public surfaces. |
| 3.1.1 Language of Page | Supports | <html lang="en"> declared on every page. |
| 3.2.1 On Focus | Supports | Focusing a component does not initiate a context change. |
| 3.2.2 On Input | Supports | Changing the value of any input does not automatically change context. |
| 3.3.1 Error Identification | Not Applicable | No interactive forms on in-scope marketing surfaces (contact is via mailto:). |
| 3.3.2 Labels or Instructions | Not Applicable | No interactive forms in scope. |
| 4.1.1 Parsing | Supports | Markup is well-formed HTML5; no duplicate IDs on in-scope pages. |
| 4.1.2 Name, Role, Value | Supports | Native HTML elements used wherever possible; ARIA used to clarify non-native interactive widgets. |
WCAG 2.1 Level AA Criteria
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | No live audio content. |
| 1.2.5 Audio Description (Pre-recorded) | Not Applicable | No pre-recorded video content with action-relevant visuals on in-scope surfaces. |
| 1.3.4 Orientation | Supports | Layout adapts to portrait and landscape; orientation is not locked. |
| 1.3.5 Identify Input Purpose | Not Applicable | No interactive forms in scope. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Body text on dark backgrounds (slate-200 on slate-900) measures ≥ 7:1; primary muted text (slate-400 on slate-900) measures ≥ 4.5:1. Some helper / footer text uses lower-emphasis tokens (e.g. rgba(255,255,255,0.4)) that can fall close to the 4.5:1 threshold depending on local background. Issues are addressed when reported via the contact below. |
| 1.4.4 Resize Text | Supports | Text resizes up to 200% without loss of content or functionality; relative units used throughout. |
| 1.4.5 Images of Text | Supports | Text is rendered as text, not images. Logos are SVG with text alternatives where they convey program identity. |
| 1.4.10 Reflow | Supports | Content reflows at 320 CSS pixels width without two-dimensional scrolling. |
| 1.4.11 Non-text Contrast | Supports | Interactive controls and meaningful graphical objects have a contrast ratio of at least 3:1 against their background. |
| 1.4.12 Text Spacing | Supports | Line height, paragraph, letter, and word spacing can be adjusted without loss of content. |
| 1.4.13 Content on Hover or Focus | Supports | Tooltips and dropdowns are dismissible, hoverable, and persistent. |
| 2.4.5 Multiple Ways | Supports | Top navigation, footer navigation, sitemap (/sitemap.xml), and in-page links provide multiple ways to find content. |
| 2.4.6 Headings and Labels | Supports | Headings describe the topic of the section they introduce; labels describe the purpose of controls. |
| 2.4.7 Focus Visible | Supports | A 3px amber outline (outline:3px solid #fbbf24) is applied to every focusable element via :focus-visible. |
| 3.1.2 Language of Parts | Supports | Page content is in English; foreign-language phrases (military doctrine acronyms) are explained in context. |
| 3.2.3 Consistent Navigation | Supports | The top navigation and footer are consistent across all in-scope pages. |
| 3.2.4 Consistent Identification | Supports | Components with the same functionality are identified consistently (e.g., dismiss buttons, back links). |
| 3.3.3 Error Suggestion | Not Applicable | No interactive forms in scope. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | No legal, financial, or data-modification transactions on in-scope surfaces. |
| 4.1.3 Status Messages | Supports | Dynamic status changes (weather alerts, install prompts) use ARIA live regions. |
Known Gaps and Honest Caveats
Out-of-scope surfaces. The authenticated operator console (/ops), the internal module sandboxes, and the live geospatial map components are pre-pilot engineering surfaces. Their accessibility is not asserted in this report. Conformance commitments for those surfaces will be scoped per pilot engagement and documented per sponsor requirement.
Leaflet map markers. Where map components are embedded in marketing surfaces, individual map markers do not yet expose an accessible name to assistive technology. A textual list of marker data is provided alongside each map for screen-reader users; full marker-level accessibility is an open engineering item.
PDF artifacts. Capability-statement PDFs and whitepaper exports are not yet tagged for full PDF/UA conformance. The HTML equivalent of every PDF artifact is linked from the same page, and the HTML version is the canonical accessible source.
Inline charts and stat grids. Performance and module-count stat cards convey information through both color and numeric text. Sparkline charts are decorative, with the underlying data presented as text adjacent to the chart.
Testing Methods Used
- Manual keyboard-only navigation through every in-scope page (Tab, Shift+Tab, Enter, Space, Escape).
- Manual screen-reader spot-checks: NVDA 2024.x on Firefox (Windows) and VoiceOver on Safari (macOS).
- Color-contrast measurement against WCAG 2.1 thresholds (4.5:1 body text; 3:1 large text and non-text contrast).
- Browser-based zoom verification at 200% without two-dimensional scrolling.
- Reduced-motion preference verification (
prefers-reduced-motion: reduce). - HTML validation and duplicate-ID checks on every in-scope page.
How to Report an Accessibility Issue
Accessibility Contact
If you encounter an accessibility barrier on any SHIELD/ATLAS surface, please contact us. We will respond within five business days and work with you to provide an accessible alternative or to remediate the issue.
Email: terry@secureassure.app
Subject line: "Accessibility — [page or surface]"
Please include: the page URL, the assistive technology you are using (if any), and a brief description of the barrier.
This contact is monitored by ISS LLC's principal directly.
Document Control
This VPAT is a self-assessment by ISS LLC. It is not a third-party audit. The canonical machine-readable capability statement (which authorities ISS LLC does and does not hold) is at /api/capability-brief. ISS LLC does not currently hold FedRAMP, IL-5, FIPS 140, CAC, ATO, or CMMC Level 2 third-party authorities; SDVOSB designation is pending.
Integrated Services and Solutions LLC (ISS LLC) · SDVOSB-pending · CAGE 9VKK3 · UEI C7YDV3P8EHL7 · Texas registered · Report v1.0, May 2026