denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Denise ([staff profile] denise) wrote in [site community profile] dw_accessibility2013-01-15 10:39 pm

Inaccessible websites?

I'm doing a talk on web accessibility at LinuxConf Australia and would like to give specific examples!

So, gimme your best examples of websites with specific accessibility problems that drive you nuts. Use of tabular data where it doesn't make any sense, sites with horrible contrast or that won't let you change font sizes, restaurant websites that are entirely flash-based, etc, etc.

Also, if anybody knows of good illustrative videos of a) people listening to a screenreader and b) people dictating to their computer, point me at 'em?
jeshyr: Blessed are the broken. Harry Potter. (Default)

[personal profile] jeshyr 2013-01-16 04:35 am (UTC)(link)
Ohh, Tumblr! There is a bizarre "fashion" I've only seen on Tumblr to make websites that have a sidebar that ends up ON TOP of the main text when I expand the web page in Safari with command-+.

The only example I can find right now is a NSFW blog although this particular page is PG rated - http://fuckyeahfrosthawk.tumblr.com/post/39650827372/a-hawk-unmade-imsorry-imsosorry-i-have

So initially when I press command-+ a bunch of times I see this:
https://www.evernote.com/shard/s56/sh/dbf65098-5157-45b3-ad96-f0da59fe78ed/f3d8353da2f604af276273bd8fbc0e74

The actual content image is way over to the right - the "You have heart" image on the left is the top of the sidebar. But when I scroll horizontally to see the content I get this:
https://www.evernote.com/shard/s56/sh/d0e825f1-06fb-4d69-a570-4ff4f58ca025/96084d827bef231d966a3717b648c718
There's no way to get the stupid sidebar out of the way except by manipulating the CSS with bookmarklets, etc. Luckily I am techy enough to do this, but it shouldn't be needed!!!

I've pretty sure that I've never seen this sidebar-on-top behaviour outside of tumblr. I suspect that one of the very early Tumblr layouts had this coded in and everybody since then has copied it or something - it's probably a good example of how a "small" accessibility mistake can snowball if it ends up in a much-copied layout!