> On 26 Apr 2015, at 06:11, chaals@yandex-team.ru wrote:
>
> 22.04.2015, 15:36, "Bernard Tyers" <ei8fdb@ei8fdb.org>:
>> I haven’t had a chance yet to pass my screen reader over it, but I wonder how the obfuscated font will work with assistive technologies? Has anyone tried it yet?
>>
>> When I get some desk space and proper Internet I’ll give it a try and see what I find.
>
> I had a very quick look, and it creates random text replacing stuff. Which doesn't play well in a screen reader…
>
> Did I miss something?
>
Let me guess you were using Firefox or Chrome? Initially I was getting the exact same issue as you when I tried this, I wrote some text and copy-pasted it into a blogpost:
http://www.ei8fdb.org/thoughts/2015/04/w3c-public-privacy-thread/
I got random text, and thought it was broken. It seems the webfont isn't loading for me because the SSL cert on the URL hosting the webfont has expired (!) and so my browsers didn’t want to load it.
Following the link to the webfont: https://fontemutante.com.br/uploads/font_mutante/file/1/Mutante_fast_mix.ttf
and accepting the expired cert allows you to download and install the font to your system.
Leaving aside the (important) issue of the expired SSL cert for a moment, the results using a screen reader are not promising.
Using JAWS on Windows (version 16) screenreader it cannot interpret the text in any of Chrome, Firefox.
On OS X both Firefox and Chrome can “decipher” the text visually but it is not readable by VoiceOver. Safari cannot decipher it visually
Here is a short video I’ve recorded to illustrate the issue on OS X:
https://youtu.be/2-DOFRsx6jw
NB: The video is not listed, so please share responsibly.
I have a contact in Amnesty International who I have forwarded this to.
Any thoughts on this?
Thanks,
Bernard