Hi Paul, and everyone,

A minor point, but I thought I'd point out that the way the iplayer icons
are implemented on pages like
http://www.bbc.co.uk/bbcfour/programmes/a-zdoesn't seem very
accessible. There's a background image specified on the
following spans:

<span class="availability" title="Available on iPlayer">&nbsp;</span>

Unless I'm mistaken though, many screenreaders, etc aren't likely to read
out the 'title' text (see the debate over the abbr-title microformat design
pattern). It's also not as semantically correct as it could be, and anyone
with images turned off (which admittedly isn't many people) don't see
anything either.

My recommended approach would be to use a plain old <img> tag with an alt
attribute of 'Available on iPlayer' - as this is exactly what alt text is
good for!

Alternatively, you could stick with specifying a CSS background, and place
the alternative text within the <span> itself, then moving it off the page
with CSS:

<span class="availability">Available on iPlayer</span>

This though retains the disadvantage of not working for people with CSS
enabled but images disabled.

Cheers,

Frankie


On Mon, May 19, 2008 at 8:54 PM, Paul Clifford <[EMAIL PROTECTED]>
wrote:

> We updated the /programmes site today and there are some new views
> that might be of use...
>
> See all programmes on a service with broadcasts +/- 7 days from now at
> /:service/programmes/a-z
>  http://www.bbc.co.uk/bbcfour/programmes/a-z
>  http://www.bbc.co.uk/6music/programmes/a-z
>
> Add /all to remove the 7 day restriction, or /player to show just the
> programmes with episodes available in iPlayer:
>  http://www.bbc.co.uk/radio1/programmes/a-z/all
>  http://www.bbc.co.uk/radio3/programmes/a-z/player
>
> Search within a service by adding "/by/:search" after "/a-z":
>  http://www.bbc.co.uk/radio4/programmes/a-z/by/e
>  http://www.bbc.co.uk/bbcone/programmes/a-z/by/doctor
>  http://www.bbc.co.uk/bbctwo/programmes/a-z/by/food/all
>
> Or search within all radio, all tv (soon), or all BBC services:
>  http://www.bbc.co.uk/radio/programmes/a-z/by/chris/player
>  http://www.bbc.co.uk/tv/programmes/a-z/by/east (soon)
>  http://www.bbc.co.uk/programmes/a-z/by/skating/all
>
> With one known and soon to be fixed exception, all the /programmes
> pages should be valid XML (and XHTML!), and hopefully easy to process
> with XPath etc.
>
> Not new, but you can fetch schedule data through the /programmes site.
>  Today's schedules:
>  http://www.bbc.co.uk/radio4/programmes/schedules/fm
>  http://www.bbc.co.uk/bbc7/programmes/schedules
>
> Or a schedule for a particular date:
>  http://www.bbc.co.uk/bbcfour/programmes/schedules/2008/04/28
>  http://www.bbc.co.uk/bbctwo/programmes/schedules/england/2008/05/22
>
> (Unfortunately, BBC One and BBC Two data outside the London and
> England regions can be patchy; we're working on improving that.)
>
> Add .xml to the end of a schedule URL to get an XML representation, or
> .json for JSON.  The format of the .xml and .json representations
> isn't fixed yet, but we're interested in any feedback from people
> using them.
>
> On Sat, May 17, 2008 at 3:38 PM, Brian Butterworth
> <[EMAIL PROTECTED]> wrote:
> > I wrote some code a while ago that goes though the BBC programme
> catalogue
> > at
> >
> > http://www.bbc.co.uk/programmes/a-z
> >
> > and creates a database table that I used to work out what the correct
> > iPlayer picture code to use for each, matching them up against the
> programme
> > schedules from
> >
> >
> http://www0.rdthdo.bbc.co.uk/cgi-perl/api/query.pl?method=bbc.schedule.getProgrammes&amp;channel_id=$strChannel&amp;start=$strDTS&amp;end=$strDTE&amp;limit=100&amp;detail=schedule
> >
> > For some reason I can access http://www.bbc.co.uk/programmes/a-z from a
> > browser, but doing a
> > file_get_contents("http://www.bbc.co.uk/programmes/a-z";) from PHP just
> locks
> > up.
> >
> > Is this intentional?
> >
> > I'm just having another go at making a 'what's on now' iGoogle theme for
> BBC
> > channels...
> >
> > Brian Butterworth
> >
> -
> Sent via the backstage.bbc.co.uk developer discussion group.  To
> unsubscribe, please send an email to [EMAIL PROTECTED] with
>  unsubscribe backstage-developer [your email] as the message.
>

Reply via email to