Documentation
Accessibility
What Mizen components guarantee, what your app owns, and what has been verified.
What components guarantee
Keyboard behavior follows WAI-ARIA patterns, through Base UI. Composite widgets keep one tab stop and move with the arrow keys.
Focus rings show for keyboard use only, and stay visible in forced-colors mode. Motion respects reduced-motion settings. Layouts mirror in right-to-left languages.
Components that need a name, including charts, Tree, Table, Carousel, and Code Block, throw an error in development when it is missing.
What your app owns
Give every control a visible label or an accessible name. Use Field to connect labels, descriptions, and errors to inputs.
Write meaningful page titles, headings, and alt text, and keep the page's heading order. Announce async results that happen away from the user's focus.
What is verified
Automated browser tests cover keyboard paths, focus, forced colors, reduced motion, right-to-left layout, and enlarged text, in Chromium and WebKit.
Firefox is not yet verified, and neither is manual testing with screen readers or on touch devices. These are open release tasks.