Re: Accessibility and MKMapView
Re: Accessibility and MKMapView
- Subject: Re: Accessibility and MKMapView
- From: Alexander von Below via Accessibility-dev <email@hidden>
- Date: Fri, 1 Jul 2022 19:25:53 +0200
Unfortunately, that Video WWDC Session 202
<https://developer.apple.com/videos/play/wwdc2016/202/> seems to have been
eaten by the Gods of Bit Rot.
Does anyone have a copy, somewhere?
Thanks
Alex
> Am 01.07.2022 um 12:01 schrieb Alexander von Below via Accessibility-dev
> <email@hidden>:
>
> Hi Dan,
>
> thank you for your reply! The annotations and current location are indeed
> exposed in VO, this was my error.
>
> Special thanks for mentioning the WWDC, I will go and revisit that. Overall,
> this is a very good exercise for me to again understand how voice over works,
> and what considerations need to be taken.
>
> Alex
>
>> Am 01.07.2022 um 01:48 schrieb Dan Golden <email@hidden
>> <mailto:email@hidden>>:
>>
>> Hi Alex,
>>
>> I’d expect the annotations and the current location marker to be exposed to
>> VoiceOver, can you file a bug with a sample project?
>>
>> With regards to disabling the points of interest, you can override
>> accessibilityElements on the map view, and only return your annotations from
>> there. You might need to create UIAccessibilityElements that represent the
>> annotation pins if you go this route though. If the POIs are showing on the
>> map, I think it’s reasonable behavior for a VO user to be able to navigate
>> through these. You could implement a custom rotor to only go through the
>> annotations you are adding if you want. We have a great WWDC talk on custom
>> rotors that covers that example in a map.
>>
>> -Dan
>>
>>> On Jun 30, 2022, at 4:26 AM, Alexander von Below via Accessibility-dev
>>> <email@hidden
>>> <mailto:email@hidden>> wrote:
>>>
>>> Hello,
>>>
>>> I am trying to get better at making apps accessible, and I found a nice
>>> exercise:
>>>
>>> For some other purpose, I created a sample app that contains a map view. It
>>> sounds like it could be accessible, because it really only serves two
>>> purposes:
>>>
>>> * It shows the current user location. With a button, the user can set a new
>>> marker at this location
>>> * It shows the previously set markers (MKAnnotations), which show callouts
>>> when selected that allow you to see details.
>>>
>>> By default, the Map View will zoom to show all the Annotations, so it
>>> sounds like even a blind user should be able to use the app.
>>>
>>> What actually happens, without giving any accessibility hints to anything:
>>>
>>> The MKMapView reads POIs on the map (which are not selectable). The
>>> Annotations are not read, nor is the current location
>>>
>>> I see that in iOS 16, there is a new MKMapFeatureOptions — is this what I
>>> would want to use? And is there a way to achieve my goal — mainly reading
>>> the existing markers on the map, without reading the POIs — in iOS 15?
>>>
>>> Thanks
>>>
>>> Alex
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Accessibility-dev mailing list (email@hidden
>>> <mailto:email@hidden>)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>>
>>> This email sent to email@hidden <mailto:email@hidden>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Accessibility-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden