Archive for the ‘web standards group’ Category

London Web Week - WSG Findability

Wednesday, May 28th, 2008 at 11:34pm

My second event of London Web Week was the Web Standard Group meeting on Findability.

The WSG meetings have been on hiatus for some time, but it was nice to see they are back on a (hopefully) more regular basis.

Concepts of Findability
Cyril Doussin

How to make something findable?

  • Make sure the item is easy to discover or locate
  • Have well organised system of navigation and retrieval

Hand-guided navigation can be helped with the aid of sensible sorting/ordering (eg of menus, alphabetical lists etc), and clear sign-posting.

Relevance

  • Precision: how well a system retrieves only relevant documents
  • Recall: how well a system retrieves all relevant documents

These two can be defined in the following way:

Precision = no. relevant & retrieved / total no. retrieved
Recall = no. relevant & retrieved / total no. relevant

Content Organisation

  • Taxonomy: organisation through labelling
  • Ontology: taxonomy + inference rules
  • Folksonomy: adds a social dimension

These will become increasingly important as the volume of information grows/is shared. Decent content organisation can be a very good basis for search engines.

Building Websites with Findability in mind
Stuart Colville

The search engine share in the US is apparently: 62% - Google, 18% - Yahoo, 10% - MSN/Windows Live and the rest are minor players. So obviously, search engine algorithms mean than you need as much content in your markup and as little fluff as possible. This means using unobtrusive JavaScript, for instance:

<ul>
<li><a href=””javascript:showPopup(’blueberry_muffins.html’);””>Blueberry Muffins</a></li>
<li><a onclick=”showPopup(’toffee_muffins.html’);” href=””#””>Toffee Muffins</a></li>
<li><a onclick=””showPopup(this.href);” href=””chocolate_muffins.html””> Chocolate Muffins </a></li>
</ul>

are all bad ways of doing it…

Instead, use non-bloated (and therefore search-engine relevent markup like this:

<ul id=”links”>
<li><a href=”blueberry_muffins.html”>Blueberry Muffins</a></li>
<li><a href=”toffee_muffins.html”>Toffee Muffins</a></li>
<li><a href=”chocolate_muffins.html”> Chocolate Muffins</a></li>
</ul>

along with this function:

function showPopup(url) {
window.open(url,”Poptastic”,”width=300,height=300″);
}
window.onload = function() {
document.getElementById(’links’).onclick = function(e) {
if (e.target && e.target.nodeName.toLowerCase() == ‘a’) {
showPopup(e.target.href);
}
return false;
}
}

[Sorry about the crappy formatting of the code block, WP doesn't let me do it any better for the moment]

Stuart also highlighted the importance (to search/findability) of URI permanence:

A Cool URI is one which does not change - Tim Berners Lee

Finding yourself with Fire Eagle
Steve Marshall

Steve gave us a run through of some of the cool stuff you can do with Fire Eagle, including how the system authenticates with other services and users. Fire Eagle is currently in closed Beta, but you can request an invite.

Playing Catchup

Thursday, May 17th, 2007 at 11:35pm

I seem to have got out of the blogging habit, so I’m hoping to catch up on a few posts now. I’ll tweak the dates so they’re relevent to the events roughly as they happened (chronology? what’s that?!)

The first event I’d like to make a post about was the excellent -

Web Standards Group Meeting on Javascript

Some of us shy away from JavaScript (until recently, myself included) on the grounds that it’s not accessible. But these days, if it’s done right, it can be positively beneficial to accessibility.

Demystifying Screen Readers - Steve Faulkner
Steve is very knowledgable on screen readers and all their foibles, and is Director of the Web Accessibility Tools Consortium. This talk mainly centred around Jaws (65%) and Window Eyes (35%). The bracketed figures are from a US National Federation of the Blind market share survey - it’s obvious these are the two big players.

The key issues revolve around:

  • Dynamic updates - user initiated and independent
    Can the user access the updated content?
    Is the user aware that the content has been updated?
  • Rich Internet Applications (RIA)
    Can the user understand the role of the control?
    Can the user successfully interact with the control?
    Is the user able to access information about the current state of the control?

He then explained the differences in screen reader modes:

  • Browse Mode (virtual buffer) - the user can navigate page content via paragraphs, headings, links, lists etc. They can also activate links and some form controls. But text characters can’t be input into form fields, or interact with select elements in this mode.
  • Forms Mode (browse mode off) - the user may only navigate through a document to focusable elements via the TAB key. Text access is limited to “read all” functionality. Most of advanced content navigation is unavailable.

The crucial question we have to consider is, when and how does content become available to the user after it’s been updated in the browser?

[Steve Faulkner and the Latency Issue]

Latency is a problem because the virtual buffer does not update and the user doesn’t know anything has changed. However, JAWS v7.1 started “listening” for virtual buffer updates in response to things like:

  • window.setInverval()
  • object.innerText (for IE)
  • object.textContent and object.appendChild (in Firefox)
  • changes in form control values
  • And other stuff like ALT or TITLE attribute value changes.

Jez Lemon has an excellent article on Improving Ajax Applications For JAWS Users on his webiste. Steve summed up with some recommendations:

  • Do not code to accommodate the poor support shown by JAWS and Window Eyes.
  • Use unobtrusive methods where available and appropriate, to help screen readers along.
  • Don’t use the excuse that JavaScript / Ajax is not accessible for screen readers to not bother to design for accessibility.
  • Start developing interface elements that use WAI-ARIA specs, which will provide some benefits now and many more in the future.

Steve’s thought-provoking presentation was followed by a turn from Christian Heilmann entitled Seven Reasons For Code Bloat

[Christain's been on the beanz again]

His notes are available for download from his blog, so I won’t repeat them verbatim. Needless to say, it was a fun presentation and contained the obligatory photo of a kitten ;-). Meanwhile, he’s thinking of this as the title of his next book:

[Christian's Next Book?]

PubStandards XVIII
Of course, the next item on the social agenda was the PubStandards gathering. Lots of fun and revelry as usual, here’s one photo, but you can see more on Flickr.

[Patrick & Ashe go head-to-head, while Ross butts in the middle]

WSG London #3 - Accessibility

Saturday, March 3rd, 2007 at 10:44pm

I’m playing catch-up a bit with blogging. I was at the third London Web Standards meeting on 28th February, which had an Accessibility theme.

We had three very different talks, each highly informative and enjoyable.

Niqui Merret on Accessbile Flash
Niqui started out by saying that Flash and accessibility don’t have to be mutually exclusive, as many people presume. However, in the real world:

No single technology can be 100% accessible to all users. Aim to achieve the most accessible solution possible.

It’s up to developers, programmers and copywriters to make sure their contributions are as accessible as possible. It’s also up to the software vendors (eg of screen readers) to try and implement the standards properly and as quickly as possible. She also mentioned FlashAid (talks to screen reader and turns off the Javascript/Ajax so browser sees alternative accessible content) and SWFFix (a tool for progressive enhancement) as useful resources for Flash developers.

She talked a bit about the Accessibility panel in the Flash authoring environment, which allows developers to set things like Tab order and ALT text. And she demonstrated a fun little game in Flash, which was fully accessible without mouse and to screenreaders:

[Niqui demonstrates her accessible Flash game]

Ann McMeekin on Accessibility - What Not To Do
Ann is a Web Accessibility Consultant for the RNIB, and clearly knew her subject inside out.

She made many excellent points, but some of the most salient were:

  • Don’t assume all users with disabilities are the same
  • Don’t ignore users who come to you with a problem
  • Don’t forget to set your page’s default colours - background and foreground (if not, changing Windows default colour scheme could have a dramatic effect)
  • Don’t waffle - be clear and concise, don’t repeat yourself
  • Just because you can add a title attribute to almost anything, doesn’t mean you should - it’s largely redundant if your link text is descriptive enough
  • Don’t be shy - show skiplinks, and use :focus and :active as well as :hover
  • Put instructions before forms - otherwise someone who has zoomed the page (magnified) doesn’t have a hope in hell of seeing what the labels are

One of the most surprising things was to learn that most screen readers will read out the legend to an accompanying fieldset before every label in the fieldset - so it’s important to keep legends short and concise, and so they will make sense when read with the form field label.

[right, Ann in full flow]

Two final thoughts from Ann:

  • Don’t jump on the bandwagon and implement the latest cool widget without knowing what impact this might have on your users
  • Accessibility doesn’t mean you can’t be creative

Mike Davies on Web Accessibility - The Developer’s Tale
Mike’s talk was a case study of the re-design of Legal & General’s website services and applications, which he had been heavily involved with before his move to Yahoo! in the summer of 2006.

Four years ago, before the project started, L&G’s website was ranked 92nd in a FTSE100 survey of websites; it ranked badly with search engines, had at least 150 links on every page and was horribly inaccessible. Through the vision of the website manager, the site was completely redesigned with accessibility at the heart of the thinking.

They reaped the benefits very quickly:

  • 40% increase in website traffic
  • doubled conversion rates (that is, number of people completing an online application for insurance etc, versus those who start the process)
  • doubled online revenue
  • cut maintenance costs by two thirds
  • increased natural search-engine traffic by 50%
  • paid for itself in five months

[conversion rates for Home Insurance - lilac = old site, burgundy = new site. The first two bars are the numbers starting the process, middle represents those finishing a quote and last pair are numbers of completed applications]

And the website is now held up as a highly-regarded example of how to do things properly - it is a PAS 78 and AccessibilityNet case study, has accreditation from the Shaw Trust, and is cited in books on accessibility.

Thanks again to Stuart for organising an excellent event. I look forward to the next one.

RDF - What’s It Good For?

Wednesday, February 28th, 2007 at 3:07pm

One of the presentations that I missed at BarCampLondon2 (I was attending another session) was a light-hearted debate about the similarities and differences between Microformats and RDF. The main protagonists were:

Thankfully, for those who didn’t see the debate, Ian has uploaded a video of the session. It makes interesting viewing! And shortly afterwards, I found Ben Ward’s insightful post about the whole subject too. I think Ben’s second paragraph hits the nail on the head:

The thing about RDF is that no-one has yet demonstrated any real-world reason to care about it. It fascinates academics who would love — just for the sake of it — to model the entire universe in triples but in the real world of web browsers the value has never really been promoted.

Spot on.

The Microformats advocates have been very quick to explain what they are for, what they do, and how to implement them. I use them regularly in this blog, and try to incorporate them wherever I can into new projects. It’s so easy to build them in from scratch when marking up events (hCalendar), people (XFN) or contact details (hCard).

But as yet, I’m really stumped as to what RDF - or more importantly, eRDF can do for me. Tom Morris has started a website called GetSemantic which hopes to chart the progress of developments about eRDF and spread the word. I’ll be keeping an eye on it from time to time, to see what’s cooking, but until then, I’ll be sticking to my diet of Microformats.

Previews

Monday, February 12th, 2007 at 5:32pm

BarCamp Presentation
I’m happy to have finished writing my presentation for BarCampLondon2. I’ve decided to do a spot on Better Picture Taking as there seem to be plenty of folks with digital cameras who want to know more about getting the most out of their gear. It won’t be technical, and it won’t be biased towards any particular type or brand of camera. Instead, I’ll be covering the basics of good composition and lighting, plus editing your pictures for showing to friends. After BarCamp, I hope to blog most of the content for those who couldn’t attend.

I’ve gone for a non web-related topic as I figure I’ll be teaching many of the attendees how to suck eggs if I talk about web standards or css. Others have said that some of the most interesting topics last time round were those which were a bit off the beaten track. So here’s hoping it will go down well.

Geek/Girlgeek Dinners
I notice there are a couple of geeky dinners coming up soon. They seem to have shot themselves in the foot slightly in that they’re both on the same day! So, clone yourself or toss a coin to decided which of the following you’d rather attend on 21st February:

Unfortunately, I’m unable to attend either event as I’m already busy, but I will be keen to read any blogs about them afterwards. Please let me know if you write a review.

WSG London #3 - Accessibility
Stuart has put together another great programme for the forthcoming WSG meeting on 28th February. Now that’s one I will be able to attend, and am looking forward to what Anne McMeekin, Niqui Merret and Mike Davies have to say on the subject.