- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 7 Feb 2019 13:57:36 +0000
- To: Peter Krautzberger <peter@krautzource.com>
- CC: "public-aria@w3.org" <public-aria@w3.org>
- Message-ID: <11BDF977-2559-4B8A-B743-BF6A647AFEEE@ets.org>
Braille ASCII varies between countries, hence between the braille tables loaded by screen readers – so it can’t be used to specify a desired braille representation reliably. For example, if the author assumes North American ASCII braille, but the user’s system is configured for one of the European codes, the result won’t be what the author would expect. Only the Unicode block is unambiguous. From: Peter Krautzberger <peter@krautzource.com> Date: Thursday, February 7, 2019 at 08:43 To: "White, Jason J" <jjwhite@ets.org> Cc: "public-aria@w3.org" <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. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Thursday, 7 February 2019 13:58:00 UTC