Accessibility Statement

Accessibility Statement

Hey there, mesh explorer! We get how challenging it can be to navigate the web with a disability—it's not always straightforward, and we truly appreciate the extra hurdles that come with it. In the amateur radio and off-grid comms world like Meshtastic, we know many folks with disabilities find joy in these hobbies as a way to connect, tinker, and pass the time from wherever they are. That's why, as a small team of hobbyist volunteers, we've poured real time and effort into making the EH - Edmund's Hill Meshtastic Dashboard accessible for everyone. We're committed to inclusive design, ensuring folks with disabilities can dive into off-grid tech without barriers. This statement outlines our approach, but remember: accessibility is an ongoing journey!

Our Compliance Level

We're proud to say this site is fully compliant with WCAG 2.1 Level AA standards. That means we've ticked the boxes for the Web Content Accessibility Guidelines, which help make the web usable for people with various disabilities. We also align with the UK's Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, even though we're a small hobby setup. No overpromising here—we've audited and fixed issues to get here, but we keep an eye on things as the site evolves.

Key Accessibility Features

We've baked in features to make navigation, reading, and interacting smooth for everyone. Here's the rundown:

• Navigation & Structure:Skip to main content links on every page, proper HTML5 landmarks like main, nav, and footer, logical headings from H1 down, and breadcrumbs with ARIA attributes for screen readers.
• Keyboard Accessibility:Everything's 100% keyboard-friendly—no traps, visible focus outlines (at least 2px), and documented shortcuts. Modals and dropdowns? Fully navigable without a mouse.
• Screen Reader Support:Semantic HTML all around, ARIA labels on nav and interactive bits, table captions with scope, labeled forms with error announcements, and aria-live for dynamic updates like loading states.
• Visual Accessibility:Color contrasts hit WCAG AA (4.5:1 for regular text, 3:1 for large), site works at 200% zoom, strong focus indicators, and a print stylesheet for readable hard copies.
• Forms:Inputs have labels, real-time validation with accessible errors linked via ARIA, and success/failure messages that screen readers pick up.
• Interactive Elements:Buttons and links have descriptive text or ARIA labels, modals manage focus properly, and our cookie banner is keyboard-ready.
• Tables:All have captions, headers with scope, and semantic structure (thead, tbody, etc.).
• Images & Media:Alt text for meaningful images, aria-hidden for decorative ones.
• Cookie Consent:Keyboard accessible with ARIA for announcements and focus handling.

How We Test for Accessibility

To keep things solid, we use a mix of tools and hands-on checks: automated scans with axe DevTools and WAVE, manual keyboard navigation, screen reader tests (NVDA, JAWS, VoiceOver), zoom checks up to 200%, color contrast verification, and even user testing with people who have disabilities. It's not perfect, but it helps us catch and fix stuff early.

Known Limitations

Right now, we're fully compliant with WCAG 2.1 AA, but if new features pop up or tech changes, we might spot minor tweaks needed. No major issues at the moment, but accessibility isn't "done"—it's continuous. If you find something off, let us know!

Feedback and Contact

Your input helps us improve! If you spot an accessibility barrier or have suggestions, drop us a line via the contact form at http://mesh.ufblive.co.uk/contact.

Updates to This Statement

We'll tweak this as needed with site changes or new guidelines. Swing by occasionally to stay in the loop!