> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/topics/accessibility.md).

# Accessibility 🚹

The balance between what looks good and what looks accessible is ongoing in products. Sure, some text next to that button will take away its minimalism, but I can guarantee a lot more users will understand what it does more clearly.

Focusing on accessibility increases the opportunities for people to use your product, because it works for them specifically. And with enough effort, 'them' can be anyone.

* [ ] Hierarchy

  Structuring elements to represent intended flow of information

  ⭐️ Sizing can help establish the importance of information

  ⭐️ Information should start from relevance and influence and descend from there
* [ ] Written and visual information

  The combination of text and icons to communicate

  ⭐️ Consider whether a visual item can communicate its action without colour and/or text
* [ ] Colors

  How they inform decisions and contrast with each other

  ⭐️ Always check contrast accessibility, even if it looks good to you
* [ ] Meta descriptions

  Text description of what an image looks like

  ⭐️ Implement this for when images don't load, or on hover if it does load
* [ ] Interactions

  How elements change when hovered, clicked, or highlighted on

  ⭐️ A visual change (darker colour, shadow) is one way to show an interaction in motion
* [ ] Device accessibility

  The difference in size and structure of elements between device sizes