Feed on
Posts
Comments

Today sees the next batch of Opera’s Web Standards Curriculum articles published bringing the total up to a very impressive 39.

It seems that this batch is especially dedicated to authors with doubled barreled names as latest additions include Accessibility Basics by Tom Hughs-Croucher and Accessibility Testing by Ben Hawkes-Lewis. Or maybe someone figured accessibility was be important or something…

Two new additions to the HTML section include Creating Multiple Pages with Navigatin Menus from Christian Heilmann and Validating your HTML from Mark Norman Francis. The CSS section also gets a whole lot of love with articles contributed from the likes of Christian Heilmann, Tommy Olsson, Ben Henick, Nicole Sullivan and Ben Buchanan. And there’s still more to come with the JavaScript section so stay tuned.

Web Standards Curriculum forum

If you have feedback or ideas to contribute then drop by the forums and tell people what you think. It would be great to hear about how the Curriculum is being used.

Translations

One of the problems with web standards is that so much is in English and not enough in other languages. If you’re a non English speaker and would like to get involved in helping translate the Curriculum have a chat to Chris Mills in the forum.

Supporting the Opera Web Standards Curriculum: Learn to build a better Web with Opera

Opera’s August State of the Mobile Web report confirms that it’s not just the web that is cross platform but also our browsing habits. While we saw in April’s report that 40% of traffic to the mobile web was to social networking sites, August’s report shows that we spend a significant amount of time browsing niche web pages in addition to the most popular ones.

I can relate to this entirely. Before I used Opera Mini I simply wouldn’t bother with some sites because they had too many links, no skip links, huge images, vast amounts of scrolling and so on. All this meant that getting to the content I wanted was a real effort. As a result I’d find myself sticking to the sites I had to use such as travel updates and possibly a bit of news.

Using the enhanced browsing features of Opera Mini I can comfortably access my social networking sites of choice to keep in touch with friends (so much so I use these more than texting) as well as catch up with cool stuff that I was previously restricted to doing on a desktop.

Take the image below for example that shows Facebook when viewed using WAP. Just at a glance it seems like (and is) a long list of links that are not easy on the eye and promises lots of laborious scrolling.

In contrast the image below shows Facebook viewed in a Opera Mini and renders just as you’d expect to see it on a web page. The zoom in and zoom out features mean that you can quickly jump around the page and find what you want.

(You can check out the difference for yourself by looking at your favorite site using the Opera Mini Emulator).

Now that we’re no longed restricted to the “walled garden” of a WAP browser, smaller sites are driving larger amounts of traffic making it really a one web experience. To ensure that your site isn’t left behind you need to make sure you have done what you can to build pages that work in all mobile and small devices using the W3C Mobile Web Best Practices. The added bonus of this of course is that if you do build pages with the mobile web in mind you’ll also be letting in a huge amount of other users such as people with disabilities as there is a strong cross over between the mobile and accessible web.

More on the mobile web and accessibility coming soon!

It all started in April at Accessibility 2.0 when Antonia Hyde, during her presentation on Rich Media for People with Learning Difficulties asked:

is it too much to have a multimedia player that people with learning disabilities can use?

A certain Flame Haired Warrior, Chris Heilmann, just so happened to be sitting in the audience about to present his own take on accessibility, Fencing the Habitat, in which he said the problem with accessibility was focused too much on stats and the business case and not enough on building solutions based on what real people want. Bingo, the start of a beautiful relationship that eventually gave birth to Easy YouTube.

What snowballed after that day has been well documented, with the latest outcome being an amazing couple of days organised by Chris called Scripting Enabled which took place over the weekend. The aim? Geeks talk to real people about what the problems are and then fix them.

So here’s what happened (all slides are available here).

The problems

Day one set out to discuss the issues that people face on the web and what people want to be fixed. The presenters all brought something new to the table and as Chris summed up at the end of the day “It’s rare to go to a conference and not be bored or have heard it all before”.

The reason why the day worked so well is because there was none of the usual utterings you get around accessibility such as it “…makes great business sense”, “…better search engine optimisation”, “…you’ll look all nice and fluffy” and so on. No, it was about hearing from people about their experiences on the web and getting to grips with their issues and not just those set out in guidelines.

Denise Stephens, from Enabled By Design, kicked off the presentations with Barriers faced by People with Changing Conditions (emphasis my own). Enable by Design is a social network Denise set up to support anyone looking to make adjustments to their lives through the use of assistive equipment. Denise herself has MS which brings with it a myriad of changing problems, such as vertigo, numbness in her hands, changing sight, hearing and mobility; all of which make her regular day to day activities a challenge. Denise really set the context for the day by flagging that accessibility is about real people not just standards and guidelines.

Kath Moonan from AbilityNet then rocked the floor (with a little help form Siouxie Sioux) with Why I hate the Interwebs. She showed some great videos of people navigating websites (filmed in AbilityNet’s shiny new User Testing Lab) illustrating barriers people face that fall outside of the Web Content Accessibility Guidelines (WCAG).

Her colleague Johan showed us just how problematic scrolling is for him when viewing web pages, an issue that got picked up on quite a lot in the question and answer session after. Custom Style Sheets were suggested as one answer but is problematic to implement as a person needs to know what these are and how to install them. It was also clear that there are issues with people not always knowing what is available in their browser to help them browse web pages. For example one neat solution for the problem of scrolling is using Opera’s Small Screen Mode (View> Small Screen) which removes scrolling altogether. Another is making easy to use custom style sheets that can be made available via the browser. This is something the RNIB Surf Right Toolbar is doing (and they’re very keen to hear from people what they want).

Problems flagged by Kath were re-emphaised by Antonia Hyde of United Response with Online Content for People with Learning Difficulties - Opening Doors. Again with the help of videos of people with learning difficulties we met Lizzie who, like many people, feels “singled out” by Web 2.0 and social networking API’s because she can’t figure them out. We saw how she struggled to navigate the cluttered interface of YouTube but found what she was looking for almost instantly on Easy YouTube. Antonia drove the point home that people with learning difficulties can learn; we just need to do things differently to support them. In fact a big ask of the day is that YouTube have a link to Easy YouTube for those that may want to use it.

After lunch Artur Ortega from Yahoo! and Leonie Watson from Nomensa discussed Barriers for Screen Readers and how JavaScript can help. So often people assume that JavaScript is the work of the devil when it comes to accessibility when really it’s not when implemented correctly. Unfortunately the internet said “No” to Artur showing us his pre-prepared websites so we weren’t able to see the JavaScript examples he’d  pulled together but these are now available on the Scripting Enabled blog.

Last up was Jonathan Hassell of the BBC who did a joint presentation with Phil Teare on Dyslexia Barriers. They looked at how Web 2.0 is about people contributing text online via blogs, forums, comments and so flagging how writing text in public forums is uncomfortable for many people with dyslexia. Easy solutions are providing spell checkers, preview options in forms and the opportunity to change text. This also made me think about a new checkpoint in WCAG 2.0 that focuses on Error Handling; something that is never given enough consideration.

Lack of control over the page and being able to view pages as you want is a huge problem. Giving people the option to personalise pages and choose colours, fonts and content is a great way round this. Personalising websites that you are signed up to is also great for people who are working on shared computers and can’t easily change system and browser settings.

We wrapped up with an excellent panel from some of the day’s speakers including Jonathan Hassell, Kath Moonan, and Artur Ortega, as well as freelance accessibility consultant and developer Ann McMeekin.

Ann, coming very much from the design perspective, summed up neatly how accessibility should be seamless and not hived off into a separate solution by describing a set of stairs she had photographed at the Brunswick Centre. Rather than placing a traditional ramp next to the steps the ramp is integrated into the steps themselves making them, in my opinion, much more aesthetically pleasing as well as accessible.

Seamless design of a ramp into stairs in London's Brunswick Centre

The fixes

Day two was about taking some of the ideas from day one and brainstorming and hacking. Some of the stuff being worked on included:

  • Longplay Wiki - a wiki that includes videos of how people with disabilities get around certain problems they encounter for others to benefit from; a bit like Video Jug. Even if it’s not a wiki there could be a YouTube group set up for it. Roger Wilson Hinds (creator of the free open source screen reader Thunder) suggested the group could be called YouTwo. Having it all available in Easy YouTube would round it off perfectly.
  • Accessible WYSIWYG editor - I don’t know of one organisation who isn’t struggling to find a fully accessible Rich Text Editor for their content management systems, blogs or forums. Having the community come up with a solution that can then be used universally would remove big headaches that organisations committed to accessibility are facing.
  • Screen part highlighter - David Owens got stuck into making a highlighter so that the user could highlight only the part of the screen that they wish to look at while the rest is greyed out. This would help many a person who finds overcrowding on a page and overuse of animated images a problem. I love the idea of having a virtual set of binoculars so you can zone in on the bit you want.
  • Custom CSS for zooming - picking up on the custom CSS idea Caz Mockett began creating a CSS file that you could save as a bookmarklet or via GreaseMonkey to change the way pages look.
  • Google Maps - using the Easy YouTube concept Jon Gibbons (aka Dotjay), Ann McMeekin, Marco Ranon and Andy Ronksley started look at ways to make bigger buttons and improve navigability. They’re still working on this but will be releasing the URL soon.

