1 | 2 | 3

11 - 12   [12]

Tourism Website of the Year!? Cornwall Tourism Awards 2008

Relates to Accessibility

I have just been imparting my experience of web accessibility to a couple of aspiring young web developers emphasising the importance of a few simple considerations when it comes to preparing a new site design realisation. Of course nothing beats learning by example so we headed over to the recently announced Cornwall Tourism Awards 2008 Tourism Website of the Year Top Three to see what the cream of the crop could show us about the importance of accessibility.

However, landing on the first site www.classic.co.uk, I quickly realised that the exercise was about to take an about turn. What I had hoped would be three websites demonstrating the perfect synergy of design and accessibility turned out to be three sites lacking in even the simplest exposition of elementary accessibility!

Robert was quick to point out that he could hardly read that text it is so small!. Small text has been less of a concern since ems were integrated as the de-facto unit of font scaling about 5 years ago but scrutinising the CSS for the site we discovered that in fact the fonts have been scaled in points!!! Points - a unit that should be reserved solely for print style sheets as it delivers very erratic sizing across the common screen browsers. More importantly, a unit of absolute dimension which instantly kisses goodbye to WAI-AA compliancy (guideline 3.4 of the WCAG 1.0). And most significantly renders the site inaccessible to a small (but still significant) proportion of web users stuck in Internet Explorer 6 hell. Especially when the point size chosen is a shockingly small 8pt AND the same eye-crunchingly illegible point size is used for the principle navigation!

Still sticking with classic.co.uk for a moment longer I got the students to run a standard user test - disabling javascript and navigating the site. Since we are looking at a tourism site (remember one of the finest in Cornwall - apparantly!) I suggested they try and book a holiday. The first property details we landed on suffered from excess white space!? In fact the copy was floating off the right of the 800px wide browser pane. A quick test with javascript back on affirmed the site was using presentational javascript to re-position the copy to the left, filling the obtrusive whitespace, once the DOM had loaded. A most peculiar practice which initially left me bewildered for a suitable answer to feed my accessibility proteges. Perusing the source code suggests the builders chose to render the site for print (sans CSS) and then use presentational javascript to realise the desired visual design!? Right… Don't try this one at home kids! What ever happened to device independence - technology has existed since well before the first millenium cork was popped to designate media styles… The unobtrusive Javascript paradigm exists to facilitate device specific features extending a device independent shell. Not to hop from one device dependency to another!?

Great for our exercise all the same - my students were really getting stuck in now and developing a solid foundation in accessibility faux-pas. Seconds later Alex piped up - I can't make a booking! Oh what a surprise, or perhaps I should say, not a surprise, to discover the entire booking system was solely device dependent on Javascript. So WAI-AA is well and truly out the window now (WCAG 6.4 failure) and really we are tinkering on the point of accepting this site does not meet the expectations of the DDA.

By this stage we had spent so long discussing classic.co.uk there was barely time to examine the other two sites up for the coveted title of Tourism Website of the Year. Other than to learn that navigating stmichaelshotel.co.uk with images disabled was impossible. At least this time the availability checker was not javascript dependent (albeit inoperable when images were disabled). However the site did succeed in bringing up a blank page (or some rather cryptic VB errors for Microsoft legacy browsers) regardless of what dates were chosen leaving bemused students and tutor alike. While the over-zealous drop down menus added serious headaches for any keyboard users out there.

On discovering that www.bedruthan.com's navigation disappeared into a cloud of invisible white-ness when images were disabled I decided to call it a day. The students had learnt more than a thing or two about the importance of user testing and non-reliance on automated accessibility tests.

This is really the main reason for this convoluted expose of our discussion. We were not trying to pick holes in otherwise successful sites. On the contrary we had set out to use these respected sites as a means to elucidate good technique in basic accessible website building. Now I don't personally know the criteria that are used for adjudicating the CTB Website of the Year but one would hope accessibility plays a significant part in that criteria. Yet all three of these sites appear to have stumbled out from beneath the rubble of the post browser wars at the turn of the millennium. Perhaps the fact they somehow fudge their way through automated accessibility tests suggests this may have been all the criteria the awards expected. At least I hope no so-called accessibility analysts lay claim to having user-tested these sites - the errors are glaringly obvious!

What use is an awards system from a notable body such as the Cornish Tourism Board if it is not to help guide future aspiring developers on their own path of enlightenment by delivering the very best that the industry has to offer. So what if a site has previously won awards (as at least one of the top three has). Web development evolves at a rapid pace and the county should be able to deliver websites that embrace the prevalent technologies while meeting the important issues that persist over the years - accessibility and device-independence being two of the many!

Perhaps there are no tourism websites out there that can assert accessibility. If so it is shame… Or perhaps an opening for aspiring accessibility developers of the future? Rich, Alex and Carl - nudge, nudge! ;)

Posted on Oct 07, 2008 at 16:31:33.

An unknown error occurred (4010) - iTunes Genius FIXED

Relates to Software and Music

Are you suffering the 4010 error in iTunes Genius when you try to activate the service?

I had set up a subsidiary repository for my most popular music on a separate laptop where I could store all audio at 128kbps and transfer it freely to my iPod Touch without interfering with the music stored at higher bit rates on my main media drive. This in theory would also allow me to easily manage the new Genius feature for these compressed files and have it working on the Touch.

Alas though, I could not get Genius to activate! The iTunes Store just threw back the 4010 error every time the tracks were submitted.

I validated my iTunes library XML file; I setup a new iTunes account; I deleted the Genius database file; I converted any MP3 files that had not been created with iTunes; I tried repeated submissions; and even tried submitting in the early hours of the morning (to get around any server bottlenecks) but still to no avail.

So as a last resort I closed iTunes down and deleted the iTunes library XML file. In fact I deleted all the files in the iTunes directory - library file, Genius file, Extras file and the artwork cache. Note my actual music library was stored on a separate partition. If this is in the iTunes directory do not delete this of course ;) So when iTunes was re-opened it was a blank slate again. In my Advanced preferences I ensured the path to my library still pointed to the directory housing all my music files to ensure I didn't end up with two copies of each file! Then I added just one album (the classic Allman Brothers Live at Fillmore East) back to iTunes by dragging the folder and dropping it into iTunes (can also do File->Add Folder from iTunes menus). Now I tried once again to enable Genius and… it actually worked! Just to play it safe I added a few more albums at a time and updated Genius from the Store menu (in case it was a corrupt album causing the problem). But after 20 or so albums had been registered successfully with Genius I dropped the rest of the albums back in (200 in total) and once again submitted to Genius with no issues at all :)

So finally now I have Genius working with all the albums on my Touch. Well I say all but of course no collection is complete without a Beatles album or three which don't fit in with Apple's Genius currently!

Posted on Oct 07, 2008 at 16:17:25.

Breadcrumbs Trail

[ Home ] -> TW Blog -> Archives for October 2008
Site Map

The Severn Solutions website achieves the following standards:

[ XHTML 1.0 ] [ CSS 2 ] [ WAI AA ] [ Bobby AA ]

Page compiled in 0.028 seconds