Accessibility Statement
Guide to Cambridge is committed to ensuring digital accessibility for all users.
Our Commitment
We believe that everyone should have equal access to information about Cambridge's restaurants, businesses, events, and neighborhoods. We are committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability.
We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards.
Accessibility Features
Visual Accessibility
- • High contrast color combinations
- • Resizable text that maintains readability
- • Alt text for all meaningful images
- • Clear visual hierarchy and headings
Motor Accessibility
- • Full keyboard navigation support
- • Skip-to-content links
- • Large clickable areas for buttons and links
- • No time-limited interactions
Auditory Accessibility
- • No audio auto-play
- • Visual alternatives for audio content
- • Transcripts for podcast episodes
Technical Accessibility
- • Semantic HTML structure
- • ARIA labels where appropriate
- • Compatible with screen readers
- • Works without JavaScript for core content
Keyboard Navigation
You can navigate our website using only a keyboard:
- Tab - Move forward through interactive elements
- Shift + Tab - Move backward through elements
- Enter - Activate buttons and links
- Escape - Close modals and menus
- Arrow keys - Navigate within menus
Assistive Technology Compatibility
Our website is designed to be compatible with:
Known Limitations
We are continuously working to improve accessibility. Current known limitations include:
- • Some interactive maps may have limited screen reader support
- • Older PDF documents may not be fully accessible
- • Some third-party embedded content may not meet all accessibility standards
We are actively working to address these issues.
Feedback & Assistance
We welcome your feedback on the accessibility of Guide to Cambridge. If you encounter any accessibility barriers or need information in an alternative format, please let us know:
- • What you were trying to do
- • The page URL where you encountered the issue
- • Any assistive technology you were using