WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Script fonts within a graphic and 508 compliance

for

From: GF Mueden
Date: May 3, 2013 12:02PM


We are wasting time until we know the users eye disability and ability,
what equipment is being used, and the settings, and an exact descriptiom
of what is seen. Some people are inarticulate. The first step in
solving the problrm is understanding the problem. Here we don't have
enough information.

Is is posibleto get that information and to let the authority lmow about
us and that we are interested and woupd like to be kept informed?

George


On 5/3/2013 12:03 PM, Chagnon | PubCom wrote:
> Lainie wrote:
> "this logo includes the script font tagline underneath it. The user is
> stating that because the font is in script, it is not 508 compliant."
>
> The user who filed the complaint may indeed not be able to view the logo and
> tagline, but the fact that the tagline is in a script font probably isn't
> the problem. Some reasons that would make the tagline inaccessible are:
> 1. The tagline is a graphic, not live text. Solution: Alt-text.
> 2. The font is illegible or difficult to read. Solution: Choose a more
> readable font.
>
> Some scripts are less legible than others, making it difficult for sighted
> visitors to read. But other scripts are quite legible. It also depends upon
> how large or small the text is set.
>
> But, on the other hand, the tagline of a logo is PR fluff and not essential
> content. I'm wondering why anyone would take the time and effort to file a
> formal accessibility complaint for something such a useless item on a
> website. Plenty of other items in a website to worry about than the
> frou-frou tagline.
>
> -Bevi Chagnon
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> - - - - - - - - - - - - - - -
> www.PubCom.com - Trainers, Consultants, Designers, Developers.
> Print, Web, Acrobat, XML, eBooks, and U.S. Federal Section 508
> Accessibility.
> New schedule for classes and workshops coming in 2013.
>
> > > >