These were only some of the hacks being worked on during the day. Others including microformats and marking up accessible buildings, further work on Easy YouTube, talking Gutenberg, easy ways to distribute GreaseMonkey scripts, mashing up Lonely Planet with ordinance survey maps and Twitter walking instructions are all written about on the Scripting Enabled wiki (see below).

What you can do

The key now is to make sure that the momentum established over the last couple of days is kept up. Whether you are someone using the web who has ideas or a designer, developer consultant or just about anyone with an interest in accessibility there are a number of ways to get involved:

  • Join the Scripting Enabled mailing list - whether you have ideas around what you want to see changed on the web or are someone who can hack these changes get involved. This is all about getting the geeks to talk to the people who need things fixing.
  • Check out the Scripting Enabled wiki - this is where you’ll find outlines of what people are working on, what people are thinking and how you can contribute.
  • Run a Scripting Enabled event - Chris is more than happy for the format of Scripting Enabled to be run elsewhere. Already Stanford University are doing one so why not do one of your own? The more the better.
  • Use the tag “scriptingenabled” - the more we talk about Scripting Enabled and what it is and get more people involved the better. So use the tag on Flickr, Youtube, Yahoo Video, Vimeo, Blip.tv, Yahoo Live, Magnolia, delicious, blogging, twitter, Facebook everything.

And finally

Interestingly just this morning I read one of Justin Thorpe’s latest blog posts Has the Web Standards and Web Accessibility Movement lost its Mojo?

It really seems like all the excitement around things like Web standards, Web accessibility, microformats, and such has stopped completely…Is this good? Have we achieved success? Is the world accessible and standards compliant… or have we just become incredibly complacent?

What’s changed is that web standards and accessibility are no longer at a point where they have to be explained and sold to every web professional and organisation with a website. In the UK at least there is a good awareness. As one person commented on Justin’s blog web standards and accessibility has gone from “being sexy to being professional”. But what we do need are more visible solutions out there.

Over the last couple of days I saw just how many super skilled people are out there who know what they are doing and just how much can be achieved when they work together. It’s these people that need to be talking to real users, hacking solutions and putting them out there. That way web standards and accessibility gets life breathed into them that goes beyond guidelines and checklisting.

Christian certainly achieved in the two days what he set out to do: to give the accessibility community a swift kick up the backside. The overall message is loud and clear: keep talking, keep hacking and most of all keep sharing. The more we work together and pool our knowledge the faster things will change.

All presentations were filmed by BBC Backstage with transcripts sponsored by Opera so stay tuned for these; I’ll post a link when they are available. And finally don’t forget to vote for the Flame Haired Warrior in the Standards Champion category of the .Net Awards 2008.

Hello Opera

After six amazing years at RNIB I have decided that it is time to move on and try my hand elsewhere. It’s been both challenging and rewarding working as the Senior Web Accessibility Consultant in such a diverse organisation and I have been fortunate enough to work on some fantastic projects with equally amazing people.

As my career has evolved I have come to see web accessibility as a key piece of a bigger picture leading me to expanded my interests into making websites work for international audiences, mobiles platforms and other browsing technologies. Hence the reason for this blog coming about; I wanted to discuss web accessibility within the bigger picture and not as an add-on or plug-in.

When I started looking elsewhere it was hard to envisage making a move from charity to corporate sector, I wanted somewhere where I felt my beliefs would not be compromised and where I could have an opportunity to be part of something that will contribute to wider change and a better web. All very worthy I know (she says shaking her new shiny Norwegian tambourine) but that’s what is important to me.

Introducing Opera

