Skip to content

feat: add screen reader semantics to map controls#51

Merged
matisiekpl merged 2 commits into
mainfrom
feat/semantics
Jun 10, 2026
Merged

feat: add screen reader semantics to map controls#51
matisiekpl merged 2 commits into
mainfrom
feat/semantics

Conversation

@matisiekpl

Copy link
Copy Markdown
Owner

No description provided.

@netlify

netlify Bot commented Jun 10, 2026

Copy link
Copy Markdown

Deploy Preview for aedmap ready!

Name Link
🔨 Latest commit f403a28
🔍 Latest deploy log https://app.netlify.com/projects/aedmap/deploys/6a2926b3db86a50008227cea
😎 Deploy Preview https://deploy-preview-51--aedmap.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@chrisdebian chrisdebian left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All seven tap targets from issue #41 are covered, labels are localised across all six languages, and the approach (wrapping in Semantics(button: true, label: ...)) is correct Flutter accessibility practice.

One optional follow-up: the navigate button could benefit from enabled: networkState.connected on its Semantics wrapper so screen reader users hear that it's inactive when offline. Not a blocker.

Great work — this is a meaningful safety improvement for an emergency-use app.

@matisiekpl matisiekpl merged commit 551dbf7 into main Jun 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Accessibility: app has no Semantics widgets — screen reader users cannot use it in an emergency

2 participants