There are some aspects in the world of accessibility which are, at the same time, a bit inaccessible. In a first point of view, things can be percieved as accessible, but when thinking a little more, the whole thing doesn’t appear to be as accessible as it seems.
JAWS: an accessible software, an inaccessible price.
One example is the famous screen reader JAWS. This application is, with no doubt, a big help in accessibility terms, but the problem raises when talking about the software price. The fact that makes this accessible service inaccessible is the high price of the software. The Standard JAWS has a price of $895 (Reference: JAWS official website), an inaccessible price for a lot of people requiring this product.
Accessible code, inaccessible structure
A website can have the AAA certification. However, the problems can begin when a blind user uses a text reader to read the content of the web page. The fact of obtaining the highest level of accessibility from a validator doesn’t confirm this website is easy to read for a blind user. The internal structure of the code should be the optimal for a screen reader. This means, for example, not having a <div> which contains a long left menu before the <div> which contains the content. The reason not to do that is that the screen reader would read the left menu before (taking a lot of time) and the content afterwards which is, for the user, the most interesting thing.
Accessible map, but does it make sense?

When on the last Easter holidays I travelled to Roma I was amazed to see a map in S.Maria Maggiore square in Braile language. I first thought it was a nice initiative, but, is it useful for a blind person to have this information in this circumstances? I dont’t think so,…




