W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Thu, 20 Apr 2017 14:29:26 +0000
To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Message-ID: <15F65C8F-ACB5-470F-9B78-BF0972E4BCAA@adobe.com>
If you go into https://symbolset.com and write the suggested words (cart, love, user, etc) they are converted to icons. Then go and change the font specified to arial or something else and you get the words.

Doesn’t this address the issue?


Andrew Kirkpatrick
Group Product Manager, Accessibility


On 4/20/17, 10:11, "Patrick H. Lauke" <redux@splintered.co.uk> wrote:

>On 20/04/2017 15:06, Andrew Kirkpatrick wrote:
>> I think that it is a problem if we forbid any
>> method/technique/technology that can be used in an accessible manner.
>> So, while using icon fonts seems to be challenging to do well, it
>> also seems possible to do well (see
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.filamentgroup.com%2Flab%2Fbulletproof_icon_fonts.html&data=02%7C01%7C%7C5e32382df79d4b0d18d908d487f75aa9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636282943838705564&sdata=8XMjonNSIB5d6aAPUOWVdXe7wuE7SOiOxzwr7pFqTW4%3D&reserved=0 for
>> problems and some solutions). If this resource is correct, we
>> shouldn’t be doing anything to forbid icon fonts _done well_ but
>> should be addressing the cases where the use of icon fonts causes
>> problems.
>There are techniques that can make icon fonts accessible to AT users, 
>and to users that run with browsers that don't support font-face,  but 
>no technique that makes them impervious to users changing their font 
>settings (note that this scenario is not mentioned in the 
>Filamentgroup's article).
>> Then we can have a failure that shows how to fail the SC by using
>> icon fonts incorrectly, and techniques that show positive examples of
>> how to pass the SC, but we don’t want to be in the situation of
>> saying that “yes, what you are doing is accessible, but because most
>> people don’t do that correctly we are banning the practice”.
>It's clearly not accessible if we're trying to allow for users to also 
>be able to arbitrarily change/override fonts though (which this SC does)
>Patrick H. Lauke
>https://na01.safelinks.protection.outlook.com/?url=www.splintered.co.uk&data=02%7C01%7C%7C5e32382df79d4b0d18d908d487f75aa9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636282943838705564&sdata=0t%2FsVSkA6rA2XB83yGIi0sfGEINQeAeZOn8DvUCzf2Y%3D&reserved=0 | https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatrickhlauke&data=02%7C01%7C%7C5e32382df79d4b0d18d908d487f75aa9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636282943838705564&sdata=4Y%2BIc%2FaKhptR46ltkWP%2Bv0dxFWH%2F2tVT3RRHnX5PdXA%3D&reserved=0
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&data=02%7C01%7C%7C5e32382df79d4b0d18d908d487f75aa9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636282943838705564&sdata=Tsb9LvPLToYfvwXvVpJuQwP1Sno312H2fs0yWr6INpY%3D&reserved=0 | https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&data=02%7C01%7C%7C5e32382df79d4b0d18d908d487f75aa9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636282943838705564&sdata=OZmOCd3il0SQXmGPhKgH%2B%2FGAEH4eqnAqMaVKykI1kaU%3D&reserved=0
>twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 20 April 2017 14:30:01 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:12 UTC