This is an interesting issue. I assume you tested this with other screen readers?

If memory serves, the issue only seems to present with NVDA, much to my
disappointment. Tested with JAWS/Window-Eyes/Mac and iOS VoiceOver

On Mon, Jul 11, 2016 at 2:51 PM, Leonard de Ruijter <
notifications@github.com> wrote:

This is an interesting issue. I assume you tested this with other screen
readers?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5063 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AQTuqh68FLh21kgaVW2dIHA1E5xtCkf8ks5qUpDHgaJpZM4JJqpf
.

just a quick note to say that this issue also presents itself when using BrailleBack with Android devices. Perhaps a BRLTTY/HIMS issue in that case.

@cskchao: Is this still the case with the new Hims driver?

@LeonarddeR yes, I'm afraid so. At least over USB, this remains the case.

I'm afraid there's nothing else we can do other than close this as a needs external fix. We usually keep issues open until an external fix has been provided, however in the case of these displays that are not actively maintained by Hims any more, it is very unlikely that there will be provided a fix for it.