Inclusive New Media Design is a research project which aims to identify the best ways to encourage web designers and developers to build websites accessible to people with Intellectual Disabilities. In a hugely interesting first session I heard Simon Evans talk on the whole question of defining intellectual disabilities and how ID users use and interpret the web. I must confess it was not something I knew a great deal about but Simon holds a wealth of knowledge in this area and was very good at communicating it.
During the first session we looked a few of the sites available to ID users and how symbols form a key part of being able to use and interpet the web. A few of the providers include:
You can see how symbols are used at Symbol World. The idea is that words are associated with symbols making them easier to understand for ID users. Symbols are not free though - they come with a commercial license making it difficult to create parsers, bookmarks or browser extensions without paying a huge fee.
During the workshop Lisa Haskel mentioned she had created a script to pull images from Yahoo’s image API to show images for words. Could this be a viable alternative for symbols or could a simliar technique be used to convert pages into ID friendly symbol based pages? For now it seems licensing makes the symbol approach a non-starter but it certainly is possible to call an API for words and get images back.
In the spirit of releasing early and often here’s an alpha release of the idea. The script sends an AJAX call to Flickr’s API and gets a response for each of the words in the sting submitted. This is then written to the page via some DOM scripting. Nothing amazing at this stage but it is more about the idea.
You can see the example here (Firefox only at the moment) and download the source code here. It is released under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License so feel free to build on it if you wish.
At this stage it would seem to work very well for nouns but not so well for other words.
In terms of a feature list I can see the following being useful:
I’m not sure all of these ideas are in line with licensing but we’ll have to see. Hopefully a few more ideas will come out of the next workshop and from ID users there too.
What do you think? Is this a total non-starter or is this worth persuing?
Have an update or suggestion for this article? You can edit it here and send me a pull request.