- There's an awful lot of tables in Facebook. All those different boxes on the page with friend information, the Wall, the feed list, they're all tables. I'm not terribly au fait with accessing tables with JAWS, but it got quite annoying (I have my verbosity settings high) after a while.
- I am not a number!! There is, as some of you may be aware, nothing in the way of alt text for the pictures, instead it reads as a very long number. In effect you get a link to a person's profile through the picture, but you don't know who the person is because it's just a number....
- There's lots in the way of duplicate links on the page, because of the links on the feed, the Wall and Friends list. Hitting Ins+F7 gives a very very very long list indeed (often with many many numbers!)!
- When I put JAWS in "Say All" mode, it read from left to right across the page from the applications links, skipping out the picture in the middle to read the personal information. On a friend's page this made for very strange reading - going from "Events" to hearing what their religious convictions were!
I'm a novice JAWS user and maybe regular users would navigate round it quicker. On the other hand, not all assistive technology users are expert (think about how many people don't know how to use Word correctly but use it every day!) but most websites are easier to navigate because they are less dynamic and tend to have a more linear structure (if they're written correctly!). It wasn't impossible to navigate around the page, but it was quirky.
There's a lot to be said for social networking. I make use of it and I certainly do not wish to halt its progress, but I would like to see it easier to use for those who rely on assistive technology.
There are a some accessibility groups on F'book who are trying to improve the situation:
There are various other reports:
- State of the eNation report on social networking - which points out various accessibility issues.
- AFB Report on CAPTCHA images in social networking sites
The BBC's accessibility blog had an interesting point to make "we all need to consider ourselves as TAB (Temporarily Able Bodied) and then design accordingly. " It's good practice and I'd highly recommend any web developers to have some basic knowledge of screenreaders and take the time to hear how a website or application "sounds".