Accessibility

Last reviewed 8 September 2026.

Our target

ChannelzIQ aims to meet WCAG 2.2 Level AA. That is the standard we hold ourselves to across the marketing site, the Creator Studio and the admin console, and it is the standard we measure against when we say something does or does not conform.

What conforms today

• Every form control on this marketing site has an accessible name, so a screen reader announces what each field is for. Placeholders are a hint, not a label — they disappear the moment you start typing — so they are no longer doing that job alone.
• Body text on this site measures 16.26:1 against its background and muted text 5.87:1, both comfortably past the 4.5:1 AA floor.
• Colours that did not pass as text — our amber accent at 2.02:1, teal at 2.49:1, green at 3.36:1 and red at 3.76:1 — are now restricted to borders, fills and icons. Text uses darker variants that were computed, not eyeballed, and each clears 4.5:1.
• Loading states describe the shape of what is arriving rather than showing a bare spinner, and are marked aria-busy.
• Every page — this site, the blog, the sign-in page, the Creator Studio and the admin console — starts with a “Skip to main content” link that appears on the first Tab press and moves focus into the main content (2.4.1 Bypass Blocks).
• Every clickable row, card, chip and thumbnail in the Creator Studio and the admin console is reachable with the keyboard and activates on Enter or Space; overlays close on Escape (2.1.1 Keyboard). 170 such controls were mouse-only on 8 September 2026 and a blocking check now prevents a new one.
• The admin console’s secondary text measures 5.87:1 (it was 3.89:1), and warning, success, danger and info text use dedicated darker tokens that each clear 4.5:1; the warning fill colour is no longer the same amber as our accent, so a warning cannot be mistaken for an upgrade prompt.

WCAG 2.2 criteria we have not yet verified

WCAG 2.2 added nine success criteria and withdrew 4.1.1 Parsing. Of the new AA criteria, these are the ones we have not yet confirmed and say so rather than imply:

• 2.4.11 Focus Not Obscured (Minimum) — sticky headers and bars may cover a focused control in some views; not yet audited.
• 2.5.7 Dragging Movements — dragging a calendar item to another day, and placing a tag on an Instagram photo, have no keyboard alternative yet. Both surfaces are declared pointer-only and announce that.
• 2.5.8 Target Size (Minimum) — some close buttons and colour swatches are under 24×24 pixels.
• 3.2.6 Consistent Help — the position of the help link is not yet consistent across every page.
• 3.3.7 Redundant Entry — the invitation form pre-fills your e-mail; the studio has not been checked for repeated entry.
• 3.3.8 Accessible Authentication (Minimum) — sign-in is an e-mailed code that can be pasted, which we believe passes, but it has not been audited.

What does not conform yet

We would rather tell you what is broken than imply everything works.

• The signed-in Creator Studio and admin console have a large number of controls without accessible names. Both are single-page apps that build most of their interface in JavaScript, and that markup has not yet had the sweep the marketing site has had. A blocking check now stops new ones being added, and the existing set is being worked through.
• Heading levels skip in places — a page may go from a level-2 heading to a level-4 — which makes navigating by headings less predictable than it should be.
• We have not yet completed a full audit with assistive technology in the hands of people who rely on it. Automated checks catch a floor, not a ceiling.

Telling us about a problem

If any part of ChannelzIQ is difficult or impossible for you to use, please email support@channelziq.com with the page and what happened. Access problems are treated as defects, not feature requests, and you do not need to be a customer to report one.

If you need information that is currently only available through an inaccessible part of the product, say so in that email and we will get it to you another way.