<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 26, 2016, at 2:11 PM, Alexander Walters <<a href="mailto:tritium-list@sdamon.com" class="">tritium-list@sdamon.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
How...does the client side text interact with screen readers? Is
that an issue? It sounds like an odd thing to do in the first
place…</div></div></blockquote><br class=""></div><div>I don’t know for sure! According to <a href="http://a11yproject.com/posts/myth-screen-readers-dont-use-javascript/" class="">http://a11yproject.com/posts/myth-screen-readers-dont-use-javascript/</a> the majority of screen readers are perfectly capable of using javascript. It’s unclear what standard of JS they support though. To be clear though, (incase it wasn’t) the fallback if the translation engine is unable to run isn’t no text, it’s English text.</div><br class=""><div class="">
<br class="">-----------------<br class="">Donald Stufft<br class="">PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br class=""></body></html>