Legal · accessibility
Accessibility statement.
Stagg Business Solutions is committed to making stagg-solutions.com usable by the widest possible audience — keyboard, screen reader, magnifier, and reduced-motion users alike. This statement explains the standard we target, what we do to meet it, and how to tell us when we fall short.
Target WCAG 2.1 Level AA · Last reviewed May 19, 2026 · [email protected] · Response SLA 5 business days
01. Our commitment
Accessibility is part of how we build, not a finish-line check. We treat accessibility defects the same as functional defects: they get a ticket, they get a fix, and they get verified before the fix is closed.
02. Standard we target
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. Where Section 508 of the US Rehabilitation Act applies to federal-facing material, we additionally align with the 2017 Section 508 ICT Refresh, which incorporates WCAG 2.0 AA by reference.
03. Practices in place
- Semantic HTML — pages use real header, nav, main, section, article, and footer landmarks. Headings follow a logical order.
- Keyboard navigation — every interactive element is reachable with Tab and operable with Enter or Space. Focus order matches reading order.
- Visible focus — focusable elements show a clear focus indicator that meets the WCAG 2.4.11 contrast and area requirements.
- Color contrast — body text meets at least 4.5:1 against its background; large text and UI components meet at least 3:1.
- Text alternatives — images convey their purpose through descriptive alt text. Decorative images use empty alt text so screen readers skip them.
- Forms — every input has a programmatically associated label. Required fields are announced. Errors are described in text, not by color alone.
- Reduced motion — animations respect the prefers-reduced-motion media query. If your system requests reduced motion, transitions are minimized or removed.
- Skip link — a "skip to content" link is the first focusable item on every page.
- Resizable text — pages remain usable at 200% zoom without loss of content or function. No fixed pixel font sizes on body text.
- No content traps — modals can be dismissed by keyboard. We do not use auto-playing audio or hijack the scroll.
04. Assistive technology support
We test pages with the combinations our customers most commonly use:
- Chrome and Firefox on Windows, with NVDA and JAWS.
- Safari on macOS and iOS, with VoiceOver.
- Chrome and Firefox on Linux, with Orca.
- Keyboard-only navigation across all of the above.
If you use a different combination and the site does not work for you, please tell us.
05. Known issues
We are honest about where we are not yet meeting our own bar. Current open items:
- Decorative photography — a small number of background images do not yet carry a descriptive label for screen readers in the rare cases where the image carries meaning beyond decoration. Tracked and scheduled.
- Mobile navigation focus return — when the mobile menu is closed via the toggle button, focus could return more reliably to the toggle in certain browser versions. Under investigation.
If you encounter something not listed here, please report it — see section 07.
06. Third-party content
The website embeds Google Fonts as a typography source. Google's font delivery is generally accessibility-friendly, but its underlying implementation is outside our direct control. We do not embed any other third-party widgets, players, chat tools, or social-media frames on this site.
07. Report a barrier
If something on this site is not usable for you, please tell us. Include:
- The URL of the page.
- A short description of what you were trying to do.
- Your browser, operating system, and assistive technology if applicable.
- Whether you would like us to follow up with a workaround in the meantime.
Send the report to [email protected]. If email is itself a barrier, you may call (801) 917-4617.
08. How we handle reports
- Within 5 business days — we acknowledge receipt and confirm whether we can reproduce the issue.
- Within 15 business days — we provide either a fix or a written explanation of the workaround and a target date for the permanent fix.
- Critical barriers (something that blocks all access for a class of user) get same-day triage and a 48-hour mitigation target.
09. Formal complaints
If you believe we have not adequately addressed an accessibility concern, US visitors may file a complaint with the US Department of Justice under Title III of the Americans with Disabilities Act, or with the Architectural and Transportation Barriers Compliance Board under Section 508 (for federal-facing material). EU/UK visitors may contact the supervisory authority for digital accessibility in their member state. We would prefer the chance to fix the issue first — please write to [email protected] before escalating.
10. Updates
This statement is reviewed at minimum every 12 months, after any significant redesign, and whenever a new WCAG version becomes a recommended target. The last review date is shown at the top of this document.