From e02a2488a7122cb09ade8a49ae32e3c7e7bb2677 Mon Sep 17 00:00:00 2001
From: Menefail <flavienmarin57275@gmail.com>
Date: Sun, 11 Jan 2026 18:51:21 +0100
Subject: [PATCH] Create ACCESSIBILITY.md

Added a web accessibility guide, covering keyboard navigation, ARIA usage, colour contrast, and testing.
---
 docs/ACCESSIBILITY.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 docs/ACCESSIBILITY.md

diff --git a/docs/ACCESSIBILITY.md b/docs/ACCESSIBILITY.md
new file mode 100644
index 00000000000..8b00ba5d1dd
--- /dev/null
+++ b/docs/ACCESSIBILITY.md
@@ -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.