Accessibility Statement

Effective: May 30, 2026 · Operator: PCS Express, operated by CyberWave Technologies LLC (cyberwaveglobal.com) · Contact: info@cyberwaveglobal.com

1. Our commitment

PCS Express is built to be usable by service members, DoD civilians, and military families with the broadest possible range of abilities and assistive technologies. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and we treat U.S. Section 508 (Revised 508) and EN 301 549 conformance as the same target.

2. What we have done

Semantic HTML across the app — <main>, <nav>, <aside>, <header>, <h1>–<h3> in hierarchy.
WCAG-conformant tab pattern (role="tab" + aria-selected + aria-controls + paired role="tabpanel" + aria-labelledby) on every navigable tab strip in the app.
Keyboard reachability — every interactive control is a real <button> or <a>, focusable with Tab.
Focus traps on modal dialogs (navigation drawer, AI Assistant, Security & Data Handling) so screen-reader users can't accidentally focus content underneath an open dialog.
.sr-only utility class used to surface page-level landmarks to screen readers without visual clutter.
Reduced-motion compatible (no auto-playing animations that violate prefers-reduced-motion: reduce).
Form labels — every input in the onboarding flow has an associated <label htmlFor>.
RTL support — the entire shell flips direction when the user picks Arabic.

3. Known issues (in active remediation)

The most recent internal accessibility audit (axe-core) surfaced the following open issues. We list them here so users know what to expect and so we are accountable for fixing them.

Skip link tab order. The "Skip to main content" link exists in the DOM but is not the first tabbable element on every screen — the autosave-status chip sometimes precedes it. Targeted fix in progress.
Horizontal tab strips on mobile clip without a visible scroll affordance on a few mission groups; users can swipe but the affordance is missing. Adding a fade gradient + chevron is queued.
Resolved (2026‑05): low-contrast muted text raised to meet 4.5:1, form inputs given accessible names (aria-label/associated labels), and a mis-used role="tab" on action buttons removed.

4. Compatibility

PCS Express is tested with:

VoiceOver on iOS (Safari, embedded WebView in the iOS app)
TalkBack on Android (Chrome, embedded WebView in the Android app)
VoiceOver on macOS (Safari, Chrome)
NVDA + Narrator on Windows (Chrome, Edge, Firefox)
Keyboard-only operation (no mouse) across the desktop layout

If you use an assistive technology not listed above and run into a barrier, please tell us — we may not have caught it.

5. Report a barrier

Email info@cyberwaveglobal.com with:

The page or screen where the issue occurred (the URL or the tab name)
What you were trying to do
What happened (or didn't happen)
The assistive technology, browser, and operating system you were using

We aim to acknowledge accessibility reports within 5 business days and target a fix in the next release cycle when feasible. There is no charge to use any feature of PCS Express; there is also no charge to request accommodation.

6. Standards we target

W3C WCAG 2.1 Level AA
U.S. Revised Section 508 (ICT Refresh)
EN 301 549 (EU)

These targets are engineering best-effort. PCS Express does not hold a formal third-party conformance certificate.