W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > August 2016

Re[2]: Finishing up WCAG Icon Font Issue 144 (was Re: Your thoughts on updated "Icon Font with an On-Screen Text Alternative" Technique)

From: <josh@interaccess.ie>
Date: Tue, 16 Aug 2016 16:27:33 +0000
To: "Laura Carlson" <laura.lee.carlson@gmail.com>, "Jim Allan" <jimallan@tsbvi.edu>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Message-Id: <emf46a4098-b92c-4d51-bdac-4153e0706d91@josh_machine>
Thanks guys. After that, the WCAG can review them.

Thanks a mil

Josh

------ Original Message ------
From: "Laura Carlson" <laura.lee.carlson@gmail.com>
To: "Jim Allan" <jimallan@tsbvi.edu>
Cc: "public-low-vision-a11y-tf" <public-low-vision-a11y-tf@w3.org>; 
"Joshue O Connor" <josh@interaccess.ie>
Sent: 16/08/2016 17:07:06
Subject: Re: Finishing up WCAG Icon Font Issue 144 (was Re: Your 
thoughts on updated "Icon Font with an On-Screen Text Alternative" 
Technique)

>Thank you, Jim. Much appreciated.
>
>Kindest Regards,
>Laura
>
>On 8/16/16, Jim Allan <jimallan@tsbvi.edu> wrote:
>>  Laura,
>>  I reviewed all of the materials associated with Icon Font Techniques. 
>>I
>>  don't find any objection to them from any task force member. You have 
>>made
>>  recommended updates and corrections.
>>  I will add to the agenda that we make a formal resolution on Thursday 
>>to
>>  finish the LVTF review of Icon Font Techniques. I am not sure what 
>>happens
>>  after that.
>>
>>  Jim
>>
>>  On Tue, Aug 16, 2016 at 9:42 AM, Laura Carlson
>>  <laura.lee.carlson@gmail.com>
>>  wrote:
>>
>>>  Hi Jim, Andrew, John, Wayne and all,
>>>
>>>  Josh has asked [1] if the following updated techniques are ready for
>>>  review by the full HTML WG:
>>>
>>>  Providing an On-Screen Text Alternative for an Icon Font
>>>  https://www.w3.org/WAI/GL/wiki/Icon_Font_with_an_On-
>>>  Screen_Text_Alternative
>>>
>>>  Using aria-hidden="true" on an icon font that AT should ignore
>>>  https://www.w3.org/WAI/GL/wiki/Using_aria-hidden%3Dtrue_
>>>  on_an_icon_font_that_AT_should_ignore
>>>
>>>  What is the next step in finishing up WCAG issue 144 so the Josh can
>>>  get them on a survey?
>>>
>>>  Thank you.
>>>  Kindest Regards,
>>>  Laura
>>>
>>>  [1] https://github.com/w3c/wcag/issues/144#issuecomment-240110660
>>>
>>>  Kindest Regards,
>>>  Laura
>>>
>>>  On 7/30/16, Wayne Dick <wayneedick@gmail.com> wrote:
>>>  > After the discussion at the LVTF this week I am really think that 
>>>Icon
>>>  > Fonts are just icons, images. None really have the same definitive
>>>  meaning
>>>  > as alphanumeric characters or punctuation symbols. They have no 
>>>precise
>>>  > definition like mathematical symbols. Icon fonts are really 
>>>non-text
>>>  > content. They are mapped to character sets for convenience, but 
>>>they
>>>  > are
>>>  > just pictures.
>>>  >
>>>  > Laura, I think your techniques are  a good start. Pictures require 
>>>text
>>>  > alternatives, and your code is one way to do that. Removing them 
>>>from
>>>  > the
>>>  > audio flow to prevent silly or incorrect text associated with icon 
>>>font
>>>  > characters, and then inserting the correct words seems exactly 
>>>right.
>>>  >
>>>  > Wayne
>>>  >
>>>  >
>>>  >
>>>  > On Fri, Jul 29, 2016 at 12:35 PM, Laura Carlson
>>>  > <laura.lee.carlson@gmail.com
>>>  >> wrote:
>>>  >
>>>  >> Hi John,
>>>  >>
>>>  >> Thank you for checking the technique and for your offer to help
>>>  >> wordsmith. Much appreciated.
>>>  >>
>>>  >> Kindest regards,
>>>  >> Laura
>>>  >>
>>>  >> On 7/29/16, Rochford, John <john.rochford@umassmed.edu> wrote:
>>>  >> > Hi Laura,
>>>  >> >
>>>  >> > I agree that description is more clear. I can help you 
>>>wordsmith it
>>>  >> later.
>>>  >> >
>>>  >> > Thank you for your work on this.
>>>  >> >
>>>  >> > John
>>>  >> >
>>>  >> > John 
>>>Rochford<http://profiles.umassmed.edu/profiles/display/132901>
>>>  >> > UMass Medical School/E.K. Shriver Center
>>>  >> > Director, INDEX Program
>>>  >> > Instructor, Family Medicine & Community Health
>>>  >> > www.DisabilityInfo.org
>>>  >> > Twitter: @ClearHelper<https://twitter.com/clearhelper>
>>>  >> >
>>>  >> > Confidentiality Notice:
>>>  >> > This e-mail message, including any attachments, is for the sole 
>>>use
>>>  >> > of
>>>  >> the
>>>  >> > intended recipient(s) and may contain confidential, 
>>>proprietary, and
>>>  >> > privileged information. Any unauthorized review, use, 
>>>disclosure, or
>>>  >> > distribution is prohibited. If you are not the intended 
>>>recipient,
>>>  >> > please
>>>  >> > contact the sender immediately and destroy or permanently 
>>>delete all
>>>  >> copies
>>>  >> > of the original message.
>>>  >> >
>>>  >> > -----Original Message-----
>>>  >> > From: Laura Carlson [mailto:laura.lee.carlson@gmail.com]
>>>  >> > Sent: Friday, July 29, 2016 7:30 AM
>>>  >> > To: Low Vision Task Force <public-low-vision-a11y-tf@w3.org>
>>>  >> > Subject: Your thoughts on updated "Icon Font with an On-Screen 
>>>Text
>>>  >> > Alternative" Technique
>>>  >> >
>>>  >> > Hello Everyone,
>>>  >> >
>>>  >> > Thank you so very much for our discussion yesterday [1].
>>>  >> >
>>>  >> > I updated the description for the "Icon Font with an On-Screen 
>>>Text
>>>  >> > Alternative" [1] technique trying to incorporate ideas from our
>>>  >> > meeting. It now reads:
>>>  >> >
>>>  >> > <quote>
>>>  >> >
>>>  >> > The objective of this technique is to show how to provide a 
>>>visible,
>>>  >> > text alternative for an icon font that conveys information.
>>>  >> > Icon fonts are fonts that use the Private Use Area (PUA) of 
>>>Unicode.
>>>  >> >
>>>  >> > Typically they are inserted in HTML via the CSS @font-face
>>>  >> > declaration
>>>  >> > and generated content property. Since they are vectors they are
>>>  >> > scalable and resolution-independent.
>>>  >> >
>>>  >> > Icon fonts can have 2 problems:
>>>  >> >
>>>  >> > 1. Some people with disabilities may not use assistive 
>>>technology
>>>  >> > (AT)
>>>  >> > and rely on on-screen text alternatives.
>>>  >> >
>>>  >> > 2. For those who do use AT, voicing of icon fonts may be 
>>>inaccurate,
>>>  >> > nonsensical, redundant, or unpredictable.
>>>  >> >
>>>  >> > To solve these 2 problems aria-hidden="true" is used so AT will
>>>  >> > ignored the icon. Then an on-screen text alternative is added 
>>>to
>>>  >> > convey meaning to everyone.
>>>  >> >
>>>  >> > <unquote>
>>>  >> >
>>>  >> > Thoughts? Is that clearer? Suggestions for improved verbiage?
>>>  >> >
>>>  >> > In addition, I added a definition section to the document per
>>>  >> > Andrew's
>>>  >> > suggestion of having an icon font definition. If anyone knows 
>>>of
>>>  >> > better definitions please let me know and I can revise that 
>>>section.
>>>  >> > The ones I found are very informal.
>>>  >> >
>>>  >> > Thank you.
>>>  >> > Kindest Regards,
>>>  >> >
>>>  >> > Laura
>>>  >> >
>>>  >> > [1] https://www.w3.org/2016/07/28-lvtf-minutes.html
>>>  >> > [2]
>>>  >> >
>>>  >> https://www.w3.org/WAI/GL/wiki/Icon_Font_with_an_On-
>>>  Screen_Text_Alternative
>>>  >> > --
>>>  >> > Laura L. Carlson
>>>  >>
>>>  >>
>>>  >
>>>
>>>
>>>  --
>>>  Laura L. Carlson
>>>
>>
>>
>>
>>  --
>>  Jim Allan, Accessibility Coordinator
>>  Texas School for the Blind and Visually Impaired
>>  1100 W. 45th St., Austin, Texas 78756
>>  voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
>>  "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>
>
>
>--
>Laura L. Carlson
Received on Tuesday, 16 August 2016 16:25:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:23:21 UTC