RE: NSAccessibilityListItemPrefixTextAttribute for non-standard Unicode characters
RE: NSAccessibilityListItemPrefixTextAttribute for non-standard Unicode characters
- Subject: RE: NSAccessibilityListItemPrefixTextAttribute for non-standard Unicode characters
- From: Charlie Powell <email@hidden>
- Date: Thu, 18 Feb 2016 23:31:48 +0000
- Thread-topic: NSAccessibilityListItemPrefixTextAttribute for non-standard Unicode characters
Thanks Josh. I was hoping that it would instead be possible to pass some sort of font information through the API in order to VO to look up the symbol's name from the font itself since I believe each character has a name like this. I guess that means it wouldn't be localized, but at least it would be something!
-----Original Message-----
From: email@hidden [mailto:email@hidden]
Sent: Tuesday, February 16, 2016 3:09 AM
To: Charlie Powell <email@hidden>
Cc: Apple Accessibility Developer List <email@hidden>
Subject: Re: NSAccessibilityListItemPrefixTextAttribute for non-standard Unicode characters
Hi Charlie!
The problem isn’t necessarily with the API, rather it’s with VO’s limited unicode set, which isn’t so limited but certainly doesn’t know how to read Wingdings :)
I’m sure you’ve already done this — as a workaround for unicode VO can’t translate, you can pass the unicode label. E.g. for smiley face, pass the label of “smiley face”.
Josh
> On Oct 27, 2015, at 4:34 PM, Charlie Powell <email@hidden> wrote:
>
> Has anyone played around with this new attribute in El Capitan? I've been able to successfully add support for the various list attributes, and it seems to work for the most part.
>
> The "documentation" for this attribute (which simply lives in NSAccessibilityConstants.h) says that for *common* Unicode characters, just return the character, and other things like images should have a label describing the image. But what are we supposed to do for *uncommon* Unicode characters? For example, I have the Wingdings font which uses the private Unicode range for certain characters, one of which is 0xF04A to represent a smiley face. The app will know to convert that to 0x4A since that's the character code for the symbol in the Wingdings. However, creating a string with this data, VoiceOver reads it as 'J' which has the standard Unicode value of 0x4A.
>
> Since this attribute apparently takes an NSAttributedString, I tried setting the font name attribute on the string to Wingdings, but that didn't help. Does anyone know if there's something I'm missing? Or perhaps this is just a limitation of the API, in which case I'll make sure a radar gets filed.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Accessibility-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> https://na01.safelinks.protection.outlook.com/?url=https://lists.apple.com/mailman/options/accessibility-dev/jscotland%40apple.com&data=01|01|email@hidden|87f6c2ffdd654ea5048808d336c1a589|72f988bf86f141af91ab2d7cd011db47|1&sdata=aiu1qVnVrJrehnz7bF/iNnhyHPs1YNzXu8UMny3bcJU=
>
> 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