Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility reader plugin #957

Open
tobrun opened this issue May 16, 2019 · 8 comments
Open

Accessibility reader plugin #957

tobrun opened this issue May 16, 2019 · 8 comments

Comments

@tobrun
Copy link
Member

tobrun commented May 16, 2019

Feature request for a plugin to integrate text to speech accessibility features. The developer is able to configure the plugin to point to a certain layer (eg. his own POI SymbolLayer) and the plugin would then hook into the Android accessibility service to read out text provided by the developer through its filter (eg. certain feature properties or the value of the text-field).

More info on accessibility services here.

cc @mapbox/maps-android

@langsmith
Copy link
Contributor

cc @malwoodsantoro , who's looking into accessibility these days.

@zugaldia
Copy link
Member

Love it. Why does this need to be a plugin, and not a core Maps SDK feature?

@stale
Copy link

stale bot commented Nov 12, 2019

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the archived Archived by Stale bot. label Nov 12, 2019
@stale
Copy link

stale bot commented Nov 12, 2019

This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.

@EscapeArtist
Copy link

Is there a fix for this? Do we have the ability to use TalkBack with the Annotations?
Would it work with MarkerView instead?

@tobrun
Copy link
Member Author

tobrun commented Mar 31, 2020

@EscapeArtist you can implement this yourself on your end by using the mapbox#queryRendererFeatures API

@langsmith
Copy link
Contributor

@EscapeArtist , the Mapbox demo app uses .queryRenderedFeatures() in various ways:

https://github.com/mapbox/mapbox-android-demo/search?q=queryRenderedFeatures&unscoped_q=queryRenderedFeatures

Then you could read out the information inside of the Feature(s) returned by the .queryRenderedFeatures() method

See https://docs.mapbox.com/android/maps/overview/query too

@EscapeArtist
Copy link

EscapeArtist commented Apr 3, 2020

@langsmith Thanks.
I followed the instructions of the documentation and stayed away from geojson, using the Annotation plugin, as is apparently recommended?
How does this work in that case? And how can you tie this with the Talkback feature of accessibility?
I should be able to use Talkback to cycle through everything on screen. That needs to include the currently visible Symbols ( Annotations ) visible on screen.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants