So this chapter is basically about accessibility for blind people. I kind of had to laugh at the thought of a blind person planning a road trip. I know, not very pc – but there you have it. In any case, it seems to me that Trip Takers would be quite easy for a blind person to use. First of all, all of the navigation remains the same – once they know where it is they can get straight back to it – and the links are where they would most likely expect them to be. Secondly, there isn't a lot of information which needs to be read in-depth. Quick bursts of information and consistent styling should make for a quite blind accessible site really - and ironically.
As far as CSS goes – I'm a completely tableless web programmer and wouldn't do it any other way – so that's not an issue. I hadn't before considered ensuring that all of the text in the html file flows logically on the page. I suspect I do this anyway but will be certain to check for it in future.
'Skip to Main Content' is something that I would definitely implement in other sites – however with the likelihood of blind people using this site being so slim it would seem to just add unnecessary clutter.
'Make all content accessible by keyboard' – I'll need to look further into this when programming the site. It's an interesting point.
Don't use JavaScript – hmmm – I sort of think that the accessibility hardware/software should catch up. If we don't move forward with new technologies because of a few users than innovation will be thwarted. Sometimes my hardware stops being appropriate for the current software etc I use so I have to upgrade – it seems this should be no different for the blind.
No comments:
Post a Comment