User:FGrose
Frederick Grose, MPH, CIH
Safe Use of the XO and Peripherals
At this point, my comments in the Safe Use of the XO and Peripherals section are aimed at raising awareness of the potential for content developers, teachers, & users to begin to culture an appreciation for preventive health, safety, & security by the way they plan and present their work.
It is difficult to interject a helpful thought about safety when attention is focused on another, more interesting or productive, activity. (How often do we breeze over the safety precautions included in owner's manuals—or even look at the manuals?!) While many believe that such precautions are only included to satisfy liability lawyers, safety and health educators look for single-point lessons that can be delivered at appropriately teachable moments.
For example, safety message icons are included as an insert page with the XO packaging, but these will be quickly lost or forgotten without some planned refreshing. The XO shutdown screen is one such reminder, as it displays the icons, but they appear only briefly, too quickly to do anything other than, perhaps, trigger the memory of an earlier lesson. Better would be the procession of the icons, perhaps while the XO is starting up, next to or in place of the dots that circle the symbolic child. Such a splash display would only be really effective if there were short, memorable, perhaps play-oriented cartoon lessons for each of the safety icon topics.
One or two of the safety lessons should be on the list of recommended, early activities for teachers and administrators during distribution and deployment of the XO. And one or two more lessons should be planned for subsequent days or weeks, so as to begin to develop a habit of briefly including safety, health, or security thoughts at the top of the agenda for any formal gathering of a community. This is an honest, safety first policy that gives permission and support for members of the community to discuss and resolve safety or security concerns.
In a similar manner, we should look for opportunities to help content and activity developers and deployers to integrate short, thoughtful, and effective reminders for users to avoid potential hazards in their play or work. For example, checklists provided to reviewers and testers should include items for code and activity safety.
[E-mail me] or use my discussion page.