W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2016

Re: Accessibility and Web Fonts

From: Michiel Bijl (list) <michiel.list@moiety.me>
Date: Fri, 25 Nov 2016 07:18:50 +0000
To: WAI Interest Group <w3c-wai-ig@w3.org>
Message-Id: <BF8E9E55-E461-4A8C-B975-EE407B0C1419@moiety.me>
Hi Michael,

This is the first time I’ve heard of SVG font’s being used in that way. Especially considering SVG fonts have been removed from SVG 2.0 and considered a deprecated feature. For example, they were removed from Chrome 37 onwards. Some people with dyslexia that I know replace web fonts altogether, whether that be SVG, OTF. WOFF, or something else doesn’t matter.


> On 24 Nov 2016, at 19:29, Michael A. Peters <mpeters@domblogger.net> wrote:
> I usually don't do more than specify the broad type of font (e.g. sans-serif) but for a project I am currently working on, I am making use of web fonts.
> Commercial web fonts came with woff, woff2, and svg
> However in converting some FLOSS fonts to webfonts - I only made woff and woff2 versions.
> It was suggested to me that making SVG fonts available is of benefit to people with certain types of dyslexia, apparently they can be rendered in a way that make the dyslexia less of an impact.
> Is that really the case or do ttf repackaged in woff/woff2 work just as well? And if woff/woff2 do not work just as well, is there anything special that needs to be done when preparing the svg fonts and/or making the client aware they exist?
> I'm having trouble finding information on it.
> Thank you for anyone who knows, and happy Thanksgiving to those of us in the United States :)

Received on Friday, 25 November 2016 07:19:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:01 UTC