http://www.washington.edu/accessit/articles?206
This link supports what we have been discussing in class for the last few weeks. Software created for the purpose of education needs to adhere to certain standards for accessibility. Keyboard access, color coding, use of pointing devices, flashing items, textual displays and other items all have standards that should be adhered to for universal design. The above link actually has links to several different resources. The one resource I read the most was the Guide to Standards that outlines what to do to accomplish universal design.
As someone trying to create quality educational curriculum software, I want to memorize and adhere to as many of these guidelines as possible so the most people can benefit from my software. Some of this stuff I have never thought of and some are pretty obvious. I hope this helps you all that plan to use software in your endeavors.
Subscribe to:
Post Comments (Atom)
1 comment:
Excellent point! I actually worry about this with my kids. In my class , we use specific verbage and universal signals. We follow certain pre-established guidelines for color coding, pointing devices, textural displays (even praise-based phrases). My kids have learned according to these constants and I don't want to see their progress diminish because their next teacher does it differently. I am pleased to know that there is a guide of these industry standards.
Thanks,
Elizabeth
Post a Comment