The Blind Shooting The Blind ∵ Stephen van Egmond’s weblog
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.
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.
That Scott is one smart cookie. He has come up with a workaround (using the accelerometer) for that annoying Mobile Safari orientation/zoom bug that I blogged about recently.
I still want Apple to fix this bug as soon as possible—the fact that such smart people are spending so much effort on ingenious hacks shows just how much of a pain-point this is.
This helps to clarify the difference between native semantics and ARIA additions.
It’s funny and heartbreaking because it’s true.
A great reminder from Christian that making JavaScript a requirement for using a website just doesn’t make much sense.
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:
Get involved!
A very even-handed look at the time and data debacle in HTML5.
A single-serving website expressing the frustration and bewilderment at Hixie’s unilateral decision to drop the time element from HTML.
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.
Accidental camera drops serve a purpose as part of a larger narrative.
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.
The threat to Google Videos shows businesses are not suitable cultural custodians — they can’t be held accountable to the public.
Freaky stuff. If you’ve seen Kevin Slavin or James Bridle talking about the increase in property prices on Wall Street as the buildings get closer to the network hub …that’s nothing—these are the new centres of world power; places where the speed of light interferes least with the speed of transactions.
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.
A fantastically detailed look by Michael at the evolution of the design of Chewbacca.
Google reaffirms its commitment to net neutrality ...except when it comes to wireless broadband, of course, because that's *totally* different, right? This disgusts me.
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.
Download Calexico live in Nuremburg, licensed under a Creative Commons attribution non-commercial share-alike license.
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."
I feel a rant coming on...
If you've ever broken/strained a limb, you'll know how tedious it gets answering the inevitable "what happened?" question time and time again.
My representative in the European Parliament is full of WIN!
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
The official website of the Obama-Biden presidential transition team is switching over to using a Creative Commons attribution licence. This bodes very well indeed.
This bodes well: "President-elect Obama appointed Kevin Werbach, assistant professor of legal studies and business ethics at Wharton, and Susan Crawford, who teaches communications and Internet law at the University of Michigan, to co-chair his FC…
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.
An in-depth look at the intersection of JavaScript and screen readers, concentrating on events in particular.
Holy crap! A ZX Spectrum emulator built entirely in JavaScript. I cannot adequately describe the Proustian sensation I get from playing Manic Miner in a browser.
Download a PDF of PPK's slides from his JavaScript workshop at Fundamentos Web. There's some good advice contained therein.
Apple have gathered all their resources about accessibility into one handy site. I sense the work of James Craig.
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.
A seriously nice recipe sharing site. Everything is creative commons licensed and everything looks delicious.
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.
Blogging can be hard. Here's some free relief. Sure, it's a shameless commercial promotion but it's kind of cute.
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.
The typography on this page is simply gorgeous. And the event looks good too.
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.
Tiki Bar TV's Johnny Johnny saves a woman from being killed on the New York subway. This is incontrovertible proof that outlandish cocktails can make you superhuman. Seriously though... bravo, Johnny Johnny, bravo!
Excellent research into how screen readers respond to empty links (i.e. A elements with no text between the opening and closing tags).
You can sign up to February's SemanticCamp by pointing it to a URL with an hCard (or FOAF). Nice.
David follows up on my talk at St Paul's with cornucopia of thoughts and links that's more in-depth than the talk itself.
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.
This is the plain vanilla look.
You can subscribe to the RSS feed of links.