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: David MacDonald <david100@sympatico.ca>
Date: Thu, 20 Apr 2017 09:50:43 -0400
Message-ID: <CAAdDpDYb5pBRm80Fpnez=98Yu-=M_qR3DWs9DS-tp3SP=x_XBQ@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: Detlev Fischer <detlev.fischer@testkreis.de>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Here's the current thinking around icon font accessibility


Are these icons going to disappear if the font family is over ridden by a
user style sheet?

David MacDonald

*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902



GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>

*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy

On Thu, Apr 20, 2017 at 6:06 AM, Alastair Campbell <acampbell@nomensa.com>

> Detlev wrote:
> > So would this basically be a technique *for users* who would have to
> update any custom stylesheets they may be using by working in this
> exception for elements with role=img?
> Yes, but it has to work both ways, this would also be a sufficient
> technique for the new SC. I.e. if you use font icons that are problematic
> when fonts are replaced, then it musts be marked up appropriately.
> It would also need to be included as something in the testing text
> (understanding doc), and recommended for user-agent side solutions.
> >  I guess there is nothing authors can do to safely exempt icon fonts
> from any manipulation by user style sheets that fail to cater for icon
> fonts this way, correct?
> Correct, but if this is a known thing included in the techniques and
> understanding document, there is a viable solution.
> Cheers,
> -Alastair
Received on Thursday, 20 April 2017 13:51:22 UTC

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