WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: introduction and question about braille unicode

for

From: Peter Krautzberger
Date: Apr 6, 2020 1:41AM

Hello Mohammad,

Perhaps the following two pieces of information are not directly helpful in
which case I apologize.

First, the ARIA Working Group is currently working on adding new attributes
for customizing braille output (aria-braillelabel,
aria-brailleroledescription). Those properties are only in the ARIA draft
so far (cf. [1] below); they will hopefully be added to ARIA 1.3.
I'm actively involved in this effort and would be very interested in more
information about your use case. Would you be able to share an example of
the kind of content you are creating and what you have tested?

Second, the APA's pronunciation task force (cf. [2] below) is probably also
relevant. Its work is at a similarly early stage howevere.

Regards,
Peter Krautzberger.

[1] https://w3c.github.io/aria/
[2] https://www.w3.org/WAI/APA/task-forces/pronunciation/

Am Mo., 6. Apr. 2020 um 09:07 Uhr schrieb mohammad suliman <
<EMAIL REMOVED> >:

> Hello all,
>
> My name is Mohammad Suliman, I am a blind software developer. In the passed
> few months, I had the chance to start to work on a web project aiming to
> help blind people visualize graphs using braille, tones and speech. To
> achieve this, we use braille unicode in a special way to represent our
> data. Now this leads me to the question: do I need to set the lang
> attribute of the braille text to some special value? Does this affect how
> the screen reader announces this text? We noticed that some TTSs announce
> the braille characters as braille pattern or something similar, others stay
> silent, and others speaks gibberish. I doubt that using HTML or js code we
> could control that, am I correct? Also, to be compliant with WCAG
> standards, do we need to do something special for the braille unicode text?
>
> Thanks in advance!
> Waiting for your reply!
> Mohammad
> > > > >