Accessibility Compliance
This page records the accessibility standards Ignite UI for React targets, what each component’s own documentation covers today, and how to report an accessibility problem.
Accessibility support is delivered by two layers — the components themselves and the theming engine that styles them. Use this page to find the status of a specific component; use Theming Accessibility for contrast, text scaling, and chart color behavior.
Scope of this page. The information below reflects the Default theme and the current documented behavior of each component. It is a support summary, not a formal conformance statement. Custom themes, typography changes, and animation or color overrides can change the result.
Standards We Target
| Standard | Region | What it requires |
|---|---|---|
| WCAG 2.1 Level AA | International | The success criteria listed below. The baseline referenced by the other two. |
| Section 508 (Revised) | United States | Federal procurement. Since the Revised Section 508 Standards (published 2017, compliance date January 2018) it incorporates WCAG 2.0 Level AA by reference, so it is satisfied by the same work. |
| EN 301 549 | Europe | The European standard referenced for ICT accessibility, built on WCAG. The European Accessibility Act, which builds on it, applies from 28 June 2025. |
Section 508 previously defined its own 16 rules under §1194.22. Those were superseded by the Revised Standards, which adopt WCAG directly. Targeting WCAG 2.1 Level AA therefore addresses all three frameworks above.
Success criteria that apply to UI components
WCAG conformance is claimed against individual success criteria, not against the broader guidelines. These are the criteria that a UI component library can affect:
| Criterion | Level | What it means for a component |
|---|---|---|
| 1.1.1 Non-text Content | A | Icons and images carry a text alternative. |
| 1.3.1 Info and Relationships | A | Structure conveyed visually is also conveyed in markup. |
| 1.3.2 Meaningful Sequence | A | Reading order matches visual order. |
| 1.4.3 Contrast (Minimum) | AA | Text meets 4.5:1 against its background. |
| 1.4.4 Resize Text | AA | Text scales to 200% without loss of content. |
| 1.4.11 Non-text Contrast | AA | Control boundaries and states meet 3:1. |
| 1.4.13 Content on Hover or Focus | AA | Tooltips and popovers are dismissible and persistent. |
| 2.1.1 Keyboard | A | All functionality is reachable by keyboard. |
| 2.1.2 No Keyboard Trap | A | Focus can always move back out. |
| 2.4.3 Focus Order | A | Tab order follows a meaningful sequence. |
| 2.4.7 Focus Visible | AA | The focused control is visibly indicated. |
| 2.5.3 Label in Name | A | The accessible name contains the visible label. |
| 3.2.1 On Focus | A | Focus alone does not trigger a change of context. |
| 3.2.2 On Input | A | Changing a value alone does not trigger a change of context. |
| 3.3.2 Labels or Instructions | A | Inputs carry labels or instructions. |
| 4.1.2 Name, Role, Value | A | Every control exposes a name, a role, and its current state. |
How Accessibility Is Delivered
| Layer | Responsible for | Where it is documented |
|---|---|---|
Component library (igniteui-angular on Angular) |
Keyboard operability, focus movement, ARIA roles and states, screen-reader announcements. | The index below, and each component topic. |
Theming engine (igniteui-theming) |
Color contrast, text sizing, chart color palettes, styling utilities for custom controls. | Theming Accessibility |
Component Support
This index records what each component’s documentation covers today. Not documented yet means the component’s own documentation does not describe this behavior — it is a statement about the documentation, not about the component.
| Status | Meaning |
|---|---|
| Documented | The behavior is described in the component’s own documentation, linked in the row. |
| Requires configuration | Available once the setting named in Configuration Required is applied. |
| Not documented yet | The component’s documentation does not yet describe this behavior. |
| Component | Keyboard interaction | Screen reader / ARIA | Reference |
|---|---|---|---|
| Grid | Documented | Not documented yet | Keyboard navigation |
| Hierarchical Grid | Documented | Not documented yet | Keyboard navigation |
| Tree Grid | Documented | Not documented yet | Keyboard navigation |
| Tree | Documented | Not documented yet | Keyboard navigation |
| List | Not documented yet | Not documented yet | — |
| Avatar | Documented | Documented | Accessibility |
| Badge | Documented | Documented | Accessibility |
| Banner | Not documented yet | Not documented yet | — |
| Button | Not documented yet | Not documented yet | — |
| Button Group | Not documented yet | Not documented yet | — |
| Calendar | Documented | Not documented yet | Keyboard navigation |
| Card | Not documented yet | Not documented yet | — |
| Carousel | Documented | Documented | Accessibility |
| Checkbox | Not documented yet | Not documented yet | — |
| Chip | Not documented yet | Not documented yet | — |
| Circular Progress | Not documented yet | Not documented yet | — |
| Combo | Documented | Not documented yet | Keyboard navigation |
| Date Time Input | Documented | Not documented yet | Keyboard navigation |
| Date Picker | Documented | Not documented yet | Keyboard navigation |
| Dialog | Not documented yet | Not documented yet | — |
| Divider | Not documented yet | Not documented yet | — |
| Dock Manager | Documented | Not documented yet | Keyboard navigation |
| Dropdown | Not documented yet | Not documented yet | — |
| Expansion Panel | Documented | Not documented yet | Keyboard navigation |
| Icon | Not documented yet | Not documented yet | — |
| Icon Button | Not documented yet | Not documented yet | — |
| Input | Not documented yet | Not documented yet | — |
| Linear Progress | Not documented yet | Not documented yet | — |
| Navbar | Not documented yet | Not documented yet | — |
| Navigation Drawer | Not documented yet | Not documented yet | — |
| Radio | Not documented yet | Not documented yet | — |
| Rating | Not documented yet | Not documented yet | — |
| Select | Documented | Not documented yet | Keyboard navigation |
| Slider | Not documented yet | Not documented yet | — |
| Snackbar | Not documented yet | Not documented yet | — |
| Stepper | Documented | Not documented yet | Keyboard navigation |
| Switch | Not documented yet | Not documented yet | — |
| Tabs | Documented | Not documented yet | Keyboard navigation |
| Text Area | Not documented yet | Not documented yet | — |
| Toast | Not documented yet | Not documented yet | — |
| Tooltip | Documented | Documented | Accessibility |
Rows marked Not documented yet are a gap in this documentation, not a known defect. If you need a conformance answer for a specific component before the next review cycle, open an issue and ask.
Configuration Required
Some accessibility outcomes depend on how you configure the application rather than on the component alone.
| Concern | Criterion | What to configure |
|---|---|---|
| Animation and motion | 2.3.1 Three Flashes or Below | No configuration required. The animation player reads the operating system’s prefers-reduced-motion: reduce setting and plays animations with a duration of 0 when it is set. |
The remaining items apply to every platform.
| Concern | Criterion | What to configure |
|---|---|---|
| Time limits on transient messages | 2.2.1 Timing Adjustable | Components that auto-dismiss — such as Snackbar and Toast — expose a display-duration setting. Extend it, or disable auto-dismiss, so a user has time to read the message. |
| Color contrast after theming | 1.4.3 Contrast (Minimum) | Set foreground colors with contrast-color() or adaptive-contrast() rather than fixed values. See Theming Accessibility. |
| Accessible names on icon-only controls | 4.1.2 Name, Role, Value | Supply an accessible name in your own markup. A control showing only an icon has no name until you give it one. |
Formal Conformance Documentation
This page is a documentation index, not a conformance claim. It records what our own documentation covers; it does not certify any component against a standard.
For procurement, contract, or audit purposes — where a traceable, per-criterion conformance statement is required — request the current accessibility conformance report (VPAT) through your account manager or Infragistics support. Cite the product, version, and the standard the report must address (WCAG 2.1 Level AA, Section 508, or EN 301 549).
Earlier revisions of this page carried per-component conformance matrices. Those tables asserted a level of conformance that was not backed by a traceable, per-criterion assessment, and have been removed rather than restated. The conformance report is the authoritative source for that information.
Reporting an Accessibility Issue
If you find an accessibility problem in a component, report it on the Ignite UI for React issue tracker.
Include the component, the assistive technology and browser you used, the expected behavior, and the WCAG success criterion you believe is affected. Accessibility reports are triaged against the criteria listed above.
Additional Resources
- Theming Accessibility — contrast, text scaling, and chart palettes.
- WCAG 2.1 Quick Reference — all success criteria with techniques.
- WAI-ARIA Authoring Practices — expected keyboard and ARIA behavior per interaction pattern.
- Section 508 — United States federal procurement requirements.
- Formal Conformance Documentation — how to request a conformance report (VPAT) for procurement.
FAQ
Conformance is a property of a finished application, not of a component library on its own. Ignite UI for React targets WCAG 2.1 Level AA and documents per-component behavior in the index above, but the markup, content, and configuration you add determine the result. Use the index above to check the components you rely on, and report anything that does not behave as documented.
That status means the component’s own documentation does not yet describe the behavior. It is not a statement that the component fails a criterion - it records what the documentation covers, so you can tell the difference between a behavior that is documented and one that is not.
No. The Revised Section 508 Standards (published 2017, compliance date January 2018) replaced the earlier §1194.22 rules and adopt WCAG Level AA by reference, so meeting WCAG also addresses Section 508.
Partly. Keyboard and ARIA behavior is unaffected by theming. Color contrast is not — overriding colors can move text below the required ratio. Verify custom palettes as described in Theming Accessibility.
On the component’s own topic, linked from the Reference column above. The grid family shares a dedicated keyboard navigation topic.