Accessibility statement
iUtils Social is built to be usable by everyone who works at an agency and by the clients who review its work — including people who use a screen reader, a keyboard alone, magnification, or high-contrast settings.
The standard
We work to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. That is the target for every page a customer or a client sees; we do not claim full conformance, and the section on known limitations below is where the gap is stated.
How it is tested
An automated accessibility engine (axe-core) runs in a real browser against the built product on every change, and a critical or serious finding fails the build. Since September 13, 2026 the scan also fails on insufficient colour contrast; before that, contrast was exempted while two failures inside a shared component were fixed.
- The public pages: home, pricing, contact, the trust pages, the help centre, sign-in and registration.
- Every signed-in page an agency works in, populated with content rather than empty, so tables and lists are actually checked.
- The client approval portal, at full strength in every case, because it is used by people who did not choose this software.
- Public SmartLink pages in every theme preset and background, with a deliberately awkward brand colour.
Automated checks find roughly a third of accessibility problems. The rest — keyboard order, focus visibility, whether an announcement makes sense — is checked by hand when a surface changes, and is where we most need to hear from you.
Known limitations
- The automated scan covers the critical and serious severities. Moderate and minor findings are tracked in a backlog in the repository rather than blocking a release.
- Some pages reachable only through a specific record — a single campaign, a single media asset — are scanned by their own seeded tests rather than the general sweep, so a new page of that kind can ship before its test is written.
- Charts on the analytics pages are not navigable by keyboard and are not described to a screen reader beyond their legend. The underlying numbers are available as a CSV export from the reports page.
- PDF reports are generated from the same templates as the web reports but have not been assessed with a screen reader.
- Content published to a connected network is presented by that network under its own accessibility practices; alt text you add in the composer is sent where the network accepts it.
Tell us
If something is hard or impossible to use with the assistive technology you rely on, we want to know — say which page, what you were trying to do and what you use, and we will treat it as a defect rather than a request. [email protected]