ACCESSIBILITY STATEMENT

Blitz Industries, Inc. ("Blitzify") is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying relevant accessibility standards to our website and AI workforce platform.

We believe that everyone, regardless of ability, should be able to access information about our products and services without barriers. Accessibility is not an afterthought; it is a design principle built into our development process.

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. WCAG 2.2 defines three conformance levels: Level A, Level AA, and Level AAA.

Target conformance: WCAG 2.2 Level AA

Current status:Blitzify has been remediated toward WCAG 2.2 Level AA and currently passes the automated accessibility checks described below. An automated audit using axe-core 4.10.0 (rule sets: WCAG 2.0 A/AA, WCAG 2.1 AA, WCAG 2.2 AA, and best-practice) was run against all thirteen public routes in August 2026 in a Chromium browser at 1280×924 in an unauthenticated state, returning zero detected violations. Automated tools cannot test every accessibility requirement. Accessibility is an ongoing effort, and some criteria, including screen-reader reading order, keyboard interaction for complex disclosures, zoom and reflow, and assistive-technology compatibility, require continued manual and assistive-technology testing that has not yet been completed.

This statement was last reviewed in August 2026 based on a self-assessment of the blitzify.ai website.

Blitzify takes the following measures to ensure accessibility of our website and platform:

• Include accessibility as a requirement in our product and design specifications.
• Conduct self-assessments using automated testing tools and ongoing manual review.
• Provide a mechanism for users to report accessibility issues (see Section 06).
• Assign clear ownership of accessibility remediation to engineering and design teams.
• Use semantic HTML5 elements and ARIA roles to communicate structure and state to assistive technologies.
• Ensure all interactive elements are keyboard-operable and have visible focus indicators.
• Include a skip navigation link to allow keyboard users to bypass repeated navigation.
• Respect the prefers-reduced-motion operating system setting to suppress non-essential animations.
• Avoid disabling user zoom and scaling in the browser viewport.
• Provide accessible names for all form controls, images, and icon-only buttons.
• Mark required form fields with both a visual and programmatic indicator.
• Announce form validation errors and status changes to screen readers using aria-live regions.

The automated audit returned zero violations, but automated tools do not cover every WCAG 2.2 success criterion. The following items require manual or assistive-technology testing that has not yet been completed:

• Screen-reader compatibility: Full end-to-end testing with VoiceOver (macOS/iOS), NVDA (Windows), JAWS (Windows), and TalkBack (Android) has not been completed. Reading order, live-region announcements, and custom widget behavior have not been verified with assistive technology.
• Keyboard interaction for complex widgets: The navigation mega-menu, accordion disclosures, and multi-step request form have not been verified by keyboard-only testing across all supported browsers.
• Zoom and reflow: Content behavior at 200% and 400% browser zoom and single-column reflow at 320 CSS pixels width has not been formally verified.
• Form error announcements: Live-region announcement of validation errors and submission status messages has not been confirmed with a screen reader.
• Mission Replay and orbital diagram visualizations: These panels contain animated or canvas-based content. Text equivalents are present in surrounding copy and the visuals are marked aria-hidden="true", but screen-reader equivalence has not been verified with assistive technology.
• Reduced-motion behavior: prefers-reduced-motion: reduce CSS rules are in place; manual verification that no meaningful content is lost when animations are suppressed has not been completed.
• Mobile assistive-technology testing: Touch target sizing and TalkBack / VoiceOver on iOS interaction have not been verified.

Please report any barrier you encounter at hello@blitzify.ai or (812) 362-5489. We will investigate and respond within 5 business days.

Accessibility of the Blitzify website relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML5
• WAI-ARIA 1.2
• CSS
• JavaScript (React 19, Next.js 16)

These technologies are relied upon for the accessibility features implemented.

Automated assessment environment:

• Tool: axe-core 4.10.0
• Browser: Chromium (headless agent-browser, desktop mode)
• Viewport: 1280×924
• Authentication state: unauthenticated (public pages only)
• Rule sets: wcag2a, wcag2aa, wcag21aa, wcag22aa, best-practice
• Date: August 2026
• Routes tested: 13 public pages (see Section 02)
• Interactive states opened: static page load only, dynamic menus, dialogs, accordions, and form error states were not opened during automated testing

Assistive-technology testing: Formal testing with screen readers (VoiceOver, NVDA, JAWS, TalkBack) and keyboard-only navigation has not yet been completed. See Section 04 for the full list of outstanding manual checks.

We welcome your feedback on the accessibility of the Blitzify website. Please let us know if you encounter accessibility barriers:

• Email: hello@blitzify.ai
• Phone: (812) 362-5489
• Contact form: blitzify.ai/contact, reference accessibility in your message.

We try to respond to feedback within 5 business days. If you are not satisfied with our response, you may contact the relevant authority in your jurisdiction. In the United States, the relevant authority is the U.S. Department of Justice. In the European Union, please contact the supervisory authority in your member state.

If you are not satisfied with our response to your accessibility feedback, you may escalate to the relevant enforcement body:

• United States: The Americans with Disabilities Act (ADA) prohibits discrimination on the basis of disability in places of public accommodation. The U.S. Department of Justice enforces Title III of the ADA. You may file a complaint at ada.gov.
• European Union: The European Accessibility Act (EAA) and Web Accessibility Directive may apply to certain services. Contact the relevant market surveillance authority in your member state.
• United Kingdom: The Equality Act 2010 applies. Contact the Equality and Human Rights Commission (EHRC) for guidance.

You also have the right to contact the relevant supervisory or enforcement body in your jurisdiction if you believe we have not adequately addressed your accessibility concern. We encourage you to contact us first so we have an opportunity to resolve the issue directly and promptly.

This statement was last reviewed and updated in August 2026.