More on BBC Mobile

On the theme of mobile web accessibility (#thereisawebappforthat) I did some more exploration of the BBC’s mobile ( web site and discovered that there is a mobile version of iPlayer at which streams video in MP4 format suitable for the iPhone. Thus, I’d have to regrade the BBC’s mobile accessibility to A+ … providing that you enter the site from the root URL.

In the spirit of research, and because I teach some of this stuff, I dug a little deeper and discovered that if you visit the BBC with a conventional browser, the pages are returned using the XHTML 1.0 Strict doctype and stylesheets are provided for screen and print media with customizations for Internet Explorer 6.

On the mobile site, the doctype is the Wapforum proper subset of XHTML 1.0 ( and the default stylesheet is tuned for mobile. What we used to call WML and WAP in fact.

Given that there is no conditional code or alternate stylesheets in these pages, I conclude that the BBC web server does some “browser sniffing” on arrival and checks the User-Agent field in the HTTP request. If you arrive at the home page with a mobile you are redirected to the mobile version of the web site. If you arrive at certain parts of the mobile site where there is media, further filtering takes place and “if you’re not on the list, you’re not getting in”.

This strategy works well, and allows the BBC to provide the mobile introduction page if you arrive with a conventional browser at This page has an embedded mobile emulator and a link to if you insist on going further with a normal browser.

If you examine the URLs in the BBC website, you get a clue as to why linking to a page, say on the news site, in a Tweet might not work for all audiences. Let’s take today’s news article: Honeybees are ‘Cleverer in the Morning’.This is the kind of quirky news headline that I’m sure you’d want to tweet. Indeed, the BBC offers you a sharing button that offers this tweet:

BBC News – Honeybees ‘cleverer in the morning’

Now, let’s say I receive this tweet on my twitter client (I used Tweetdeck, but Twitterific does the same thing) on my iPhone 3GS and I follow the link. The embedded browser loads the normal news page rather than the more appropriate The content is identical, but the doctypes, HTML headers and styleshets are different. The actual page (the one that was linked to remember) uses the conventional two column layout, rich navigational options and lots of white space and is tiny on a mobile on nomal (320 pixel wide (illustrated)) orientation and not much better at 460 pixel landscape orientation.

Honeybee story as displayed on mobile with 320 pixels width.

The mobile version stacks the headline, picture (smaller than the one on the main page), byline, article and navigation tools and is designed to work on small resoultion displays and looks great at even 320 pixels.
Honeybee story as displayed on mobile device

The fix is “simple”, expect your clients to reach your web sites from a referal rather than navigation, and do the browser sniffing and redirection everywhere, not just at the top level.

Of course, I write this from the comfortable position of a critic’s armchair. I don’t underestimate the technical problem of creating a fully accessible web site as large as the BBC’s, and they clearly have addressed many of the issues. There are just a couple of grey areas left.

There is a further complicating factor. As examination of the URLs will reveal, the BBC is not one website. It has many websites, spread out across many virtual directories and even across multiple domains (students read virtual hosts). Each one is presumably managed by separate teams and it must be quite difficult to achieve consistent and correct browser-based behaviour across them all. The BBC actually makes for a good case study for my students and I see an assignment coming on!

Blogged with the [Flock Browser]( “Flock Browser”)