Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions docs/ACCESSIBILITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Accessibility Best Practices

This document outlines guidelines to ensure the Base web experience
is inclusive and usable by as many people as possible.

## Keyboard navigation

- All interactive elements must be reachable via Tab and Shift+Tab.
- Provide visible focus styles for links, buttons and form controls.

## ARIA roles and labels

- Use semantic HTML elements where possible (e.g. `<button>`, `<nav>`, `<header>`).
- When semantics are insufficient, add appropriate ARIA roles.
- Always associate form inputs with `<label>` or `aria-label`.

## Colour contrast

- Text and interactive elements should have a minimum contrast ratio of 4.5:1.
- Avoid relying on colour alone to convey meaning.

## Testing

- Use screen readers (e.g. NVDA, VoiceOver) to test flows.
- Run automated tools such as axe-core as part of CI.
- Include accessibility considerations in code reviews.

Accessibility is a shared responsibility—following these best practices
helps provide a better experience for everyone.