Quality
Accessibility
Make the behavior of the components work for the whole interface.
Give every control a purpose
Prefer visible labels. Use aria-label when a control has no visible name, and name navigation landmarks when more than one appears on a page. A tooltip supplements a label; it does not replace one.
Provide captions or accessible names for tables and charts. Keep status text visible when color conveys success, warning or failure.
Test a complete keyboard journey
Tab through your composition and check focus visibility. Test arrow navigation in Tabs, Select, Command and date controls. Open overlays, press Escape and verify focus returns to a useful trigger.
The individual components provide behavior, but your composition can still break it through hidden content, disabled controls, unlabelled triggers or conflicting keyboard shortcuts.
Respect user preferences
Review the UI in light and dark, RTL, forced-colors and prefers-reduced-motion. Give tables a contained scrolling region instead of making the page overflow. Stack form groups when their content no longer fits.
Do not remove focus outlines. Scope animation to meaningful changes, and provide a reduced-motion presentation.
Know what has been verified
The repository has React/jsdom tests, token and CSS checks, plus manual browser review. Those checks are useful evidence, not a blanket WCAG certification.
Complex families such as DataGrid still need deeper assistive-technology audits. Verify the exact feature set, browser and preset you ship, and include real keyboard and screen-reader testing in your product's validation.