RE: properties for exposing custom Braille descriptions

I think that the label needs to be locale dependent. Otherwise people in one locale may see a label in another which will not make sense to them.
As soon as you start using ASCII Braille you must pair it with a table that converts the ASCII to Braille dot patterns. Different locales have different tables. And within some locales, multiple tables exist. If Unicode Braille can’t work, perhaps just a textual string which the screen reader can convert to Braille using the active table for that locale.

--Glen

Glen Gordon
Vispero™ | Software Fellow
17757 US Highway 19 N, Suite 560, Clearwater, FL 33764
T 727-803-8000 F 727-803-8001
ggordon@vispero.com<mailto:ggordon@vispero.com>
www.vispero.com<http://www.vispero.com/>

From: Peter Krautzberger <peter@krautzource.com>
Sent: Thursday, February 7, 2019 7:43 AM
To: White, Jason J <jjwhite@ets.org>
Cc: public-aria@w3.org
Subject: Re: properties for exposing custom Braille descriptions

Hi Jason,

This question is mentiond in the list of questions at the end of the page. My apologies if the page was not accessible enough to make it there.

Speaking for myself, I'd very much hope that Unicode Braille would work. But Braille ascii might be a useful consideration. As I understand it, NVDA's prototype back in May pushed the raw value out (and Sina's test files used grade 1).

Best regards,
Peter.