Web Accessibility Report WCAG 2.2 AA · Q2–Q3 2026 · Prepared for external audit
Where SalesIQ stands on accessibility today, the strengths already in place, and a prioritized roadmap for the rest. Hover any tag or ⓘ for a plain-language explanation.
01 In place today
What SalesIQ already gets right
Accessibility strengths confirmed in the shipping product. Hover a criterion tag for what it means and what's expected.
Keyboard & visible focus
Operable end to end by keyboard, with a clear, visible focus indicator as you move through the console.
SC 2.1.12.1.1 · KeyboardWhat: every action works with a keyboard, no mouse needed.Expected: nothing is mouse-only.Here: in place, passed the keyboard review.SC 2.4.72.4.7 · Focus VisibleWhat: you can see which element is selected.Expected: a clear focus indicator while tabbing.Here: in place.
Comfortable color contrast
Text sits roughly four times above the readable minimum, see the ratios below.
SC 1.4.31.4.3 · Contrast (Minimum)What: text stands out clearly from its background.Expected: at least a 4.5:1 ratio for body text.Here: in place, around 18–21:1.
Readable typography
An accessible type family and sizing; text enlarges past 200% without breaking the layout.
SC 1.4.41.4.4 · Resize TextWhat: text can be made larger.Expected: readable at 200% without losing content.Here: in place.SC 1.4.121.4.12 · Text SpacingWhat: line and letter spacing can be increased.Expected: text stays readable, nothing clipped.Here: in place.
Descriptive labeling
Well over a hundred interactive elements carry meaningful names, many reflecting live context.
SC 1.3.11.3.1 · Info & RelationshipsWhat: on-screen structure reaches screen readers.Expected: labels and groupings are programmatic, not visual only.Here: in place.SC 4.1.24.1.2 · Name, Role, ValueWhat: each control announces what it is and does.Expected: a valid name, role, and state.Here: labeling in place; role refinement on the roadmap.
Color contrast, measured How to read thisEach bar shows the ratio between text and its background. Longer is easier to read.Expected: at least 4.5:1 (the marked line).
Passes AA & AAAThe 4.5:1 AA minimum sits near the far left, every text combination clears it comfortably.
02 By user need
What SalesIQ provides, by disability
The same work, seen through the people it serves. Hover any ⓘ for a simple example.
For users with low vision, larger text, strong contrast, reliable zoom.
Readable typography & zoomExampleA user zooms the chat to 200% to read it, text stays sharp and nothing is cut off.
Accessible type and sizing; content enlarges cleanly.
Comfortable contrastExampleDark text on light panels stays easy to read, even in bright daylight.
Text sits well above the readable minimum.
High-zoom layout confirmationWhat's nextChecking that panels don't overlap or clip when zoomed all the way in.
A final reflow check at high zoom.
For blind users navigating entirely by screen reader.
Descriptive, context-aware labelsExampleThe screen reader says “Response overdue” instead of just “icon”.
Elements carry meaningful names, many reflecting live state.
Semantic structureExampleA button is announced as “button”, not read as a blank image.
Roles convey meaning; decorative parts are hidden.
Role & name refinementWhat's nextMaking sure every label is attached to a real control so nothing is skipped.
Ensuring every label sits on a valid element.
Alt text, language & announcementsExampleA new chat message is read out automatically as it arrives.
Rounding out alternatives and live updates.
For users operating by keyboard or assistive input.
Keyboard operabilityExampleTab and arrow keys move through the whole console, no mouse required.
The console works end to end by keyboard.
Visible focus indicatorExampleA clear outline shows exactly where you are as you tab.
A clear, consistent outline follows keyboard focus across controls.
Dialog focus handlingWhat's nextFocus jumps into a dialog when it opens and returns when it closes.
Predictable focus in and out of dialogs.
For users with cognitive or reading needs, clarity and consistency.
Readable, helpful interfaceExampleA hint explains what an action does before you commit to it.
Clear type and supportive hints reduce effort.
Consistent navigationExampleMenus and tabs stay in the same place from screen to screen.
Familiar patterns across the console.
Clear error recoveryExample“Enter a valid email” instead of just a red box.
Accessible, well-described form errors.
In placeOn the roadmap
03 Ahead
Roadmap
The work planned next, grouped by theme, with a target quarter.
Accessibility Module
One in-product hub where each user can tune SalesIQ to their needs.
Low vision
- Text size & zoom
- High-contrast theme
- Comfortable spacing
- Font choice
Screen reader
- Announcement detail
- Live-update alerts
- Landmark shortcuts
Motor
- Keyboard shortcuts
- Larger targets
- Reduced motion
- Sticky focus
Cognitive
- Simplified / focus mode
- Fewer distractions
- Plain-language hints
- Reading guide
Q3 2026Near term
Labeling & semantics refinementSC 4.1.24.1.2 · Name, Role, ValueWhat: controls announce what they are and do.Expected: a valid name, role, and state on every control.Planned: refine roles; publish accessible component specs.
Refine roles so every control is announced correctly; reusable component specs.
Images, forms & page languageSC 1.1.11.1.1 · Non-text ContentWhat: images have text alternatives.Expected: meaningful alt text for informative images.Planned: complete alternatives, labels, and page language.
Round out alternative text, form labels, and the page-language declaration.
Q4 2026Hardening & automation
Screen reader optimizationSC 1.3.11.3.1 · Info & RelationshipsWhat: structure and updates reach assistive tech.Expected: landmarks, dialogs, and announcements work.Planned: optimize for dynamic content.
Landmarks, dialog behavior, and announcements for dynamic chat content.
Automated testing & regression
Accessibility checks in the release process, run every release.
Remaining manual assessments
Completing assessment of the remaining WCAG categories (see overview).
04 Full overview
Coverage across every WCAG category
The complete assessment framework at a glance, in place, on the roadmap, or not applicable. Hover any ⓘ for what the category checks.
KeyboardKeyboardEverything works with a keyboard alone.In place.In place
ContrastContrastText stands out enough to read easily.In place.In place
Typography & textTypography & textReadable fonts and sizes; text can be enlarged.In place.In place
Labels & semanticsLabels & semanticsControls tell assistive tech what they are.In place; refinement ahead.In place
FocusFocusYou can see and follow keyboard focus.In place, a visible focus indicator.In place
LandmarksLandmarksRegions like header, nav, and main are marked for quick jumping.On the roadmap.Roadmap
HeadingsHeadingsA logical heading outline to navigate by.On the roadmap.Roadmap
Links & navigationLinks & navigationClear link text and consistent ways to move around.On the roadmap.Roadmap
ImagesImagesInformative images have text alternatives.On the roadmap.Roadmap
Forms & errorsForms & errorsLabelled fields and clear, spoken error messages.On the roadmap.Roadmap
Widgets & dialogsWidgets & dialogsCustom controls and dialogs behave for assistive tech.On the roadmap.Roadmap
LanguageLanguageThe page states its language so it's pronounced correctly.On the roadmap.Roadmap
Adaptable contentAdaptable contentContent adapts to different sizes and orientations.On the roadmap.Roadmap
Sensory & pointerSensory & pointerNot relying on color, shape, or complex gestures alone.On the roadmap.Roadmap
CognitiveCognitiveClear, forgiving, low-effort interactions.On the roadmap.Roadmap
Timed eventsTimed eventsEnough time; no surprise timeouts.On the roadmap.Roadmap
Repetitive contentRepetitive contentSkip links past repeated blocks.On the roadmap.Roadmap
ParsingParsingValid markup for assistive tech.Not applicable, retired in WCAG 2.2.N/A
Audio / videoAudio / videoCaptions and alternatives for media.Not applicable, the console has no media.N/A
MultimediaMultimediaSynchronized media alternatives.Not applicable, no media.N/A
In placeOn the roadmapNot applicable
05 Sustainable practice
Accessibility in the design process
In product reviews
Considered from requirements through design review and handoff.
Tracked to closure
Findings are logged, prioritized, owned, and followed through.
Review checklist
Every design review runs a shared accessibility checklist.
Awareness & trainingAwareness & trainingThe team knows accessibility basics and how to apply them in design.Established
Design-review integrationDesign-review integrationAccessibility is checked as a normal part of every design review.Established
Accessibility trackingAccessibility trackingIssues are logged with an owner and tracked until they're resolved.Established
Design-system accessibilityDesign-system accessibilityShared components carry accessibility built in, so it's right by default.Developing.Developing
Automated validation & monitoringAutomated validation & monitoringAutomated accessibility checks in the release pipeline, run continuously.Planned.Planned
06 Appendix
WCAG 2.2 AA, complete criteria
Every applicable success criterion mapped to SalesIQ, for the auditor's reference.
| Criterion | What it checks & what's expected | Status |
|---|---|---|
| 1.3.1Info & Relationships | On-screen structure is available to assistive tech, in place. | In place |
| 1.4.3Contrast (Minimum) | Text meets ~4.5:1; SalesIQ runs ~18–21:1, in place. | In place |
| 1.4.4 / 1.4.12Resize & spacing | Text scales to 200%+ and spacing adjusts, in place. | In place |
| 2.1.1Keyboard | Full keyboard operation, passed review, in place. | In place |
| 4.1.2Name, Role, Value | Labeling broadly in place; role validity being refined. | Roadmap |
| 1.1.1Non-text Content | Alt text present on most images; completing the rest. | Roadmap |
| 2.4.7Focus Visible | A clear, consistent focus indicator, in place. | In place |
| 2.4.1 / 2.4.6Landmarks & headings | Skip navigation and a clear heading outline, planned. | Roadmap |
| 3.3.1 / 3.3.3Errors & suggestions | Descriptive, announced form errors, planned. | Roadmap |
| 3.1.1Language of Page | The document language declaration, planned. | Roadmap |
| 1.2.xTime-based media | No audio or video in the console, not applicable. | N/A |
In placeOn the roadmapNot applicable