The second instalment…

• Is a new form of digital divide emerging?: What is the relationship between technology use and educational performance in science?
• http://andysblackhole.blogspot.com/2010/04/interested-in-biggger-picture-take-look.html

• Be the search engine: Geocaching adds an additional physical element to location-based social networking sites like Foursquare and Gowalla. 
• http://jwtto.wordpress.com/2010/04/22/be-the-search-engine/

• ePublish yourself: Not-for-profit website ePad Bud – the YouTube of children’s ebooks – is hugely motivating in the classroom.
• http://ilearntechnology.com/?p=2319

• Spotify takes aim at iTunes, befriends Facebook: Spotify upgraded its service by integrating social features to let users connect with friends and share music.
• http://www.wired.com/epicenter/2010/04/spotify-takes-aim-at-itunes-befriends-facebook/

• 100-year-old with impaired vision discovers the iPad: The intuitive way in which the iPad works seems to open doors to the elderly.
• http://edu.blogs.com/edublogs/2010/04/100-year-old-with-impaired-vision-discovers-the-ipad.html

accessibility, blogs, Education, epad, foursquare, ipad, location, spotify, Usability

The release of any new publically funded website inevitably provokes a tide of articles across the technology pages of the national press. The Queen’s new website, The Official Website of the British Monarchy, is the latest to face public scrutiny.

The Telegraph offers not one, but three articles providing detailed analysis of Her Majesty’s latest venture. In one of them, Julian Sambles reviews the site for its Search Engine Optimization and concludes that, scandalously, there are a number of areas in which it falls short:

• There are 2.6 error pages to every 1 genuine, working page
• Missing pages have no 404 page (‘This is a basic requirement for any website, let alone the Queen’s’)
• The homepage is duplicated and confusingly labelled
• There are inconsistencies in the title tags and the URL structure
• No h1 or h2 tags are present
• [etc.]

His conclusion is pretty damning:

It is disappointing that as our head of state, Her Majesty has allowed the creation of a website which should have been designed to engage with her subjects as much as possible but has overlooked the basics of good Search Engine Optimisation.

Dear, oh dear. Queen Elizabeth really shouldn’t have signed off on her own site without checking its SEO.

Aashish Chandarana raises the important issues of accessibility and usability throughout the site, in a second article by the trusty Telegraph, citing the inconsistent use of Alt tags and the same colour applied to both links and standard text. Fair enough – these are pretty basic errors that can make some users’ experiences incredibly frustrating.

I have some more general criticisms of the site. As with the new No. 10 site discussed in an earlier post, why can’t I leave comments on any of the videos? Why can’t I add my own obsessively catalogued pictures of the Royal Family to the paltry selection on some of the galleries? Why doesn’t the LightBox functionality work properly? Why, in the ‘Contact the Queen’ section of this ostensibly Web 2.0 site, can’t I just send her an email? What kind of an egomaniac only accepts communication stamped with her own face?

Why are there only 4 videos of the Duke of Edinburgh? And why does only one of them feature the good Duke? (The National Playing Fields Association 1951 advert is well worth a look incidentally, as he explains to a bunch of urchin-like children how to go about getting a playing field in their community – an issue that only surfaces when one of their number is brutally run down by a car whilst playing football in the street.)

http://www.youtube.com/watch?v=yMsnix1GPI4&eurl=http://www.royal.gov.uk/ThecurrentRoyalFamily/TheDukeofEdinburgh/TheDukeofEdinburghvideogallery.aspx&feature=player_embedded

The list goes on, but I won’t. I actually rather like the site – there’s a wealth of archive material and the articles I’ve read were informal, well-written and pretty interesting.

Now, whilst Sambles does sound at times as though he thinks Queen Elizabeth has been personally responsible for designing and coding the site –

– these sort of articles do of course raise some very real issues. It is right that publically funded sites in particular should be rigorously scrutinised, and it is absolutely right that the web should be accessible to all.

The articles highlight a numbers of issues surrounding the pursuit of best practice in our industry, which we should all aim to meet. If our monarch’s site doesn’t follow the basics, where does that leave the rest of us? In an industry so fast-paced, with attitudes and technologies changing faster than Prince Philip can say “Aren’t most of you descended from pirates?” to an islander in the Caymans, it’s difficult to stay on top of best practice methodologies.

This struck us recently when we developed a Flash game for BBC Ouch, a site ‘aimed at those with a stakehold in disability’. We do a lot of work in Flash, but it’s notoriously difficult to make Flash content accessible. However, the project gave us an excellent opportunity to learn about and improve in this area. Needless to say, developing for screen readers was a steep learning curve for all of us – and we’d be the first to admit that we’ve still got a lot to learn.

In fact there’s little doubt that there’s much more we – those of us in digital media – need to do to stay on top of usability and accessibility best practice values, however much of an uphill struggle that can be.

“Everybody was saying we must have more leisure. Now they are complaining they are unemployed.” (Duke of Edinburgh, during the 1981 recession).

accessibility, royalty, state_media