Accessibility Statement
Last updated: September 20, 2026
Our commitment
We build software for a living, and we hold our own site to the standard we ask clients to meet. This site is built so that people using keyboards, screen readers, magnification, and reduced-motion settings can read our content and contact us.
Conformance target
We use Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our design and testing target. This is a target, not a claim that every page has been fully evaluated for conformance. Automated checks run on every change, and we supplement them with manual evaluation.
Measures we take
- Semantic HTML with native controls to improve compatibility with assistive technology.
- Visible focus styles for interactive elements and a skip link to main content.
- Text and interface contrast measured against the WCAG 2.2 AA thresholds.
- Layouts that reflow to a 320 pixel viewport and remain usable at 200 percent zoom.
- Motion that respects the operating-system reduced-motion preference.
- Automated axe-core testing in our build pipeline, which blocks a change from merging on serious issues.
Known limitations
We have not completed our planned manual testing with VoiceOver and NVDA. The automated, keyboard, reflow, zoom, reduced-motion, and forced-colors checks completed so far have not identified a specific barrier, but those checks cannot find every accessibility problem. We will update this statement when additional testing or user feedback identifies an issue.
Reporting a barrier
If any part of this site blocks you, tell us at contact@fusionfueled.com and describe what you were trying to do. We aim to acknowledge reports within five business days.
Alternate means of access
If the contact form does not work for you, email us directly at contact@fusionfueled.com. We will provide the information or service you need through another channel, including by phone or in another format on request.
Assessment approach
This statement reflects self-assessment by Fusion Fueled, LLC using automated tooling and manual checks. It has not been evaluated by an independent third party, and the planned manual screen-reader testing described above is not yet complete.