Re: Icon fonts - semantic elements

+1  (and thanks Alastair for all you do to keep so many balls moving
forward)

G

glenda sims    |   team a11y lead   |    deque.com    |    512.963.3773


*web for everyone. web on everything.* -  w3 goals

On Tue, May 16, 2017 at 9:50 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> After a fairly epic twitter conversation with Patrick, we came to the
> conclusion it should be a failure of 4.1.2, which can be added by having a
> technique (and/or failure). It would then help to publicise this ‘change’,
> if there is any associated LV documentation that goes up around the time of
> 2.1…
>
>
>
> This is the thread (linking towards the end):
>
> https://twitter.com/patrick_h_lauke/status/864490963879723008
>
>
>
> Assuming people agree, where could we track this as a to-do item?
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
>
>
> *From: *"Repsher, Stephen J" <stephen.j.repsher@boeing.com>
> *Date: *Thursday, 11 May 2017 at 18:31
> *To: *Katie Haritos-Shea GMAIL <ryladog@gmail.com>, 'Jim Allan' <
> jimallan@tsbvi.edu>, LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.
> org>, 'Glenda Sims' <glenda.sims@deque.com>
> *Subject: *RE: Icon fonts - semantic elements
> *Resent-From: *LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org>
> *Resent-Date: *Thursday, 11 May 2017 at 18:32
>
>
>
> Yes, I was going to say the same thing as Katie.  The definition is:
>
>
>
> user interface component
>
> a part of the content that is perceived by users as a single control for a
> distinct function
>
>
>
> There’s certainly a deficiency here because ARIA can change the native
> role to various types that wouldn’t be considered UI components, such as
> “img” for icon fonts or sprites.  I’d also question whether role=”toolbar”
> or other container roles are covered here.
>
>
>
> Furthermore, if an icon is used as a UI component like a button for
> example, then 4.1.2 may only require you use <button> or role=”button” and
> give it a label, but then we’re back to the same problem when it comes to
> font replacement.
>
>
>
> Steve
>
>
>
> *From:* Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com]
> *Sent:* Thursday, May 11, 2017 1:07 PM
> *To:* 'Jim Allan' <jimallan@tsbvi.edu>; 'public-low-vision-a11y-tf' <
> public-low-vision-a11y-tf@w3.org>; Repsher, Stephen J <
> stephen.j.repsher@boeing.com>; 'Glenda Sims' <glenda.sims@deque.com>
> *Subject:* RE: Icon fonts - semantic elements
>
>
>
> Jim,
>
>
>
> In my mind only if that icon font was used as a *control*. 4.1.2 is
> really about interactive elements….my 2 cents…
>
>
>
> ​​​​​** katie **
>
>
>
> *Katie Haritos-Shea*
> *Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)*
>
>
>
> *Cell: 703-371-5545 <(703)%20371-5545> **|* *ryladog@gmail.com*
> <ryladog@gmail.com> *|* *Oakton, VA **|* *LinkedIn Profile*
> <http://www.linkedin.com/in/katieharitosshea/> *|* *Office: 703-371-5545
> <(703)%20371-5545> **|* *@ryladog* <https://twitter.com/Ryladog>
>
> NOTE: The content of this email should be construed to always be an
> expression of my own personal independent opinion, unless I identify that I
> am speaking on behalf of Knowbility, as their AC Rep at the W3C - and -
> that my personal email never expresses the opinion of my employer, Deque
> Systems.
>
>
>
> *From:* Jim Allan [mailto:jimallan@tsbvi.edu <jimallan@tsbvi.edu>]
> *Sent:* Thursday, May 11, 2017 12:56 PM
> *To:* public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>;
> Repsher, Stephen J <stephen.j.repsher@boeing.com>; Glenda Sims <
> glenda.sims@deque.com>
> *Subject:* Icon fonts - semantic elements
>
>
>
> Was drafting the email to html editor about where to file a but about
> specifying the semantic of sprites or icon-fonts so they can be
> programmatically determined.
>
> "role" popped into my head.
>
> How is using <i>some icon-font stuff</i> not a failure of
>
> *4.1.2 Name, Role, Value:* For all user interface components
> <https://www.w3.org/TR/WCAG20/#user-interface-componentdef> (including
> but not limited to: form elements, links and components generated by
> scripts), the name <https://www.w3.org/TR/WCAG20/#namedef> and role
> <https://www.w3.org/TR/WCAG20/#roledef> can be programmatically determined
> <https://www.w3.org/TR/WCAG20/#programmaticallydetermineddef>; states,
> properties, and values that can be set by the user can be programmatically
> set <https://www.w3.org/TR/WCAG20/#programmaticallysetdef>; and
> notification of changes to these items is available to user agents
> <https://www.w3.org/TR/WCAG20/#useragentdef>, including assistive
> technologies <https://www.w3.org/TR/WCAG20/#atdef>. (Level A)
>
>
>
> the icon-font is text but its role is an image shouldn't this fail 4.1.2?
>
>
>
>
>
> --
>
> Jim Allan, Accessibility Coordinator
>
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315 <(512)%20206-9315>    fax: 512.206.9264
> <(512)%20206-9264>  http://www.tsbvi.edu/
>
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>