WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: RE: Is "this-or-that logo" adequate in an ALT text?

for

Number of posts in this thread: 3 (In chronological order)

From: Ian.Lloyd@nationwide.co.uk
Date: Wed, Aug 21 2002 12:58AM
Subject: RE: Is "this-or-that logo" adequate in an ALT text?
No previous message | Next message →

-----BEGIN PGP SIGNED MESSAGE-----

********************************************************************
The contents of this email are intended exclusively for the
addressee. If you are not the addressee you must not read
use or disclose the email contents ; you should notify us
immediately [ by clicking "Reply" ] and delete this email.

Nationwide monitors e-mails to ensure its systems operate
effectively and to minimise the risk of viruses. Whilst it has
taken reasonable steps to scan this email, it does not
accept liability for any virus that may be contained in it.
********************************************************************

There has been a lot of debate on this issue, and it's actually got me
confused now - everyone has an opinon, and they're not all the same.

At the risk of causing more disagreement (dontcha just love it), could
someone summarise this thread into a few rules within one posting, based on
all the comments received so far?

Ian Lloyd, Electronic Channels
Nationwide Building Society

e-mail: = EMAIL ADDRESS REMOVED =
tel: 01793-655260
fax: 01793-656368


- -----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: 21 August 2002 07:14
To: = EMAIL ADDRESS REMOVED =
Subject: RE: Is "this-or-that logo" adequate in an ALT text?


Jim Thatcher wrote:

> It is not the visual alphabetical sorting that is the
> problem. It is the first letter navigation of the list
> that we all can use, whether with a
> screen reader or not. If the alt text [Home Page] appears,
> "H" will not hit that link. Same for "Link to Home Page."

Point taken. (Besides, the alphabetic sorting is relevant too, especially
when a list of links is presented in speech. Upon arriving at a page, a user
who hears the browser say "42 links on the page" might wish to listen to
them quickly to get a rough idea, then decide what to do next. And
alphabetic order might be an option, and a convenient one. On the other
hand, sorting algorithms _could_ be coded to ignore a leading "[", or even
leading "Link to".)

But the cases where I would (primarily) recommend the use of brackets around
the alt text are not things like "Home page" but what I call content-rich
images, or images that _really_ say more than a thousand words. For example,
an image could contain a pie chart and the alt text would say
"[Pie chart of our sales in 2002]"
or something like that. The alt text is not a _replacement_ for the image;
it does not communicate in words what the image communicates graphically.
Hence, it could be useful to distinguish it from genuine alt texts like
"Our sales in 2002 were dominantly (65 %) Widgets and just 35 % Gadgets"

(In fact, in the pragmatic side, there are three types of alt texts: alt
text that just describes the image; alt text that communicates verbally the
same thing as the image; and alt text that _partially_ communicates the same
thing as the image, hopefully the most important information. For example,
it might not be useful for a pie chart alt text to present _all_ the
information, down to the items with fractions of percentage.)

Images that say more than a thousand words would seldom be links, except in
contexts like a photo gallery where they are thumbnails (and then it might
actually be useful to sort their alt texts as different from normal links on
the page). If there would be some need to make the pie chart image a link,
it's probably better to use a separate textual link instead.

- --
Jukka Korpela
TIEKE Tietoyhteiskunnan kehitt

From: John Foliot - bytown internet
Date: Wed, Aug 21 2002 5:23AM
Subject: RE: Is "this-or-that logo" adequate in an ALT text?
← Previous message | Next message →

The thread has divided into two

1) the concept of using a phrase such as "FooBar Logo" as Alt Text for an
image. From my understanding, most users will understand what is meant when
we use alt text such as that, although it has been suggested that the logo
be descibed in more detail at least once on the site:
<.img alt="Nike Logo - a small swoosh similar to a checkmark, usually blue
(and worth millions)"> (artistic license to keep things light!) Other
solutions would be to provide a detailed description as text on one of your
pages (Mission Statement, Corporate History, etc.) and/or provide a LONGDESC

2) my push on whether there is any value or impedements introduced when
wrapping alt text in bracket containers [and I use square ones]. Here,
there is a potential issue if the [alt text value] is also being used to
indicate a hyperlink as screen readers *may* attempt to sort a links list by
the first character ("["), although at least one posting indicated that IBM
HPR ignored the sqaure brackets (Feedback from a JAWS user would be
welcome). It occurs to me that one could use:
<.a href=""><.img alt="[Photo - Skiddlefat]" title="Skiddlefat's web
page"></a> to resolve that issue.

As you have noted, there was a lot of traffic on this topic, but there
doesn't seem to be a resolution, although Jukka has summed it up well:
>
> (In fact, in the pragmatic side, there are three types of alt texts: alt
> text that just describes the image; alt text that communicates
> verbally the
> same thing as the image; and alt text that _partially_
> communicates the same
> thing as the image, hopefully the most important information. For example,
> it might not be useful for a pie chart alt text to present _all_ the
> information, down to the items with fractions of percentage.)
>
> Images that say more than a thousand words would seldom be links,
> except in
> contexts like a photo gallery where they are thumbnails (and then it might
> actually be useful to sort their alt texts as different from
> normal links on
> the page). If there would be some need to make the pie chart image a link,
> it's probably better to use a separate textual link instead.

