cometchat-a11y
Ground truth: the UI Kit components are documented as designed targeting WCAG 2.1 Level AA with keyboard navigation built in (the Angular component docs state this most explicitly; note the docs' own caveat that full conformance still requires manual testing — do not assert a blanket AA/VPAT claim to the user without it). Treat AA as the design target, not a certified guarantee. Accessibility failures in a CometChat app are almost always host-side regressions — global CSS, a broken focus order, a container with no accessible name, or motion that ignores the user's preference. Verify component-level a11y claims against the component's own docs page (
cometchat-<family>-components→ docs-map); this skill owns the host-side discipline the kit can't control.
Use this skill when
An accessibility review (WCAG / Section 508 / ADA / EN 301 549), a screen-reader or keyboard complaint, or "make our chat accessible." Procurement for public-sector, education, healthcare and large enterprises requires this.
Start from what the kit gives you
The kit ships accessible components: keyboard-operable lists/composer, focus handling, and semantics designed targeting AA (the design target — not a certified guarantee; see above). On web it sets ARIA roles and names itself — the conversation/user rosters render as a labelled listbox and manage roving focus — so don't override or strip them. Your job is to not break it and to make the surrounding app equally accessible. Two rules first:
- Don't let global CSS leak into the
.cometchatsubtree (web) — a globaloutline:none, a low-contrast override, atext-align/flex reset, or a Tailwind base can strip focus rings or break contrast the kit set correctly. Scope your resets away from the kit (RULES.md→ CSS isolation). - Give the chat container a real, labelled home — a sized region (a11y needs a visible, non-collapsed surface too) with an accessible name (e.g. an
aria-label/landmark on web, an accessibility label on native) so screen-reader users can find and enter it.
The checklist (host-side)
- Keyboard: every path reachable and operable by keyboard — open a conversation, type, send, open thread, close. Don't trap focus; return focus sensibly when a panel/dialog closes. Don't remove focus outlines; if you restyle them, keep a visible focus indicator.
- Screen reader: the surface and its regions have accessible names; your own buttons around the kit have labels (not icon-only with no
aria-label/accessibility label). New-message announcements: verify the kit's live-region behavior on your target reader (VoiceOver/NVDA/TalkBack) and don't suppress it witharia-hiddenon an ancestor. - Contrast: if you theme the kit (
cometchat-<family>-customization), keep text/UI contrast at AA (4.5:1 text, 3:1 large text/UI). Check both light and dark themes — a brand color that passes on light can fail on dark. - Reduced motion: honor
prefers-reduced-motion(web) / the OS "reduce motion" setting (native) in any animation you add around the chat; don't force motion the user opted out of. - Text scaling / zoom: the surface must remain usable at 200% zoom / large Dynamic Type — don't cap font sizes or clip at large text.
- RTL: direction-correct for RTL locales (pairs with
cometchat-i18n). - Targets: your custom controls meet the minimum touch-target size; don't shrink the kit's.