# Are Mantine components accessible? Learn about Mantine components accessibility features ## Are Mantine components accessible? Yes, Mantine components follow [WAI-ARIA](https://www.w3.org/WAI/standards-guidelines/aria/) accessibility guidelines. All components have proper roles, aria-\* attributes, and semantics, provide full keyboard support, manage focus correctly, and support screen readers. ## How are Mantine components tested for accessibility? All components that have interactive elements are tested with [axe](https://www.deque.com/axe/) ([jest-axe](https://www.npmjs.com/package/jest-axe)) to ensure that they have all required roles and aria-\* attributes. Additionally, all components are tested for keyboard support and focus management with unit tests. You can view an example of these tests [here](https://github.com/mantinedev/mantine/blob/master/packages/%40mantine/core/src/components/Tabs/Tabs.test.tsx). The Mantine codebase has more than 10,000 unit tests. In addition to automated tests, Mantine components are manually tested with screen readers (VoiceOver) to ensure that they are fully accessible for users of assistive technologies. ## Is there anything I need to do on my side to make my app accessible? Of course! While Mantine components provide a solid foundation for accessible applications, there are still things that you need to do to ensure that your app is fully accessible. If a component requires props to make it accessible, this will be mentioned in the component documentation. Things to look out for while building accessible applications: * Use semantic HTML elements where possible: use `