There are several critical accessibility barriers on the current map:
• Unlabeled Interactive Elements: Many buttons on the map are announced only by a generic number or simply as "button." Without a geographic name (like the city or neighborhood) in the label, a screen reader user has no context for what they are selecting.
• Lack of Focus Management: When a camera cluster is selected, the screen reader focus does not automatically move to the resulting data. This forces the user to manually search the page to find the information they just requested.
• Non-Semantic Navigation: The page lacks ARIA landmarks and a clear heading structure, which prevents efficient navigation via keyboard for those who cannot see the visual layout.
To bring the site into alignment with WCAG 2.2 (Web Content Accessibility Guidelines) standards, the following is recommended:
-
Descriptive ARIA Labels: Add aria-label attributes to map markers so they announce contextually (e.g., aria-label="7 cameras in Kingston, WA").
-
Live Regions: Implement aria-live="polite" for the results panel so that camera lists are automatically announced when a location is selected.
-
Keyboard Optimization: Ensure all map markers are in the Tab order and can be activated using standard keyboard commands.
-
Text-Based List Toggle: Providing a "View as List" option that displays camera data in a standard, searchable table is often the most effective way to make geographic data accessible.
There are several critical accessibility barriers on the current map:
• Unlabeled Interactive Elements: Many buttons on the map are announced only by a generic number or simply as "button." Without a geographic name (like the city or neighborhood) in the label, a screen reader user has no context for what they are selecting.
• Lack of Focus Management: When a camera cluster is selected, the screen reader focus does not automatically move to the resulting data. This forces the user to manually search the page to find the information they just requested.
• Non-Semantic Navigation: The page lacks ARIA landmarks and a clear heading structure, which prevents efficient navigation via keyboard for those who cannot see the visual layout.
To bring the site into alignment with WCAG 2.2 (Web Content Accessibility Guidelines) standards, the following is recommended:
Descriptive ARIA Labels: Add aria-label attributes to map markers so they announce contextually (e.g., aria-label="7 cameras in Kingston, WA").
Live Regions: Implement aria-live="polite" for the results panel so that camera lists are automatically announced when a location is selected.
Keyboard Optimization: Ensure all map markers are in the Tab order and can be activated using standard keyboard commands.
Text-Based List Toggle: Providing a "View as List" option that displays camera data in a standard, searchable table is often the most effective way to make geographic data accessible.