Appendix D - Sample requests/communications with Web Developers
✓ Users with screen readers can’t navigate the menu — can we add proper labels?
❌ The ARIA attributes are missing.
✓ The contrast is too low — can we make the text darker?
❌ We need to meet WCAG contrast ratios.
✓ Keyboard users can’t tab through the form—let’s ensure they can navigate it without a mouse.
❌ The form is missing keyboard navigation support.
✓ Captions should be added so people who are hard of hearing can follow the video.
❌ The video needs WebVTT files.
✓ Some users can’t submit the form because error messages aren’t clear—can we make them more specific?
❌ We should implement proper error handling.
✓ On mobile, the map isn’t loading—let’s ensure it works on all devices.
❌ The JavaScript API has mobile rendering issues.
✓ The website is difficult to use on tablets—can we improve touch interaction?
❌ We need to fix the responsive design.
✓ The page doesn’t work well on different screen sizes—can we make it more flexible?
❌ The media queries are incorrect.
✓ Users on slow internet connections are struggling to load images—can we compress them without losing clarity?
❌ Optimize the image file sizes.
✓ It takes too long to find property zoning—can we simplify the search?
❌ The information architecture is bad.
✓ Users are confused about where to click next—can we add a clear call to action?
❌ The UX needs improvement.
✓ “Residents need to understand what ‘R-2’ means at a glance—can we add a short explanation?
❌ We should improve zoning code readability
✓ The contact form should confirm when a message is successfully sent.
❌ Add AJAX form validation.
✓ People should be able to find city council meeting minutes in three clicks or less.
❌ Improve site navigation.
✓ We need to show when data was last updated so users trust the information.
❌ Add metadata timestamps.
✓ Some community members don’t feel comfortable sharing their full address—can we allow ZIP code-only submissions?
❌ Adjust the geolocation data collection settings.
✓ We want to track engagement trends without collecting personal data—can we anonymize IP addresses?
❌ Enable IP tracking for public comments.
✓ Residents should be able to provide feedback without creating an account.
❌ Remove authentication for public engagement tools.
✓ People don’t know their feedback was received—can we send a confirmation email after they submit a comment?
❌ Set up auto-responses for submissions.
✓ The community wants to know how their input is used—can we add a section summarizing public feedback and next steps?
❌ Improve transparency in the engagement process.
✓ Not everyone is familiar with planning terms—can we add a glossary or tooltips for technical words?
❌ Improve content accessibility.