As of next week I will be joining the team at Opera Software as their new Web Evangelist. As Opera is all about web standards and the open web this move allows me to do all that I have wanted and more. Additionally I will also be joining a crack team that I’m really looking forward to working with including:

  • Chris Mills, Developer Relations Community Manager, keeper of the Web Standards Curriculum (a must read) and incredibly tall person who very sweetly bends his knees when he talks to me
  • Bruce Lawson, Web Evangelist and leading UK accessibility advocate who’s jokes are legendary (and you have to laugh at because he is a purple belt)
  • David Story, Chief Web Opener, and keeper of Dragonfly, Opera’s developer tool
  • Andreas Bovens, Web Evangelist and Japanese copyright expert based in Japan
  • Cheah Zi Bin, Web Evangelist, who I’ll be spending October with on the China leg of the Opera University Tours
  • Lawrence Eng, Product Research Manager, who talks to people and figures out how to make My Opera rock

What we do

The one question that people keep asking me is “What does a Web Evangelist do?”. I’ll be able to tell you more after I’ve started but some of the sorts of things I’ll be looking at doing are:

  • Working with web developers to help promote the adoption of web standards
  • Working with standards bodies such as W3C to input into guidelines and standards such as WAI ARIA, HTML 5, accessibility and cross overs with the mobile web
  • Blogging on the Opera Developer Network blog and writing articles for Dev Opera and other websites and publications
  • Talking about the world’s most popular mobile platforms Opera Mobile and Opera Mini
  • Conference speaking around the world

What’s really great is that Opera will also support me in my work leading the WaSP International Liaison Group as well as participating in WAI’s Education and Outreach working group. I’ll be based in London but on the road more often than not travelling the world talking to folk about standards in general, accessibility and mobile web best practices.

And finally…

I will miss the Web Access Team terribly. They’re a talented, passionate bunch who for a team of (soon to be) three are doing amazing things. The team is stronger now than it has ever been and I know will go from strength to strength. I’ve learnt a lot from them and other people at RNIB as well as our clients and their teams. Hat tip to all of them but especially Bim Egan who has taught me more than she will ever know.

Hopefully see you all on the road.

In a recent article in the UK’s Guardian How CAPTCHA was foiled: Are you a man or a mouse?, CAPTCHA was reported as being “broken” and as Wordpress’s Matt Mullenweg described it “the bane of the internet”.

I couldn’t agree more. These distorted images of text designed to prevent anything but a human register for a site, leave comments on blogs and so on, are essentially flawed as they are problematic for most people to use and impossible for a screen reader user to access. To my mind they serve as a superficial rather than actual security solution and succeed in nothing but turning real people away. They really are the Internet equivalent of an unfriendly bouncer working the door.

Like the ill-fated dodo CAPTCHA seems to have really lost it’s ability to go anywhere. There are so many ways of cracking CAPTCHA, either automated or human, that they are beginning to pale as a defendable security solution for a website. In fact the only thing that I can see being argued in their defence is that they keep the numbers of spammers down even if they don’t keep them out altogether; hence why sites such as Google, Yahoo!, and Hotmail keep using them. Even this is becoming questionable however. Just as the dodo became extinct as a result of coming into contact with humans so CAPTCHA seems to be losing it’s battle with spammers especially as they are using not just automated techniques but also people in sweatshops diligently breaking CAPTCHA’s manually.

What follows CAPTCHA?

The ineffectiveness of CAPTCHA has been discussed by many people in the web industry, not just accessibility advocates (see the Links section below). This being the case why are we all still battling with CAPTCHA’s on a daily basis? The problem to me is not just that there is no accessible and usable version of CAPTCHA’s but that there is nothing that can replace CAPTCHA’s altogether. The fact that they seem to keep the volume of spam down for website owners, even if they don’t prevent spam entirely, is also a reason why so many website owners are in no hurry to remove them.

What really needs to happen is some sort of industry collaboration where issues around security and spammers are tackled collectively and an industry standard is developed that can replace CAPTCHA. By this I don’t necessarily mean an accessible alternative to CAPTCHA but a replacement of the CAPTCHA concept altogether; specifically one that does not put the burden on the user in the way that CAPTCHA does. It’s an industry problem after all so working collaboratively makes sense. Already we have solutions such as Microsoft Passport or OpenID but even these don’t seem to have replaced CAPTCHA altogether. Until we find something viable to replace CAPTCHA we may find ourselves stuck with this increasingly ineffective security measure that does nothing more that sideline real people.

So what do you think folks, is CAPTCHA going the way of the dodo?

Links

« Newer Posts - Older Posts »