Re: Supporting dynamic type
Re: Supporting dynamic type
- Subject: Re: Supporting dynamic type
- From: Vincenzo Rubano <email@hidden>
- Date: Thu, 12 Oct 2017 12:04:50 +0200
Hi Clare,
once again thanks for your help. It looks like iOS 11 has improved a lot
regarding dynamic type, so I think I’ll schedule implementing its support in my
app after the Swift 4 migration and iOS 11 SDK adoption.
Regarding Xcode, here’s an initial list of issues I’ve already reported
(they’re still present up to Xcode 9.1 beta 2):
* When using VoiceOver, keyboard commands to navigate texts don't work reliably
within the editor - 34475509
* Xcode 9.0 (9A235) VoiceOver commands to find text don't work within the
source code editor - 34475473 (closed as DUPLICATE OF 34246862)
* Xcode 9.0 (9A235) Unable to know which lines of code are affected by an issue
using VoiceOver - 34475460
* not reported yet: lines of code that wrap are announced multiple times when
reading code line by line;
Then there is this one which is not strictly related to accessibility, but due
to the accessibility regressions having an answer would be extremely helpful:
* Technical QA 1806: how long will Xcode 8 builds be accepted for? - 34475585
It is possible that there are other regressions, but due to these issues I’ve
not performed more extensive testing. As documented in Xcode release notes for
example there are some regressions in interface builder regarding the
IBOutlets/IBActions creation procedures…
Regards
Vincenzo
NVApple team
https://www.nvapple.it/about-us <https://www.nvapple.it/about-us>
> Il giorno 11 ott 2017, alle ore 01:14, Clare Kasemset <email@hidden> ha
> scritto:
>
>
>
>> On Oct 10, 2017, at 20:06, Vincenzo Rubano <email@hidden>
>> wrote:
>>
>> Hi Clare,
>>
>> thank you so much for your very detailed reply, it helps a lot! I’d need
>> some more clarifications.
>>
>>
>>> Il giorno 09 ott 2017, alle ore 03:00, Clare Kasemset <email@hidden>
>>> ha scritto:
>>>
>>> Starting in iOS 11, the best way to support dynamic type for navigation
>>> controllers is to access its navigationBar property and then set the
>>> prefersLargeTitles property to true. This will allow the bar to scale as
>>> needed for Dynamic Type, in the same way that navigation bars across the
>>> system do.
>>>
>> Thanks. I think I’ll use the prefersLargeTitles property as soon as I can
>> leverage the iOS 11 SDK, perhaps wrapping it in an availability check as the
>> app should support older iOS versions. What about the eventual prompt shown
>> on top of the UINavigationBar and the UIToolbar shown on the bottom of the
>> UINavigationController?
>
> In iOS 11, a user can long press to see a larger version for both UIToolbar
> and UINavigationBar items.
>
>>
>>
>>> I am not sure if there is an equivalent property for web views. It is
>>> possible that you may need to reload the webpage when the
>>> UIContentSizeCategoryDidChangeNotification gets posted.
>>>
>> OK, I’ll check this with a sighted tester unless I can figure out a way to
>> know how the font changes by using VoiceOver (I’m blind). But anyways
>> reloading the page when the UIContentSizeCategoryDidChangeNotification gets
>> fired is easy to implement.
>>
>>
>>> Currently there is no way to customize the font of the search text.
>>>
>> Does it mean that it will look bad when the view that contains it scales to
>> accomodate dynamic type? If so, would you recommend not supporting dynamic
>> type in that screen? Basically it is an advanced search screen shown modally
>> that contains a static UITableView, whose sections contain respectively the
>> search field and some filters that can be activated by pressing on the
>> corresponding cells.
>
> The search bar doesn't adapt for dynamic type currently, but it also doesn't
> interfere with other UI that adapts. I would recommend supporting dynamic
> type in other places on the same screen if possible.
>>
>>
>>> I don't believe there is API to customize the fonts in this view.
>>>
>> Does it mean that AVPlayerViewController playback controls do not scale to
>> accomodate dynamic type? And what about subviews added to the
>> contentOverlayView?
>
> Unfortunately I am not an expert on AVPlayerViewController. If the text in
> the main UI doesn't scale, please file a bug, as this should be handled at
> the framework level. I would expect subviews added to the contentOverlayView
> to scale if you set them up to handle dynamic type.
>
>>
>>
>>> Please do file bugs about the accessibility regressions in Xcode 9, if you
>>> haven't already. Thanks!
>>>
>> I’ve already done that for most of them, let me know if giving you their ID
>> could help ;)
>
> If you could send the list, that would be helpful. Thanks!
>
>>
>> Thanks again for your very detailed reply!
>>
>>>>
>>>> Vincenzo Rubano
>>>>
>>>> NVApple team
>>>> https://www.nvapple.it/about-us
>>>>
>>>>
>>>>> Il giorno 06 ott 2017, alle ore 14:08, Clare Kasemset
>>>>> <email@hidden> ha scritto:
>>>>>
>>>>> Hi Vincenzo,
>>>>>
>>>>> Which controls are you interested in? For example, UIButton gives you
>>>>> access to the underlying UILabel, so you can set the property on that
>>>>> instead. Or are you manually drawing text?
>>>>>
>>>>> Clare
>>>>>
>>>>> iPhoneから送信
>>>>>
>>>>> 2017/10/06 19:00、Vincenzo Rubano <email@hidden>のメール:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> since iOS 10.0 UIKit provides the UIContentSizeCategoryAdjusting trait
>>>>>>
>>>>>> https://developer.apple.com/documentation/uikit/uicontentsizecategoryadjusting
>>>>>>
>>>>>> which is very handy for supporting dynamic type without writing a ton of
>>>>>> boilerplate code. By using it you can enable support for dynamic type
>>>>>> from the UIAppearance proxy, which is even handier!
>>>>>>
>>>>>> However, according to docs only UILabel, UITextField and UITextView
>>>>>> adopt it. What about other controls? Do you need to reload fonts the old
>>>>>> way or do they have some “special” magic in order to support dynamic
>>>>>> type properly? Or perhaps they can be coerced in some way to adopt the
>>>>>> trait?
>>>>>>
>>>>>> Thanks in advance for your support
>>>>>>
>>>>>>
>>>>>> Vincenzo Rubano
>>>>>>
>>>>>> NVApple team
>>>>>> https://www.nvapple.it/about-us
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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