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

Re: Direct Outreach on Implementing WCAG 2.1

From: Katie Haritos-Shea <ryladog@gmail.com>
Date: Mon, 26 Nov 2018 09:21:13 -0500
Message-ID: <CAEy-OxFpUVijX90xv1snhXd-PpnvBhX99PF2F5MKDnA8-RuNCw@mail.gmail.com>
To: Wayne Dick <wayneedick@gmail.com>
Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>, Sharron Rush <srush@knowbility.org>, Shawn Henry <shawn@w3.org>, Judy Brewer <jbrewer@w3.org>, "Katie @ EverFi GOOGLE" <kshea@everfi.com>

I *think* Font Awesome has added what you are looking for via their
auto-accessibility feature for SVG+JS for web fonts (on their virtually
hidden Accessibility page) when a 'title' is added:

SVG with JavaScript: Semantic Icons

Getting accessibility right can be tough. So we’ve tried to make it as
simple as we can with our auto-accessibility feature. Using a dash of JS,
we add supporting HTML elements and attributes so that your icons are
accessible to the widest audience possible.

If your icon has semantic meaning, all you need to do is throw a
title="meaning" attribute. Auto-accessibility takes care of the rest,
adding the following:

   - Proper ARIA role (role="img")
   - title tag with a proper id attribute
   - aria-labelledby attribute and wire it to the title tag

Maybe you were looking for something simpler or different different?

** katie **

*Katie Haritos-Shea*

*Principal ICT Accessibility Architect, Vice President of Accessibility at
EverFi, **Board Member and W3C Advisory Committee Rep for Knowbility *

*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Oakton, VA **|* *LinkedIn Profile

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.

On Sun, Nov 25, 2018 at 5:26 PM Wayne Dick <wayneedick@gmail.com> wrote:

> Hello EOWG Members,
> Right now the most significant barrier to access for people with Low
> Vision is lack of implementation for WCAG 2.1. I imagine this is also an
> issue for Cognitive Disabilities as well.
> For low vision, on issue is particularly critical: Sticky headers, footers
> and buttons disable the responsive gains of the past 8 years for people who
> need responsive enlargement.
> Another serious issue is the failure caused by not including role="img" on
> icon fonts. Icon fonts are great when they are identified semantically.
> I think a letter from EOWG to educational institutions in the US as well
> as news outlets that these issues exists, constitute a significant barrier
> and do not meet current standards could be very helpful.
> For example if Awsome Fonts accessibility page could include the need for
> role="img" on "i" and "span" elements, it could have a dramatic impact.
> Consider this.
> Sincerely, Wayne
Received on Monday, 26 November 2018 14:22:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:55 UTC