http://historiarum.org/2007/03/26/accessibility/ Thoughts on Digital Media and History Sat, 22 Nov 2008 06:40:39 +0000 http://wordpress.org/?v=2.6.3 http://historiarum.org/2007/03/26/accessibility/#comment-126 Karin Tue, 27 Mar 2007 22:39:30 +0000 http://historiarum.org/2007/03/26/accessibility/#comment-126 Listening to the screen reader read through the header graphics drove me up a wall too. I had trouble with the voice on the simulator...a little two robotic for my full comprehension. At first I wondered if the simulator had chosen the voice just because it was hard to listen to, but then recalled that the JAWS voice on a dislexic (sp?) co-workers computer sounded the same. Very frustrating. I found the stie to test the color properties of you site in Joe Clark's essay, but I'm wondering if there is anyway to test the readability of it without downloading the screenreader software. Listening to the screen reader read through the header graphics drove me up a wall too. I had trouble with the voice on the simulator…a little two robotic for my full comprehension. At first I wondered if the simulator had chosen the voice just because it was hard to listen to, but then recalled that the JAWS voice on a dislexic (sp?) co-workers computer sounded the same. Very frustrating. I found the stie to test the color properties of you site in Joe Clark’s essay, but I’m wondering if there is anyway to test the readability of it without downloading the screenreader software.

]]> http://historiarum.org/2007/03/26/accessibility/#comment-122 Mark Stevens Tue, 27 Mar 2007 00:53:13 +0000 http://historiarum.org/2007/03/26/accessibility/#comment-122 Ken, I agree with you about the need to take all of these issues into account when we design and program a site. These readings brought an even deeper understanding of how intricate and multi-layered web programming can be if you want to try to do it right. It is a time consuming process to make an engaging and accessible site. Ken,
I agree with you about the need to take all of these issues into account when we design and program a site. These readings brought an even deeper understanding of how intricate and multi-layered web programming can be if you want to try to do it right. It is a time consuming process to make an engaging and accessible site.

]]> http://historiarum.org/2007/03/26/accessibility/#comment-121 Misha Griffith Mon, 26 Mar 2007 16:19:18 +0000 http://historiarum.org/2007/03/26/accessibility/#comment-121 Ken, were you as baffled as I about the labels used in the screen reader exercise? We frequently use these one-word labels like "history", "contacts", etc. and expect them to be self-explanatory. Guess what, if the audience doesn't have the luxury of looking at and pondering all the choices, they can be confusing. It is amazing how much information we infer from context, rather than knowing for sure. When stripped of context, it really becomes a guessing game. I will be more carefull about labels in the future. Ken, were you as baffled as I about the labels used in the screen reader exercise? We frequently use these one-word labels like “history”, “contacts”, etc. and expect them to be self-explanatory. Guess what, if the audience doesn’t have the luxury of looking at and pondering all the choices, they can be confusing. It is amazing how much information we infer from context, rather than knowing for sure. When stripped of context, it really becomes a guessing game. I will be more carefull about labels in the future.

]]>