Accessibility

Charleston Livability aims to provide a website that is readable, navigable, and usable for as many people as practical across desktop, tablet, and mobile devices.

The site is built around structured content, clear navigation, responsive layouts, and progressive enhancement so core information remains available even when a feature does not behave perfectly.

The site’s accessibility work focuses on practical usability: readable text, sufficient contrast, keyboard-friendly navigation, meaningful page structure, descriptive links, responsive layouts, and interface elements that remain usable on touch devices.

Where possible, pages should use semantic headings, visible focus states, alt text for meaningful images, and clear labels for interactive controls.

Some parts of the site may depend on third-party services, including mapping tools, MLS/IDX data displays, embedded media, analytics scripts, or browser-specific behavior. Those systems may not always provide the same level of accessibility control as native site content.

When a third-party component creates a barrier, the goal is to provide a practical alternative or improve the implementation where the site has control.

Global navigation, search links, menu controls, forms, buttons, and page links should remain reachable by keyboard. Mobile and off-canvas menu behavior should preserve access to links without creating hidden or unreachable navigation.

If you find a menu, form, map, listing component, or link that cannot be used with a keyboard or assistive technology, please report it.

If you experience difficulty using Charleston Livability, contact us at {accessibility-email}. Please include the page URL, the issue encountered, the device/browser or assistive technology used, and the best way to follow up.

Useful reports beat vague frustration. Screenshots are welcome. So are plain descriptions like “the menu opens, but I cannot tab to the close button.”

Accessibility is treated as part of the site’s maintenance process, not a decorative badge. Future improvements may include additional keyboard testing, clearer focus states, improved labels, better alternatives for map-heavy content, and more consistent component behavior across breakpoints.