Built to be usable by everyone — and honest about where we are.
We design SolarFleet to be operable by keyboard, screen reader and on a phone in the field. We aim for WCAG 2.2 AA. We have not been through a formal accessibility audit, and we won't claim a certification we don't hold.
What we've done
These are accessibility measures actually built into the product and marketing site today — not aspirations.
Skip to main content
Every page starts with a keyboard-reachable "Skip to main content" link as the first focusable element. The site navigation sits outside the main landmark, so the link genuinely jumps past it to the page body.
Visible focus ring everywhere
A project-wide focus ring — a 2px ink outline with a lime halo — is applied to every interactive element on keyboard focus, so it stands out on both light and dark backgrounds. It fires on :focus-visible, so the ring shows for keyboard navigation without cluttering mouse clicks.
Respects reduced motion
If your operating system asks for reduced motion (for example iOS Settings → Accessibility → Motion → Reduce Motion), we honour prefers-reduced-motion and effectively switch off animations, transitions and smooth scrolling.
44px minimum tap targets
On touch screens, interactive controls — pagination, filters, menu and close buttons, toasts — are sized to a minimum 44×44px tap target so they're comfortable to hit on a phone in the field.
Semantic HTML and ARIA
We use real headings, landmarks (main, nav, footer) and native controls. Menu and FAQ buttons announce whether they're open (aria-expanded), the homepage product tour uses the ARIA tabs pattern, modals expose role="dialog" with aria-modal and a wired-up accessible label, and sortable tables announce sort state via aria-sort.
Keyboard navigable
The application and marketing site can be operated with a keyboard. Dialogs trap focus while open and return focus to the element that opened them on close. The mobile site menu closes with Escape and takes the page behind it out of the tab order while it's open.
What we're aiming for
WCAG 2.2 AA
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We have not commissioned a formal, independent accessibility audit or conformance assessment, so we describe ourselves as partially conformant: we believe most of the platform meets AA, but some areas may not yet, and we have not had this verified externally.
Known limitations
SolarFleet includes data-dense views — fleet maps, charts and large tables — that are harder to make fully accessible than a simple page. Some inline text links, such as those in the site footer, are smaller than 44px (they're spaced so neighbouring targets don't overlap). We're improving these as we touch them. If you hit a barrier, please tell us; real reports are the fastest way for us to fix the right things.
Report an accessibility issue
Found something that's hard to use with a keyboard, a screen reader, or at your text size of choice? Email hello@solarfleet.io. Tell us the page and what got in your way — we'll get back to you within a working day and treat accessibility fixes as real bugs, not nice-to-haves.
Last updated: October 2026