Describe the issue
The Maps filtering should work like the Events filtering in that the "Filter: Upcoming; Location: 1524" should be keyboard accessible and announced to Screen reader users upon landing back on page from applying filters.
To ReproduceSteps to reproduce the behavior:
Using Android, turn on TalkBack
Gesture to 'Map.'
Swipe through
Set a filter
Try to swipe through and ensure filter was applied
Expected behavior
"Filter: Upcoming; Location: 1524" can be gestured to using TalkBack so the user can ensure their filter parameters were applied. (This should also be receiving the focus upon landing on Map page after applying filter parameters)
Actual behavior
The "Filter: Upcoming; Location: 1524" is only read upon landing on the screen initially, this is not keyboard accessible to users gesturing through with TalkBack. Furthermore, the user lands on the back arrow receiving focus not "Filter: Upcoming; Location: 1524"
Screenshots
This area is not keyboard accessible but should be and should receive focus after applying filters.
Please let me know if you'd like it to have a separate bug. I thought these go hand in hand perhaps though and was trying to not over inundate y'all. :)
Describe the issue The Maps filtering should work like the Events filtering in that the "Filter: Upcoming; Location: 1524" should be keyboard accessible and announced to Screen reader users upon landing back on page from applying filters.
To Reproduce Steps to reproduce the behavior:
Expected behavior "Filter: Upcoming; Location: 1524" can be gestured to using TalkBack so the user can ensure their filter parameters were applied. (This should also be receiving the focus upon landing on Map page after applying filter parameters)
Actual behavior The "Filter: Upcoming; Location: 1524" is only read upon landing on the screen initially, this is not keyboard accessible to users gesturing through with TalkBack. Furthermore, the user lands on the back arrow receiving focus not "Filter: Upcoming; Location: 1524"
Screenshots This area is not keyboard accessible but should be and should receive focus after applying filters.
https://github.com/user-attachments/assets/ed226bb3-5cf7-4922-b70b-c131d6c10ce4
Testing Environment & Devices (please complete the following information): • OS: Android Version 13 • Device: Google Pixel 4a
Additional context I know the receiving focus could technically be another bug since it was technically violating these: WCAG 2.4.7 Focus Visible (AA) WCAG 2.1.1 Keyboard
Please let me know if you'd like it to have a separate bug. I thought these go hand in hand perhaps though and was trying to not over inundate y'all. :)