I’ll be speaking at this event in London on Thursday. It would be lovely if you could come along. It’s free!
These seem just about as reasonable as any other CAPTCHA.
This is a great initiative. I’m going to learn a lot from it. I hope that I might even be able to contribute to it sometime.
I think this is kind of brilliant.
An excellent tale of performance optimisation …complete with a coda on looking behind the numbers when it comes to analytics data.
An ever-timely call-to-arms from Eric:
Sir Tim Berners-Lee envisioned the web as open and accessible for everyone, no matter where they comes from, what speed their connection is, how capable their browsers are or how good their eyes or hands or both work. I feel proud every day to make that vision reality, and it is the job of web developers to make it a reality.
He’s right. We have tremendous power and privilege, and correspondingly tremendous responsibility.
A behind-the-scenes look at how Gov.uk is handling mobile devices. Spoiler: it’s responsive.
I found this particularly interesting:
When considering the extra requirements users of different devices have we found a lot in common with work already done on accessibility.
A worrying look at how modern web developers approach accessibility. In short, they don’t.
The low-hanging fruit of accessibility fixes; it’s worth bearing these in mind.
My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update) from James Craig on 2012-09-15 (firstname.lastname@example.org from September 2012)
James Craig is a mensch. This is how you give feedback to a working group.
Why mobile Web accessibility matters - best practices to make your mobile site accessible | mobiForge
There’s some great practical advice for building accessible mobile web apps here.
Bruce’s thoughts on the proposed inclusion of a “content” or “maincontent” element in HTML5.
Personally, I don’t think there’s much point in adding a new element when there’s an existing attribute (role=”main”) that does exactly the same thing.
Also, I don’t see much point in adding an element that can only be used once and only once in a document. However, if a “content” or “maincontent” element could be used inside any sectioning content (section, article, nav, aside), then I could see it being far more useful.
If you make inaccessible iOS apps, you really only have yourself to blame.
There are also some handy tips here for getting to know VoiceOver.
A really nice site dedicated entirely to making the web a better place for the colourblind.
Oh, this is just wonderful: a camera that outputs a text description instead of an image (complete with instructions on how to build one yourself). I love it!
A cautionary tale from Stuart. We, the makers of modern technology, are letting people down. Badly.
We’re in this to help users, remember: not just the ones who think as we do, but the ones who rely on us to build things for them because they don’t know what they’re doing. If your response is honestly “well, he should have spent more on a phone to get something better”, then I’m exceedingly disillusioned by you.
I can’t remember the last time I read something I disagreed with so fundamentally. This sums up the tone of the article:
Accessibility is not a right; it’s a feature.
I do not agree. I do not agree at all.
(Also, the pre-emtive labelling of anyone who may disagree with your point of view as defending a “sacred cow” is as tired and misguided as labelling anyone who disagrees with your viewpoint as a “fanboy”.)
Yes, yes, yes! This article does an excellent job of explaining what Captchas are attempting to do and why, therefore, they are so utterly shit.
This helps to clarify the difference between native semantics and ARIA additions.
This is a great response to my recent post about semantics in HTML. Steve explores the accessibility implications. I heartily concur with his rallying cry at the end:
Given some recent hand-wringing about the web as a “platform,” it seems appropriate to revisit this superb article from Ben. The specifics of the companies and technologies may have changed in the past year but the fundamental point remains the same:
Everything about web architecture; HTTP, HTML, CSS, is designed to serve and render content, but most importantly the web is formed where all of that content is linked together. That is what makes it amazing, and that is what defines it. This purpose and killer application of the web is not even comparable to the application frameworks of any particular operating system.
Andy responds to Joe Hewitt’s recent despondent posts about the web. I tend to agree with Andy: I think comparing the web to other “platforms” is missing the point of what the web is.
See also: http://benward.me/blog/understand-the-web
John reinforces the importance of universal access above the desire to build only for the newest shiniest devices:
Universality is a founding principle of the web. It is the manifesto the web has been built on, and I believe one of the key drivers of the almost unimaginable success of the web over these last two decades. We ignore that at the web’s peril.
A great opinion piece from Addy Osmani prompted by the panel discussion I took part in at the Update conference.
A great reminder from Bruce that we need to remember to use cutting-edge web technology responsibly.
Leonie points to a change in the semantics of the a element in HTML5 that could be very handy for accessible navigation.
A cute website that’s a call-to-arms against low-contrast text on the web.
Derek runs some tests on how screenreaders behave when block-level elements are wrapped in links, which is now legal in HTML5.
Ignoring the awful misleading title, this is a really good post from Paul on his personal experiences dealing with accessibility on one or two projects.
A superb post by Dan on the bigger picture of what’s wrong with hashbang URLs. Well written and well reasoned.
A nice succinct description of the placeholder attribute, with an emphasis on accessibility.
This consortium of institutions and universities came together “to provide practical solutions and expertise in digital preservation.”
PLANETS stands for Preservation and Long-term Access through Networked Services.
Tim Bray calmly explains why hash-bang URLs are a very bad idea.
This is what we call “tight coupling” and I thought that anyone with a Computer Science degree ought to have been taught to avoid it.
A great little jQuery script to automatically assign ARIA roles to HTML5 elements with the corresponding semantics.
Steven nails exactly why I’m so excited about the increasing diversity of devices accessing the web; not so that we can build more silos, but so that we can sure our content is robust enough for the multitude of different devices:
To be honest, I can think of a few, but not many use cases of web sites or apps which are or should be exclusively mobile. It seems like the Mobile Web allows us to revisit all of the talk of inclusion, progressive enhancement and accessibility from years ago.
The notes and slides from the talk Ann gave at the London Web Standards meetup in May.
This is an excellent idea: buy up a communications satellite and use it to provide free internet. I kinda wish it were a Kickstarter project though.
It'll be interesting to see how this service works out: people can report accessibility problems with any website, and other people can volunteer to help fix the issues.
A handy table of new HTML5 elements and whether or not they are exposed to assistive technology.
Think Vitamin have been their accessibility material available for free.
An emotionally affecting endorsement of the accessibility features on the iPhone.
The website of the Yahoo accessibility team.
A one-day event in London in September on the topic of accessibility, with a focus on motor impairment.
Steve Faulkner has created a petition to let Google know what screenreader users think of Chrome's appalling lack of basic accessibility hooks.
An API for Turing test questions.
A list of services you can use to get your podcast transcribed.
Test results for screen readers navigating content that uses new HTML5 elements and ARIA roles.
There is a doctype for HTML4 + ARIA but "This DTD is made available only as a bridging solution for applications requiring DTD validation but not using HTML 5."
An excellently written zero-edit change proposal from Edward O'Connor and others, refuting issues raised by Shelley Powers (I offered to help with this change proposal but I never followed through).
An excellent piece by Bruce on why the details element needs to be in HTML5.
A handy accessibility resource from Auntie Beeb.
Cute covers for Macbooks to give them that bookish look.
Your one-stop shop for ongoing accessibility work related to HTML5.
The results of the second screen reader survey from WebAIM are, once again, required reading.
Using Google Chrome Frame in IE will give users of assistive technology the same shitty to non-existent experience they would get in the actual Google Chrome browser.
A pattern library that considers colour blindness.
A hands-on account of the new accessibility features in the iPhone. Sounds like a great experience.
A forthcoming typeface designed specifically to help people with dyslexia read and write more effectively.
Wendy gives some commentary from her ringside seat at the theatre of HTML5.
Bert Bos's 2000 Treatise (published in 2003) is a must-read for anyone involved in developing any kind of format. "This essay tries to make explicit what the developers in the various W3C working groups mean when they invoke words like efficiency, maintainability, accessibility, extensibility, learnability, simplicity, longevity, and other long words ending in -y."
USA, Canada and the EU attempt to kill treaty to protect blind people's access to written material - Boing Boing
I feel a rant coming on...
This list of screenreader survey results is required reading. Conclusion: "there is no typical screen reader user."
An excellent rumination on the meaning of accessibility, prompted by real world experiences.
Prompted by the Bespin fuss, Derek shares his thoughts on *when* accessibility should be integrated into products.
Great article by Bruce defending the principle of One Web.
Stuart has an interesting take on ARAI attributes. Why can't they be set declaratively in an external file in the same way as we set styles?
Stevie Wonder talks about assistive technology. I think this finally proves that yes, accessibility *is* sexy!
Gez lays out the case for and against keeping the alt attribute mandatory in HTML5. If he's missed anything, add a comment.
A guide to using ARIA roles from the mighty Steve Faulkner.
A collection of tips, guidance, advice and practical suggestions in developing accessible websites
Joe has written a rousing call to arms on the state of online captioning. It's a lengthy article but well worth reading.
WCAG 2.0 has just entered proposed recommendation status. What a long strange trip it's been.
Apple have gathered all their resources about accessibility into one handy site. I sense the work of James Craig.
Call for Review: Updated WAI-ARIA Specification from Shawn Henry on 2008-08-06 (email@example.com from July to September 2008)
Shawn at the W3C wants feedback on the ARIA working draft, particularly "feedback on host language embedding, that is, how ARIA is implemented in HTML, XHTML, SVG, and other host languages." If you don't chime in now, don't bitch later.
A good overview of ARIA from the mighty Gez Lemon. There seems to be quite a bit of overlap with some HTML5 ideas here.
Sometimes Apple gets it wrong and Microsoft gets it right. That's certainly the case for users with low-vision.
Christian is using the prize money he won at Mashed to put on an event in London in September devoted to "ethical hacking": creating mashups to make social networks more accessible.
Excellent explanation of DRM by Mark Pilgrim, prompted by MSN Music's gunshot to the head.
The last piece is falling into place. IE8 has ARIA support, Mozilla has ARIA support ...and now WebKit is getting there. Excellent!
Ignore the attention-grabbing headline. Brothercake is something more nuanced here (and he's backing it up with examples).
There is an undocumented feature in Google Maps: add "&output=html" to the URL to get the accessible, non-Ajax version.
Joe's latest project is deliberately garish.
A free screen reader. If this turns out to be any good, it could be a game-changer: a long overdue kick in the behind for Freedom Scientific.
This is pretty freakin' awesome: an accessible interface onto Second Life.
Steve Faulkner gives a rundown of the current state of play between screen readers and Ajax.
Excellent research into how screen readers respond to empty links (i.e. A elements with no text between the opening and closing tags).
Remember the video of that Cadbury's ad I linked to a while back? It turns out that there's a transcript of the video on the website.
A new feature on Matthew Somerville's brilliant train timetable site. Just put /fares at the end of any URL to get the cheapest available fare.
It's easy for us to take technology for granted. This video shows how transformative technology can be. I am humbled.
Excellent news from the New York Times: no more charging for content. Finally, I can link to NYT articles from blog posts (and del.icio.us).
Yet another reason never to fly with Ryanair.
Notes from Joe's @smedias. Please read the whole thing before (mis)judging what he said.
Now this is what I call a captcha. You want to know about my mother? I'll tell you about my mother.
Sounds like Brighton is ready to become one big WiFi hotspot.
John McCain stole Mike Davidson's bandwidth. This sounds like a job for .htaccessman.
Aral has been busy whipping FlashAid into shape. Now let's get busy kicking the tyres.