Accessibility
Frontsiter's accessibility goal, what is in place, and how to report a problem.
Our goal
Frontsiter aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We build accessibility into the design and the code from the start, instead of checking for it at the end.
What is in place
- Contrast. All text meets the WCAG 2.2 contrast levels: at least 4.5:1 for normal text, and at least 3:1 for large text and for buttons and other controls.
- Keyboard. You can use every link and control with a keyboard, and the item in focus always has a visible outline.
- Skip link. A "Skip to content" link at the top of each page lets you jump past the header.
- Structure. Pages use headings in order, landmarks such as header, main, and footer, and real tables, so screen readers can move through them.
- Color is never the only signal. Links in text are underlined, and status messages use an icon and words, not only a color.
- Reduced motion. If your device is set to reduce motion, animations and smooth scrolling are turned off.
How we test
We test pages with automated accessibility checks (axe-core, run through Google Lighthouse). The latest check, on 11 October 2026, covered all main pages and found no issues. Automated checks cannot find every problem, so if you find one, please tell us.
Known issues
We do not know of any accessibility issues at the moment. When we find one, we will list it here with our plan to fix it.
Report a problem
If something on Frontsiter is hard to use with your device or assistive technology, email hello@frontsiter.com. Tell us which page it is, what you tried to do, and which browser or assistive technology you use. We read every message.
