JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MCG Archives


MCG Archives

MCG Archives


MCG@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MCG Home

MCG Home

MCG  August 2009

MCG August 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Accessibility: where do we stand on alt tag use?

From:

Cristiano Bianchi | Keepthinking <[log in to unmask]>

Reply-To:

Museums Computer Group <[log in to unmask]>

Date:

Mon, 17 Aug 2009 18:49:23 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (245 lines)

Great post Frankie, and very clever and informative.
Thanks for sharing.

Best, Cristiano


On 17 Aug 2009, at 18:11, Frankie Roberto wrote:

> On Mon, Aug 17, 2009 at 11:59 AM, Jon Pratty <[log in to unmask] 
> >wrote:
>
>
>> My query today is about Alt tags.
>>
>
> I didn't want to go all geek on everybody, but nobody else has  
> responded to
> this yet, and it's something that there's still a bit of confusion  
> about, so
> I'll give it ago. If you're not interested, or already know this  
> stuff, look
> away now...
>
> Okay, so the alt tag (more precisely called an attribute) is meant to
> represent an textual "alternative" to the visual content (the photo or
> image). That is, if someone can't see the image, either because they  
> are
> blind, visually impaired, or because they're on a flaky or slow  
> internet
> connection, or because the image isn't available due to a broken  
> link, or
> because they're offline and only have access to the text (eg if  
> using an RSS
> reader which only caches the text for offline use, such as Google  
> Reader) or
> finally because they've simply chosen not to display images (rare,  
> but might
> happen for example on a mobile phone if someone wanted to save  
> bandwidth
> costs, or to just make pages load quicker)...
>
> ... then the text in the alt attribute is displayed INSTEAD of the  
> visual
> image.
>
> This is an important point, as it means that you show only ever see  
> the
> visual content OR the alt text, never both at the same time. So the
> behaviour of Internet Explorer prior to version 8 was 'wrong' in the  
> sense
> that it displayed the alt text as a tooltip. To appreciate why this is
> wrong, consider the instance where you have an image containing your  
> logo,
> which consists of the name of your museum (eg "The Hat Museum") in a
> particular font or wordmark. Wherever possible, you'd want people to  
> see
> this in the graphic form, as it's part of your brand identity, but  
> if that's
> not possible, then people should just see the name in plain text. So  
> the alt
> text is simply "The Hat Museum". So the behaviour of old versions of
> Internet Explorer in showing the alt text as a tooltip meant that  
> people
> hovering over the logo got the same text as was written in the logo  
> - not
> very useful.
>
> So far, this is all pretty represents the consensus of best  
> practice, and
> the fact that Internet Explorer 8 has changed its behaviour shows  
> that it's
> the way to go.
>
> What's less understood is what the alt text should be for images like
> photos, or illustrations, or graphics which serve a purely aesthetic
> purpose.
>
> If, for example, you write a blog post featuring an interview with  
> somebody,
> which contains a photo of the person you've interviewed, what should  
> the alt
> tag be on that photo. Some people might include something minimal like
> "Photo of <person's name>", which isn't very helpful at all. Other  
> people
> might try to be a bit more descriptive and say something like "Photo  
> of
> <person's name> posing in <location> with a laptop and a cool pair of
> shades". On the one hand, this is giving you the information which  
> someone
> who can see the photo is getting. However, the location, the laptop  
> and the
> cool shades probably aren't relevant to the story you're telling in  
> the blog
> post (in linguistics-geek-speak, it's not the "overtly intended
> communication"). So in this example, to work out what the optimal  
> alt text
> should be, you have to work out what the photo is actually  
> communicating.
> It's probable that it's not actually communicating much at all -  
> simply
> giving you an idea of what the person looks like. In this case the  
> alt text
> should be blank - ie alt="". This means that people who can't see  
> the image
> just get the text, with nothing else present - not an identical  
> experience
> to those who can see the image, but an equivalent one.
>
> On the other hand, there may be instances where a photo of a person
> communicates something which is central to the understanding of a  
> web page.
> For instance, you may write a "mystery object" type blog post, which  
> shows a
> curator holding an usual object, along with some text asking people  
> to guess
> what the object is. What should the alt text be here? Well, if you  
> left it
> blank, anyone who can't see the object is pretty left out from the  
> whole
> experience. On the other hand, if you described the photo fully in  
> the alt
> text, eg as "A photo of museum curator <person's name> holding an old
> medical instrument called an 'Earoscpope'" - then you're also giving  
> people
> who can't see the photo a poorer experience, as you're giving the  
> game away
> and are telling them exactly what it is. So in this example, a  
> better alt
> text would be something like "A curator holds a small metal object,  
> about
> the size of her palm, which at one end has a nut and screw, at the  
> other end
> has a small, curved protruding brown tube, and at the bottom has a  
> small
> wooden knob". This gives people who can't see the photo an  
> experience which
> is a little more equivalent to those who can (depending on how good  
> you
> think my description is), and they can still participate by guessing  
> what
> the object might be.
>
> So that's how alt text is meant to work. In practice, however, very  
> few
> people have this level of understanding about what good alt text  
> should be,
> and even amongst those who do, very few people take this amount of  
> time to
> properly consider the meaning of an image and to craft an equivalent
> text-based experience. This is compounded by the fact that very few  
> CMSs
> implement alt text in a way that supports this kind of considered  
> usage (eg
> by limiting the amount of characters you can use, or by associating  
> the alt
> text with the image, when the same image can communicate different  
> things in
> different contexts). Plus you also have to consider sites like  
> Flickr, where
> millions of photos are contributes by ordinary people, and it's hard  
> enough
> to get them to title and tag the photos, let alone write alternative  
> textual
> versions.
>
> For this reason, the current HTML 5 specification (
> http://www.whatwg.org/specs/web-apps/current-work/#alt) makes a  
> distinction
> between a blank alt attribute, which means roughly "this image is  
> decorative
> and doesn't communicate any content", and a missing alt attribute,  
> which
> means roughly "this image does communicate something, but we are  
> unable to
> tell you what". This latter case is obviously not ideal from an
> accessibility perspective, but at least it's honest, and in  
> circumstances
> like Flickr, is really the only option.
>
> So my general advice is to try to write meaningful alt text whenever
> possible, and to train other people to do so, but where this isn't  
> possible
> (due to time, resources, CMSs issues, whatever), acknowledge your  
> failings
> by not specifying an alt attribute at all...
>
> Phew!
>
> Cheers all,
>
> Frankie
>
> P.S The mystery object I described above is actually featured on this
> Powerhouse Museum blog post:
> http://www.powerhousemuseum.com/collection/blog/?p=436, where the  
> alt text
> is simply "Earoscope", (although this name is also given in the blog  
> post,
> along with a reasonable description, so perhaps the alt text should be
> blank?).
>
>
> -- 
> Frankie Roberto
> Experience Designer, Rattle
> 0114 2706977
> http://www.rattlecentral.com
>
> ****************************************************************
> For mcg information visit the mcg website at
> http://www.museumscomputergroup.org.uk.
> To manage your subscription to this email list visit
> http://www.museumscomputergroup.org.uk/email.shtml
> ****************************************************************



--

Cristiano Bianchi
Keepthinking

Bull Inn Court
15 Maiden Lane
London WC2E 7NG

t. +44 20 7240 8014
f. +44 20 7240 8015
m. +44 7939 041169 (uk)
m. +39 329 533 4469 (it)

NEW: Bologna +39 051 0547918

[log in to unmask]




****************************************************************
For mcg information visit the mcg website at
http://www.museumscomputergroup.org.uk.
To manage your subscription to this email list visit
http://www.museumscomputergroup.org.uk/email.shtml
****************************************************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager