Accessibility

Accessibility statement

Last updated: November 23, 2025

Person using crutches reviewing an accessible interface with keyboard, audio, and contrast controls
Built to stay usable with keyboard navigation, screen readers, and high contrast modes.

Our commitment

CrutchesGuide.com is committed to digital accessibility for people of all abilities. As a resource for mobility assistance, accessibility is central to our mission.

CrutchesGuide.com is run by one person who has spent a lot of time on crutches personally, so I know how important accessible information is when you are already juggling pain, mobility, and technology. I try to keep the site not only informative, but also usable for as many people as possible.

Goal: Make CrutchesGuide usable by the widest possible audience, regardless of technology, ability, or circumstance.

Conformance status

CrutchesGuide.com is designed with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA in mind. I aim to keep layouts, colors, and interactive components aligned with these guidelines.

  • WCAG 2.1 Level AA used as a target when designing templates and components.
  • Periodic reviews to maintain and improve accessibility.

Accessibility features

Keyboard navigation

  • Skip to main content on every page (Tab on load).
  • Full keyboard access (Tab, Enter, Arrow keys).
  • Visible focus indicators; logical tab order.

Screen reader support

  • Semantic HTML with proper heading hierarchy and landmarks.
  • ARIA labels on interactive elements.
  • Alt text for images; labeled forms; live regions for dynamic content.

Visual design

  • Text and buttons are designed to meet WCAG AA contrast ratios, and I adjust colors when audits reveal issues.
  • Text can typically be resized up to 200 percent without loss of core functionality.
  • Information is never conveyed by color alone; clear focus states.

Mobile and touch

  • Key touch targets are designed to be at least 44x44 px where possible; responsive design; zoom to 400% supported.
  • No horizontal scrolling on narrow viewports; content reflows.

Content structure

  • Plain language; consistent navigation and layouts.
  • Descriptive link text; logical grouping with clear headings.

Testing and validation

I periodically check accessibility using tools and methods such as:

  • Automated checks, including WAVE and Lighthouse reports.
  • Keyboard-only navigation tests.
  • Basic screen reader passes on key pages (for example, NVDA or VoiceOver).
  • Contrast checking tools.
  • Mobile device zoom and touch testing.

Known limitations

  • Third-party embeds (videos/maps) may not be fully accessible; alternatives provided where possible.
  • PDFs: HTML-based PDFs are accessible, but printed versions may lose some features.
  • External links: Accessibility of external sites cannot be guaranteed.

I am actively working to mitigate these limitations.

Feedback & assistance

I welcome your feedback. If you encounter barriers, please contact me:

  • Email: [email protected] (use subject “Accessibility Feedback”).
  • Contact form: Contact us.
  • Response time: typically within 2 business days.

When reporting issues, include the page URL, description, assistive tech used, browser, and OS.

Compatible technologies

  • Screen readers: JAWS, NVDA (Windows), VoiceOver (Mac/iOS), TalkBack (Android).
  • Browsers: Chrome, Firefox, Safari, Edge (latest versions).
  • Assistive tools: Keyboard navigation, voice control, screen magnification, browser zoom (up to 400%).

While CrutchesGuide.com is a small, independently run site, I use the following standards and laws as guides for accessibility:

  • Americans with Disabilities Act (ADA) principles for accessible public information.
  • Section 508 accessibility standards for digital content.
  • WCAG 2.1 Level AA as the primary technical benchmark.

I cannot guarantee perfect compliance at all times, but I treat these standards as the target when building and updating the site.

Continuous improvement

  • Periodic accessibility reviews as the site and templates evolve.
  • Ongoing self-education on accessibility best practices.
  • Updating code and content when new standards or tools emerge.
  • Incorporating feedback from readers who use assistive technologies.

Accessibility resources