WEPPcloud
UserSummary Docs

← Back to usersum index

Accessibility Statement

Last updated: April 1, 2026

This statement describes WEPPcloud's current accessibility posture for users and federal buyers. It is a public-facing summary and does not replace the product's formal Accessibility Conformance Report (ACR/VPAT).

Commitment

WEPPcloud is developed and tested with accessibility as a product requirement. For core user journeys, the engineering target is WCAG 2.1 AA. For U.S. federal procurement, WEPPcloud is being evaluated against the Revised Section 508 standards, which incorporate WCAG 2.0 Level A and AA requirements for applicable web content.

Current Accessibility Features

  • Keyboard-operable controls across primary run and report flows
  • Accessible names for interactive controls and modal/dialog content
  • Focus visibility and keyboard navigation coverage in controller-level tests
  • Screen-reader-oriented status announcements using live regions on supported workflows
  • Rendered contrast validation for the AA-validated theme set
  • 200% zoom and reflow checks in manual accessibility review
  • Public and authenticated smoke testing with axe on representative pages

Theme Options

WEPPcloud provides multiple interface themes because user needs differ.

  • Themes marked AA checked are part of the validated accessibility set and are the recommended choices for users and buyers who need WCAG AA-aligned operation.
  • Themes marked Sensory preference remain available for users who prefer lower-stimulation palettes or alternate visual presentation. These themes are not included in the AA conformance set and should not be selected when strict WCAG AA operation is required.

Known Limitations

  • Some optional sensory-preference themes do not meet the same contrast requirements as the AA-validated theme set.
  • A formal product-specific ACR/VPAT is maintained separately for federal procurement and release governance.

Feedback and Alternate Access

If you encounter an accessibility barrier, need an alternate format, or want current accessibility evidence or procurement documentation, contact:

When reporting an issue, include:

  • the page or workflow where the problem occurred
  • the browser, operating system, and any assistive technology you were using
  • the date and time of the issue
  • a short description of what you were trying to do

Procurement Note

Federal buyers should treat this page as a user-facing accessibility summary only. The formal procurement artifact remains the product-specific Accessibility Conformance Report (ACR/VPAT), which is maintained separately from this statement.