Open tobrun opened 5 years ago
cc @malwoodsantoro , who's looking into accessibility these days.
Love it. Why does this need to be a plugin, and not a core Maps SDK feature?
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.
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.
Is there a fix for this? Do we have the ability to use TalkBack with the Annotations? Would it work with MarkerView instead?
@EscapeArtist you can implement this yourself on your end by using the mapbox#queryRendererFeatures API
@EscapeArtist , the Mapbox demo app uses .queryRenderedFeatures()
in various ways:
Then you could read out the information inside of the Feature
(s) returned by the .queryRenderedFeatures()
method
@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.
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