Skip to main content

Last updated: August 24, 2026

Accessibility Statement

StackShield is committed to ensuring digital accessibility for all users, including people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

Conformance status

We aim for WCAG 2.1 Level AA conformance across the StackShield web application. We recognize that accessibility is an ongoing effort and are actively working to address any areas where we fall short.

What we've done

  • Semantic HTML — All pages use proper heading hierarchy, landmark regions (header, main, footer), and meaningful element names.
  • Form labels — Every form input has an associated label or visible description. Required fields are marked.
  • Keyboard navigation — All interactive elements (buttons, links, form inputs, dialogs) are reachable and operable via keyboard alone. Focus indicators are visible.
  • Color contrast — Text and interactive elements meet or exceed the 4.5:1 contrast ratio for normal text and 3:1 for large text.
  • Screen reader support — ARIA labels and roles are used where native HTML semantics are insufficient. Status messages and loading states are announced to assistive technologies.
  • Error identification — Form validation errors are clearly described in text and associated with the relevant input field.
  • Responsive design — The application is usable across viewport sizes from 320px to 2560px+.

Known limitations

We are aware of the following areas where accessibility can be improved:

  • Terminal-style scan output — The live scan terminal uses a monospace scrolling log. We provide a summary view alongside it for users who cannot parse the raw terminal output.
  • Third-party content — Some pages link to external services (Supabase, GitHub, Vercel) whose accessibility we do not control.
  • Animated transitions — Page transitions use motion. Users who prefer reduced motion can enable the prefers-reduced-motion system setting, which we respect.

Testing approach

We test accessibility using:

  • Manual keyboard-only navigation testing
  • axe DevTools automated scanning
  • WAVE Web Accessibility Evaluation Tool
  • Browser zoom testing up to 200%
  • Screen reader testing (VoiceOver on macOS)

Feedback

We welcome your feedback on the accessibility of StackShield. If you encounter an accessibility barrier or have suggestions for improvement, please contact us at contact@stackshield.org. We take all accessibility reports seriously and aim to respond within 5 business days.

Enforcement

If you are not satisfied with our response, you have the right to escalate your concern. Depending on your jurisdiction, you may contact your national accessibility enforcement body. We are committed to working with you to resolve any issues.