As far as surrounding alt text in square brackets, I have not been presented
with a compelling reason not to, I have had at least one other agree that it
was a *good* idea and so I personally will continue. I had hoped at one
point to try and push this a little harder, but there did not seem to be any
real concencus. Oh well.

JF


----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/


From: Leo Smith
Date: Thu, Aug 22 2002 2:54PM
Subject: RE: Is "this-or-that logo" adequate in an ALT text?
← Previous message | No next message

I am not sure there is going to be one agreed upon set of rules just
yet, as I think there is still much debate (or maybe it all took place
today on this list, in which case apologies, as I receive the digest
version).

I have re-read the thread thus far, and in my mind one needs to
consider the various scenarios where ALT text is used instead of
the image element, and in each case consider the pros and cons
of the techniques we are proposing.

The first scenario is that of a screen reader user - the ALT text will
be used as a spoken alternative to the image, and in this case the
use of [ ] will not be of any use, and may even be a hindrance as it
will affect the first letter navigation of links in cases where images
are used as links and their ALT texts are used as the link
description. They may also affect the alpha listing of links.
Someone seemed to suggest that placing the link destination
information in the title attribute would solve this problem, that is:
<.img src="somelogo" alt="[some company logo]
title="homepage">.
But, will a screen reader index the title attribute value in favor of the
alt attribute value when it indexes the page's links - I have not
tested that so I do not know.

The second scenario is that where ALT text acts as a *visual*
replacement for the image. This would include situations where one
has images turned off in one's browser, or where text-only browsers
are being used. In these cases, using [ ] may well be of some
benefit. My preference would be to use these square parentheses
*only* where the ALT text is not a strict and complete replacement
for the information conveyed by the image. So, employ them for
purely visual images where generally only the *idea* can be
conveyed, or where the image conveys so much information (pie
chart example) that only a synopsis can realistically be offered with
ALT. In these cases, such images would probably tend to be used
less as links and so the pitfalls of using [ ] in ALT text would not be
as much of an issue. For example one *could* use "[bullet]" as the
ALT value for graphical bullets, which is certainly better than just
"bullet", but null alt text is probably still better here.

More often, images used as links are text-as-images that describe
the link destination - any ALT texts in these cases would be a
strict replication of the text-as-image content, and so would not be
contained in [ ] and thus avoid any pitfalls of using [ ]. I also like
the idea of using [ ] within ALT texts, to differentiate which part of
an ALT value is strictly verbatim replacement of the text-as-image,
and which part goes on to also describe extra idea or function
information about the image. Thus going back to our logo example,
I personally like:
<.img src="logo.gif" alt="Some Company [logo]">
or
<.img src="logo.gif" alt="Some Organization [go to home page]">
or
<.img src="logo.gif" alt="another company [logo]" title="go to
home page">

In these three examples, I think that the use of [ ] is fairly intuitive
and does not necessarily require some kind of explanation on the
site. These examples also avoid the problems with alpha link
listings and first letter navigation. I fear any title attribute values
would be lost in text only browsers, so the third example may not
be as useful for this scenario.


The last scenario I can think of at this late stage in the day (and I
am sure my scenarios are not exhaustive) is that of tooltips.
Agreed, using ALT text at tooltips is not _standard_ browser
behavior, but we cannot just ignore its use here when the dominant
browser out there uses it as such. In this scenario, I am not sure
whether using [ ] for any part of any alt text is useful or not. Indeed,
if we use a title attribute value in addition to ALT, then the user will
not see the ALT as a tooltip anyhow. I would say that in this
scenario, any literal information that the image conveys is entered
as the ALT value. Any additional information about the image's
function is placed in the title attribute. So for a company logo:
<.img src="logo.gif" alt="Some Company" title="go to Some
Company's home page">
Since the user in this scenario is using the visual information as
well as the tooltip, they do not need to have a tooltip that repeats
what the text-as-image spells out, nor do they need to be told that
it is the company logo (although I guess you could be explicit). The
tooltip does however provide extra information about the function of
the image that might be useful to a user in this scenario.

Any guidelines that we come up with will, I think, need to consider
all of these scenarios and probably more, and be something that
works for all of them.

That's my rather long 2 cents.

leo.

> There has been a lot of debate on this issue, and it's actually got me
> confused now - everyone has an opinon, and they're not all the same.
>
> At the risk of causing more disagreement (dontcha just love it), could
> someone summarise this thread into a few rules within one posting,
> based on all the comments received so far?
>


Leo Smith
Web Designer/Developer
USM Office of Publications and Marketing
University of Southern Maine
207-780-4774


----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/