← Back to Legal Documentation
Effective Date: October 15, 2025 Last
Updated: October 23, 2025 Version: 1.0
WCAG Level: AA Compliant
Our Commitment to
Accessibility
StreetZones is committed to ensuring digital accessibility for people
with disabilities. We are continually improving the user experience for
everyone and applying the relevant accessibility standards.
We believe parking ticket defense should be accessible to ALL
drivers, regardless of ability.
1. Accessibility Standards
StreetZones conforms to the Web Content Accessibility
Guidelines (WCAG) 2.1 Level AA standards, which include:
- Perceivable: Information and user interface
components must be presentable to users in ways they can perceive
- Operable: User interface components and navigation
must be operable
- Understandable: Information and operation of the
user interface must be understandable
- Robust: Content must be robust enough to be
interpreted reliably by a wide variety of user agents, including
assistive technologies
2. Accessibility Features
2.1 Visual Accessibility
High Contrast Theme:
- ✅ Dedicated High Contrast Accessibility Theme with WCAG AA compliant color combinations
- ✅ All text meets minimum contrast ratio of 4.5:1 (WCAG AA standard)
- ✅ Large touch targets (minimum 44×44pt) for easy tapping
Text Scalability:
- ✅ Supports iOS Dynamic Type (font scaling)
- ✅ Supports Android font size preferences
- ✅ UI adapts to user's system font size settings
Color Usage:
- ✅ Information is never conveyed by color alone
- ✅ Icons and labels supplement color coding
- ✅ Chicago Stoplight System uses both color AND text labels:
- Red = "Boot Crew" (not just red)
- Orange = "Ticket Writer" (not just orange)
- Green = "All Clear" (not just green)
Visual Feedback:
- ✅ Loading states with text indicators (not just spinners)
- ✅ Error messages with clear text descriptions
- ✅ Success confirmations with visual and haptic feedback
2.2 Screen Reader Support
VoiceOver (iOS) Compatibility:
- ✅ All interactive elements have descriptive labels
- ✅ Proper heading hierarchy for navigation
- ✅ Meaningful announcements for dynamic content
- ✅ Alerts and notifications read aloud
TalkBack (Android) Compatibility:
- ✅ Semantic HTML and ARIA labels
- ✅ Logical reading order
- ✅ Custom announcements for critical alerts
Screen Reader Features:
- ✅ "Skip to main content" navigation
- ✅ Descriptive button labels (not just icons)
- ✅ Alt text for all meaningful images
- ✅ Zone numbers announced clearly (e.g., "Zone 3-8-1-6-0-8")
2.3 Motor Accessibility
Touch Targets:
- ✅ All buttons meet minimum size of 44×44 points (Apple HIG)
- ✅ Adequate spacing between interactive elements (8pt minimum)
- ✅ Large "Alert Others" button for easy one-handed use
Gesture Alternatives:
- ✅ No gesture-only controls - all actions have button alternatives
- ✅ Camera zoom has both pinch gesture and +/- buttons
- ✅ Map controls accessible via buttons (not gestures alone)
Keyboard Navigation (Bluetooth keyboard users):
- ✅ Tab order follows logical visual flow
- ✅ Focus indicators clearly visible
- ✅ All actions accessible via keyboard
2.4 Cognitive Accessibility
Simple, Clear Language:
- ✅ Plain language throughout the app (no jargon)
- ✅ Concise labels and instructions
- ✅ Consistent terminology
Error Prevention:
- ✅ Confirmation dialogs for destructive actions
- ✅ Clear error messages with recovery instructions
- ✅ Form validation with helpful feedback
Consistent Navigation:
- ✅ Predictable interface patterns
- ✅ Persistent navigation structure
- ✅ Clear visual hierarchy
2.5 Auditory Accessibility
Visual Alternatives for Audio:
- ✅ Push notifications include both sound and visual alerts
- ✅ Critical alerts show on-screen banner (not just sound)
- ✅ Haptic feedback for important events
No Audio-Only Content:
- ✅ All information has visual equivalents
- ✅ Captions for any future video content
- ✅ Transcripts for any audio instructions
3.1 iOS Accessibility Features
StreetZones supports iOS native accessibility
features:
| Feature |
Support |
Description |
| VoiceOver |
✅ Full |
Screen reader for blind and low-vision users |
| Voice Control |
✅ Full |
Hands-free navigation and interaction |
| Dynamic Type |
✅ Full |
Adjustable text sizes |
| Reduce Motion |
✅ Partial |
Respects animation preferences (where applicable) |
| Increase Contrast |
✅ Full |
High Contrast theme automatically activates |
| Bold Text |
✅ Full |
System-wide bold text preference supported |
| Button Shapes |
✅ Full |
Clear button affordances |
| Switch Control |
✅ Full |
External switch device support |
3.2 Android Accessibility
Features
StreetZones supports Android native accessibility
features:
| Feature |
Support |
Description |
| TalkBack |
✅ Full |
Screen reader for blind and low-vision users |
| Voice Access |
✅ Full |
Hands-free voice navigation |
| Font Size |
✅ Full |
System font size scaling |
| Display Size |
✅ Full |
Screen magnification support |
| Color Correction |
✅ Full |
Works with system color filters |
| High Contrast Text |
✅ Full |
Increased text contrast |
| Switch Access |
✅ Full |
External switch device support |
4. Testing and Validation
4.1 Testing Methodology
We test accessibility using:
- ✅ iOS VoiceOver on iPhone and iPad
- ✅ Android TalkBack on Pixel and Samsung devices
- ✅ Keyboard-only navigation (Bluetooth keyboard)
- ✅ Automated accessibility scanners (Axe, Lighthouse)
- ✅ Manual testing with users who have disabilities
4.2 WCAG 2.1 Compliance
Level AA Success Criteria Met:
| Principle |
Guideline |
Compliance |
| Perceivable |
1.1 Text Alternatives |
✅ All images have alt text |
|
1.3 Adaptable |
✅ Semantic structure, logical reading order |
|
1.4 Distinguishable |
✅ 4.5:1 contrast ratio, resizable text |
| Operable |
2.1 Keyboard Accessible |
✅ All functions keyboard accessible |
|
2.2 Enough Time |
✅ No time limits on critical tasks |
|
2.3 Seizures |
✅ No flashing content |
|
2.4 Navigable |
✅ Clear focus, skip links, headings |
|
2.5 Input Modalities |
✅ Touch target size, no gesture-only |
| Understandable |
3.1 Readable |
✅ Plain language, clear labels |
|
3.2 Predictable |
✅ Consistent navigation |
|
3.3 Input Assistance |
✅ Clear error messages, validation |
| Robust |
4.1 Compatible |
✅ Works with assistive technologies |
4.3 Known Limitations
Current Limitations (Being Addressed):
- Camera View: VoiceOver support for real-time camera OCR is limited (manual capture still accessible)
- Map Interactions: Some map gestures may be challenging for screen reader users (alternative list view available)
Workarounds:
- Camera: Use manual capture button + VoiceOver reads OCR results
- Map: Use text-based alerts list instead of map view
5. Assistive Technology
Compatibility
5.1 Tested Devices and Software
Screen Readers:
- ✅ iOS VoiceOver (iOS 15+)
- ✅ Android TalkBack (Android 10+)
- ✅ NVDA (Windows screen reader, for web admin portal)
- ✅ JAWS (Windows screen reader, for web admin portal)
Magnification:
- ✅ iOS Zoom
- ✅ Android Magnification
- ✅ Third-party magnifiers
Alternative Input:
- ✅ Bluetooth keyboards
- ✅ Switch Control devices
- ✅ Voice control software
5.2 Third-Party Accessibility Apps
Compatible with:
- Be My Eyes (visual assistance for blind users)
- Seeing AI (Microsoft's AI vision app)
- Voice Control apps (Dragon, Voice Access)
6. Feedback and Support
6.1 Accessibility Feedback
We welcome your feedback on accessibility!
If you encounter accessibility barriers or have suggestions for
improvement, please contact us:
Email: accessibility@streetzones.app
Subject Line: "Accessibility Feedback"
Please include:
- Device and OS version (e.g., iPhone 14, iOS 17.2)
- Assistive technology used (e.g., VoiceOver, TalkBack)
- Description of the issue
- Screenshot or screen recording (if possible)
Response Time: We aim to respond within 3
business days.
6.2 Accommodation Requests
If you need a reasonable accommodation to use StreetZones:
- Email: accessibility@streetzones.app
- Examples:
- Alternative formats (large print instructions)
- Customized notifications
- Dedicated accessibility support
We will work with you to find a solution.
7. Accessibility Roadmap
7.1 Ongoing Improvements
In Progress:
- 🔄 Enhanced VoiceOver camera guidance
- 🔄 Improved map accessibility (alternative list views)
- 🔄 Audio descriptions for visual alerts
Planned for 2025:
- Q4 2025: Voice-activated zone lookup
- Q4 2025: Audio readout of enforcement alerts
- Q1 2026: AI-powered accessibility features
7.2 Continuous Monitoring
We are committed to:
- Quarterly accessibility audits
- Regular testing with assistive technology users
- Staying current with WCAG updates
- Responding to user feedback promptly
8. Legal and Compliance
8.1 Legal Framework
StreetZones complies with:
- ✅ Americans with Disabilities Act (ADA) - Title III
- ✅ Section 508 of the Rehabilitation Act - Federal accessibility standards
- ✅ WCAG 2.1 Level AA - International accessibility standard
- ✅ Apple App Store Accessibility Guidelines
- ✅ Google Play Store Accessibility Guidelines
8.2 Non-Discrimination Policy
StreetZones does not discriminate on the basis of
disability. All features and services are designed to be accessible to
users with disabilities.
If you believe you have been discriminated against, please contact:
- Email: accessibility@streetzones.app
- Subject: "Accessibility Discrimination Complaint"
9. Training and Awareness
9.1 Team Training
Our development team receives training on:
- WCAG 2.1 guidelines
- iOS and Android accessibility APIs
- Screen reader usage
- Disability awareness and etiquette
- Inclusive design principles
9.2 User Education
We provide accessibility resources:
- In-app accessibility tutorial (first launch)
- Help documentation with accessibility tips
- Video guides with captions and transcripts
- Community support for accessibility questions
10. Third-Party Content
10.1 External Links
Third-party websites linked from StreetZones (e.g.,
Chicago parking payment portals) may have their own accessibility
standards. We are not responsible for the accessibility of external
sites.
10.2 User-Generated Content
Community-submitted content (zone photos, enforcement reports) may not meet our accessibility standards. We encourage users to:
- Add descriptive captions to photos
- Use clear, concise language in reports
- Avoid relying solely on color or images
11. Updates to This Statement
11.1 Revision History
This Accessibility Statement will be reviewed and updated:
- Quarterly - Regular updates based on app changes
- After Major Releases - When new features are added
- Following Feedback - When users report accessibility issues
Current Version: 1.0 (October 15, 2025)
11.2 Notification of Changes
Material changes to this statement will be announced via:
- In-app notification
- Website update
- Email to users who requested accessibility accommodations
General Accessibility Inquiries
Email: accessibility@streetzones.app
Website: https://streetzones.app/accessibility
Accessibility Coordinator
Name: [To Be Assigned]
Email: accessibility@streetzones.app
Phone: [To Be Added]
Mail: StreetZones Accessibility Team [Address to be
added]
For urgent accessibility issues, please mark your
email “URGENT - ACCESSIBILITY” and we will prioritize your request.
Acknowledgments
We thank our users with disabilities who have provided valuable
feedback to improve StreetZones’s accessibility. Your input makes our
app better for everyone.
Special thanks to:
- iOS and Android accessibility teams for comprehensive platform support
- The W3C for maintaining WCAG standards
- Accessibility advocates who champion inclusive design
Last reviewed and approved: October 23, 2025
This Accessibility Statement demonstrates our ongoing
commitment to making StreetZones usable by people of all
abilities.
Questions or suggestions? We want to hear from you at
accessibility@streetzones.app