Skip to content
DilworthCharlotte, NC

Accessibility Statement

We're aiming for WCAG 2.2 Level AA and want to hear about anything that gets in your way.

Last updated August 1, 2026

Plain language summary

We build this site to WCAG 2.2 AA as a target: real headings, skip links, keyboard navigation, alt text, and color contrast that meets the standard. We haven't formally audited every page, so if something is hard to use with a screen reader, keyboard or magnification, please tell us and we'll fix it. This document is a template provided for transparency; it is not legal advice, and we recommend the site operator have it reviewed by counsel before relying on it.

1. Our commitment

Discover Dilworth aims to make this site usable by as many people as possible, including people using screen readers, keyboard-only navigation, voice control or screen magnification. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C.

2. What we've built in

  • A visible "skip to content" link at the top of every page for keyboard users.
  • Semantic HTML headings with a single H1 per page and a logical heading order.
  • Descriptive alt text on photography and meaningful link text rather than "click here."
  • Color combinations chosen for a minimum 4.5:1 contrast ratio for body text.
  • Keyboard-operable navigation, FAQ accordions and forms, with visible focus states.
  • Responsive layout that reflows for zoom up to 200% without loss of content.

3. Known limitations

We have not commissioned a formal third-party accessibility audit of every page, and a site of this size can develop gaps as new pages are added — for example, an embedded map or an interactive filter that isn't yet fully described to assistive technology. We treat any such gap as a bug, not an acceptable trade-off, and prioritize fixes when they're reported.

4. Compatibility

This site is built to work with recent versions of major browsers (Chrome, Safari, Firefox, Edge) and commonly used screen readers (VoiceOver, NVDA, JAWS). It does not rely on Flash or other deprecated technologies.

5. Reporting a barrier

If you encounter a page, image, form or control that is difficult or impossible to use with assistive technology, please tell us. Include the page URL, the assistive technology or browser you were using, and a description of the problem if you can. We will confirm receipt and aim to address genuine barriers promptly. Reach us through our Contact page.

6. Ongoing work

Accessibility is a continuous process rather than a one-time checklist. We review new pages against this statement before publishing and revisit older pages as the site evolves.

Continue

Elsewhere on the site