Accessibility
We build to WCAG 2.2 AA as a baseline and treat accessibility defects as functional defects rather than enhancements.
What we have implemented
Semantic landmark structure, a skip link to the main content, visible keyboard focus, accessible names on interactive controls, and disclosure and tab patterns implemented with the appropriate ARIA relationships.
Every scroll-driven or hover-driven interaction has a keyboard and touch equivalent, and no information is conveyed by motion or colour alone.
Reduced motion
If your device requests reduced motion, animation is switched off across the site: momentum scrolling is disabled, marquees become static, scroll-linked movement is removed and transitions resolve immediately.
Known limitations
The horizontally scrolling process section relies on a native scroll container on small screens; it is reachable by keyboard and by touch, but a visitor using a screen magnifier at very high zoom may prefer the vertical stacking that appears below 1024 pixels.
Questions about this page can be sent to boost@iboost365.com and we will respond within one working day.