Pharmacie sans ordonnance livraison rapide 24h: acheter viagra en ligne en France.

File://e:\documents and settings\george birbilis\desktop\conviv

Design for All and Assistive Technology for computer science and design students In this article I outline my background in teaching and conducting research on "design for all" and assistive technology. I then discuss definitions of these two terms, which are not straightforward, and present some of the arguments for including them in computing and design curricula. Finally I present a number of exercises that I have successfully used in teaching these topics with undergraduate and graduate computer science students and web design students. I am currently professor of human-computer interaction (HCI) in the Department of Computer Science at the University of York in the United Kingdom [43]. In the department we teach a number of undergraduate degrees in computer science. Students studying either a degree in Computer Science or Computer Science with Mathematics take an introductory course on the design of interactive systems in the second year of their course. This course includes a component on "design for all" (DfA) and assistive technologies (AT). We also have a taught Masters degree for students with only a limited computing background (MSc in Information Technology); this degree has a similar introductory course on the design of interactive systems with a DfA/AT component. Both undergraduate and MSc students undertake a research project as part of their degree, and projects on the design of interactive systems, many of which concern DfA/AT topics, are always popular. In the 2008/2009 academic year we will launch a Masters degree specifically on the design of interactive systems which will have a substantial DfA/AT component. My original training was in psychology, culminating in a PhD in cognitive and experimental psychology. I subsequently became interested in how people interact with computers and why they have such difficulties in doing so. In order to understand more about the computer side of human-computer interaction, I took a year out of my academic career to return to being a student and took a Masters degree in computer science (very similar to the MSc in IT on which I now teach at York). Then, quite by chance, I was introduced to the use of computers and other new technologies for disabled people, initially for people with visual disabilities. That research and teaching topic has continued to be my passion for the last 12 years. My first research efforts on computers for visually disabled people were on access to the then new Microsoft Windows graphical user interface [32], [49]. I also worked on one of the first personal navigational systems for visually disabled and elderly people, the MoBIC system [29], [40]. I have always been influenced by my background in psychological methodologies, and have tried to bring rigorous design of user requirements and evaluation studies and appropriate statistical analysis of data to the design and evaluation of technologies for disabled and elderly people [20], [27]. More recently I have conducted considerable amounts of research on the accessibility of the World Wide Web for people with disabilities [8], [18], [28], [30], [31], [38], [39]. My research team conducted the two largest and most detailed studies of web accessibility to date [8], [31]. These studies went beyond the standard methodology of testing websites for conformance to the Web Content Accessibility Guidelines (WCAG) [46], to investigate whether websites are usable by people with disabilities and the relationship between conformance, accessibility and usability. This work has lead to several projects that have involved teaching professional web developers about web accessibility. In a project for the U.K. government's Culture Online accessibility. In a project for the U.K. government's Culture Online Initiative, funded by the Department of Culture, Media and Sport [5], we conducted twelve workshops on web accessibility for web teams who were receiving funding to produce innovative web-based applications. In the EU-funded Tenuta Project [41] we have been providing a similar workshop to web teams funded by the eTen Initiative [12] designed to help the deployment of telecommunication networks based services (e-services) with a trans-European dimension. The importance of teaching Design for All and Assistive Technologies It is perhaps important to outline the reasons why courses for computer scientists, designers, and students in related disciplines should include a component on DfA and AT. The arguments may be necessary to persuade colleagues of the importance of these topics, and may be an important part of the curriculum on these topics, as students may in the future need to persuade managers and colleagues of the importance of considering these topics in designing and evaluating technologies. However, before addressing these topics, I will address the issue of the definitions of DfA and AT, even though I have been blithely using these terms in this article up until this point. Definitions of Design for All and Assistive Technology "Design for all", "accessible design", "inclusive design", "universal design" and "universal usability" are all terms that have been used in recent years to convey a focus on: "the design of products and environments to be usable by everyone, to the greatest extent possible, without the need for adaptation or specialised design" [3] However, as Vanderheiden and colleagues have noted [44], [45], there are probably as many definitions of these concepts, as there are people discussing them, and considerable misunderstanding. A particularly misunderstanding is that Design for All (DfA, the term I will use to cover all these terms) requires systems that will be usable by every user, regardless of capability (it is not a surprisingly misunderstanding, given the literal meanings of many of the terms), and that to attempt to achieve this might seriously compromise their designs. Yet the reality is much more complex and interesting and it is important that students, as future HCI professionals, realize this. Definitions of assistive technology (AT) are often very general and in some situations seem unhelpfully broad. For example: "Assistive Technology is any product or service designed to enable independence for disabled and older people." (King's Fund Consultation, 14th March 2001) [17] The problem is that one person's mainstream technology might be another person's AT. So if I use a miniature voice recorder to make my shopping list because I cannot see well enough to write one (or read it later), does that make a voice recorder an assistive technology? Undoubted the answer is yes. So any definition needs to be contextually grounded. One potentially useful way of conceptualizing DfA and AT is in terms of the proportion of a potential user population who are able to use a product or system. We should try to design mainstream products and systems so we make them accessible to and usable by the largest possible proportion of users, given constraints such as cost, complexity and good design decisions. Thus, computer operating systems and web browsers include options to allow visually impaired users to increase font size very easily up to a certain size. This will be sufficient for many users with mild to moderate visual impairments. For users with more severe visual impairments, ATs such as screen magnification and screen reading programs provide access and usability [33]. DfA is concerned with increasing the user proportion as much as possible and not impeding the use of ATs by those users who much as possible and not impeding the use of ATs by those users who cannot be included in the mainstream user proportion for a particular system. This latter point is important educationally - at the very least, developers of the future should be aware that their designs should allow ATs to function appropriately. ATs can also be thought of as bridging two distinct "gulfs of accessibility" [27]. Firstly, providing access to and use of the ever-burgeoning range of new technologies that citizens in the information and knowledge society need or want to use. Secondly, ATs can bridge the gulf of accessibility created by a person's disability and the organization of society in general. Thus for visually impaired people, the inability to read signs in the built environment is a major problem, but only because modern societies chose to create highly complex built environments full of printed signs (we might have developed technologies to have spoken and musical signs instead, in which case hearing impairment people would be handicapped rather than visually impaired people). But personal navigation systems with map and point of interest information are now being developed [29], [40], [42] to help visually impaired people negotiate the built environment more easily. I will now consider the various arguments for undertaking and also for teaching DfA and AT. In developed countries, between 12 and 20% of the population have a disability sufficiently severe that it may affect their interaction with technology [25]. Many people optimistically believe that with increasing medical advantages the proportion of the population who are disabled is decreasing. Unfortunately, modern problems such as car accidents, and medical advances that enable lives to be saved after serious trauma and illness, mean that this is not the case [16]. The increasing longevity of the population is another important factor. The proportion of the population who are elderly is currently increasing globally, and age is the principle cause of disability. For example, by the year 2030 one third of the population of the European Union will be over the age of 60 [14]. Of particular important for the development of AT is that as the proportion of older people increases in society, so the proportion of younger people decreases. So, over the next 50 years there will be fewer and fewer younger people to care for older people, so older people will need to remain more independent and care for themselves and each other more than previously. Numerous countries now have legislation that protects the rights of people with disabilities. For example the USA has the Americans with Disabilities Act (ADA) [1], Australia and the UK each have a Disability Discrimination Act (DDA) [6], [7]. Legislation may cover rights of access to technology directly or indirectly, particularly via access to goods and services. For example, there have been a number of legal cases concerning accessibility to information or services via the Web. In Australia, the Sydney Olympics Organizing Committee was successfully sued by a blind person because their failure to make their website accessible. In addition, the European Union has emphasized the importance of DfA and AT, funding research programmes in this area and including these topics in plans such as the eEurope 2002 and 2005 Plans [11], [12]. In many ways the economic argument flows from the demographic and legal arguments. With increasing participation of disabled and elderly people in society, partly due to legal and technological developments, the market represented by these groups is growing rapidly. The Disability Rights Commission in Great Britain estimates that the spending power of disabled people in their country is 50 billion Pounds (approximately 74 billion Euros) per annum [9]. From the demographics, it is clear that product and system developers might increase their market by at least 10% by adopting a DfA approach (assuming that such an approach might make their product or system usable by half the disabled population, the other half might need AT to access the product or system, a very conservative estimate). It may seem unnecessary to evoke a moral argument, but it is puzzling in an age when it is unacceptable to discriminate against people based on their race, gender or sexuality, that it seems acceptable for developers of products and systems to says disabled people will not want to use our system or will not be able to use it. Yet I have heard this argument many times in boardrooms and classrooms. There may be situations in which it is indeed impossible to make a particular technological solution accessible and that an AT or non-technological solution is required. However, computer scientists and designers should regard it as part of their professional challenge to provide solutions for disabled and elderly people, rather than simply discounting them. It is well-known that solutions designed with disabled people in mind often turn out to be very popular and usable by non-disabled groups. Recent examples include the British Telecom (BT) Big Button telephone [2] (the most popular telephone BT ever produced, and still for sale) and Good Grips kitchen utensils [26] were developed with elderly and disabled people in mind, but became extremely popular with mainstream markets. In the area of web accessibility, in our research for the Disability Rights Commission [8], we found that websites which were highly accessible were also 35% faster for non-disabled users to interact with, an astonishing efficiency saving. Useful Exercises in Design for All and Assistive Technology In this section I will outline some of the exercises that I have used in teaching DfA and AT in a range of contexts (see above), commenting on their effectiveness and the practicalities of organizing them. Often I find that educators in computer science and design are nervous about including these topics in their courses because they fear that they are not sufficiently expert in the topics to teach them. This is very unfortunate, as there are many resources, both electronic and human, that can be used to support teaching in these areas. I have always found that both students and other staff involved in these exercises find them interesting and enjoyable as well as informative. One of the problems we must overcome is that most computer science and design students and indeed most developers of new technologies are young and able-bodied and have no experience of the problems encountered by disabled and elderly people, either in life in general and in using technology in particular. However, there are many interesting and revealing exercises that can be undertaken to gain some insight into these problems and live as a disabled or elderly person. While it must be emphasized that taking part in such exercises is interesting and revealing, it is not the same as having that disability or characteristic of aging. For example, turning off one's computer screen and trying to use it with a screen reader is an interesting and informative experience, but the average blind person brings a lifetime of experience of interacting with the world non-visually, so their experience with a screen reader are very different from those of a sighted person. Many organizations of and for people with disabilities run provide awareness training courses and might be prepared to run a special version of such a course for a group of students. If not, a teacher might be able to take a course with their local organization to gather ideas for exercises with students. Many of these organizations also produce brochures and factsheets about the disability and how to interact with people with this disability that can be useful sources of information. For example the Royal National Institute for the Blind in the UK produces brochures on how visually impaired people use technology [34], how to guide visually impaired people [35] and how visually impaired people do everyday things [36]. Some of the many experiences of being disabled or elderly that students (and teachers) will find interesting and informative include: borrowing a wheelchair and get students to spend time in the chair trying to access library bookshelves, computer terminals, automated banking machines etc. creating simulations of different forms of visual impairment by cannibalizing borrowing or buying a long cane and have students wear very dark/ cannibalized sunglasses to simulate visual impairment (see b) and guide each other in public places - get students to observe how much clutter there is in the environment, what it is like to negotiate that environment and how other people react to them. Creating a "third age suit" [4] with thick gloves, a neck pad, padding for elbows, ankles etc. Ask students to do everyday and computer-based tasks wearing the suit. downloading demonstration versions of screenreaders such as JAWS [15], screen magnification programs, software for dyslexic readers, scanning software (and their associated manuals). Ask students to learn how to do simple tasks with these programs. Discussions and demonstrations with disabled and older people To understand the needs of disabled and older people in relation to technologies, one of the best initial exercises is to host discussions with disabled and elderly individuals who are interested in technology. One might make contact with such individuals through the local organizations of and for disabled and elderly people and through the computer groups they may well run. People are usually very pleased to be consulted about their views on technology, if approached in an appropriate manner. If people are users of ATs, it is very useful to ask them to give quite a detailed demonstration of how they use the AT. No only does this break the ice in the discussion, but allows students to see AT in real use, often by an experienced and expert users. Nor is there any need to be nervous about asking questions about people's experience of disability - if approached politely, people are usually very interested to talk about their lives and share these experiences with others who are genuinely interested. Such discussions should also be a two-way interaction, with students and teachers being honest about the difficulties of understanding the needs of different user groups and the ATs they use. Students and educators should also make the discussions an interesting experience for the disabled and older individuals, introducing them to the material the students are learning and how DfA/AT fits into the curriculum. If it is not possible to arrange live discussions with disabled or elderly people, it may be possible to find videos of disabled and elderly people talking about their experiences with technologies [24], [48]. There are also a variety of case study materials available on the Web about people's use of technology in general [13] and the WWW in particular [47]. For educators who wish to gain a more detailed knowledge and students who want to undertake in-depth work, such as research projects, reading autobiographies and memoirs of people with the relevant disabilities can be very informative. For example, there are numerous autobiographies of blind and visually impaired people that can assist in understanding their experiences [19], [21], [23], [50]. Design exercises with disabled and elderly people Having understood something of the experiences of disabled and/or elderly people, it can be very informative to then undertake design exercises for, but preferably also involving, some of these user groups. In a 10 week introductory course on HCI, I have successfully used small group projects in which students go through the different phases of the user-centred design lifecycle (user requirements - design - prototype - evaluation) adapting a familiar product so that is more suitable for a particular user group. If the instructor does not have access to a group of people with disabilities to take part in this type of exercise, it can be undertaken very easily and successfully by type of exercise, it can be undertaken very easily and successfully by focusing on elderly people as the target user group. Inevitably, some students will have elderly relatives who will be able to participate in the exercise. It is far easier with introductory students to undertake a re-design exercise of a familiar product rather than undertake a new design exercise. However with more advanced students, a more ambitious project such as the initial design of a new assistive technology for a particular disabled or elderly user group can be undertaken. It is interesting that undertaking a design exercise for a disabled or elderly user group not only introduces students to the complexity of DfA and AT, but also highlights many of the issues of user-centred and participatory design. If a design exercise is undertaken with more familiar users as the target user group, students can often skip performing user requirements seriously, because they think they understand the needs of users. Using a target user group whose needs are so unfamiliar can focus their minds on the importance of eliciting user requirements and conducting evaluations properly. I have involved disabled and elderly people in these group projects and had a final conference style session in which the students present their projects to a panel of disabled and elderly people and members of staff. This exercise serves a number of useful purposes. It shows that the group projects are a serious part of the course (I have offered small prizes for the best project). It develops presentation skills in the students, makes them consider how to present to a non-technical audience, and sometimes to n audience with members who cannot see. It also shows to the disabled and elderly people that we treat this work seriously, and lets them see how the discussions and interviews they might have undertaken with students were used. DfA and AT are important topics to include in courses for computer science and design students. Educators may seem daunted by the prospect of teaching a topic in which they feel they are not expert, but there are many interesting exercises that can be undertaken that allow both teachers and students to deepen their knowledge and skills in these areas. Burgstahler, S. (2004). Universal design: principles, process and application. Cook, S.E. (2005). Designing for the third age. Accessible Design in the Digital World: Where Theory and Reality Collide; whereas ideas and practice merge, 23-25 August, Dundee, Scotland, 1-13. Disability Discrimination Act. Australia. Disability Rights Commission. (2004). The Web: access and inclusion for disabled people. London: The Stationery Office. Disability Rights Commission. (2006). Information for employers and service providers. European Design for All eAccessibility Network. Everyday lives. Freedom Scientific. Demonstration versions of JAWS. Fujiura, G.T. (2006). Emerging trends in disability. Population Reference Bureau. Harrison, C. and Petrie, H. (2006). Severity of usability and Harrison, C. and Petrie, H. (2006). Severity of usability and accessibility problems in eCommerce and eGovernment websites. Proceedings of Annual Conference of the British Computer Society HCI Group. London: ACM/BCS. Hull, J. M. (1991). Touching the rock: an experience of blindness. Pantheon Books. Johnson, V. and Petrie, H. (1996). Evaluation methodologies for navigational aids for blind people. In J. Klaus, E. Auff, W. Kremser and W.L. Zagler (Eds.), Interdisciplinary aspects on computers helping people with special needs. Vienna: R. Oldenbourg. Kleege, G. (1999). Sight unseen. Yale University Press. Kornbrot, D., Penn, P., Petrie, H., Furner, S. and Hardwick, A. (in press). Roughness perception in haptic virtual reality for sighted and blind people. Perception and Psychophysics. Kuusisto, S. (1998). Planet of the blind. G.K. Hall and Co. McNeil, J. (2001). Americans with disabilities: household economic studies. Current Population Reports, 70-73. OXO Good Grips. Wikipedia information page. Petrie, H. (1997). User-centred design and evaluation of adaptive and assistive technology for disabled and elderly users. Informationstechnik und Technische Informatik, 39(2), 7-12. Petrie, H., Harrison, C. and Dev, S. (2005). Describing images on the Web: a survey of current practice and prospects for the future. Proceedings of 3rd International Conference on Universal Access in Human-Computer Interaction. Las Vegas, Nevada. Petrie, H., Johnson, V., Strothotte, T., Michel, R., Raab, A., Reichert, L. and Schalt, A. (1997). User-centred design in the development of a navigational aid for blind travellers. Human-Computer Interaction: INTERACT '97 (IFP TC13 International Conference on Human-Computer Interaction) . London: Chapman and Hall. Petrie, H. and Kheir, O. (in press). The relationship between accessibility and usability of websites for blind users. Petrie, H., King, N., and Hamilton, F. (2005). Accessibility of museum, library and archive websites: the MLA audit. London: Council for Museums, Libraries and Archives. Petrie, H. Morley, S., and Weber, G. (1995). Tactile-based direct manipulation in GUIs for blind users. Proceedings of Conference on Human Factors in Computing Systems (CHI '95) , Denver, Colorado. New York: ACM Press. Petrie, H., O'Neill, A-M. and Colwell, C. (2002). Computer access by visually impaired people. In A. Kent and J.G. Williams (Eds.), Encyclopedia of Microcomputers Volume 28. New York: Marcel Dekker. Royal National Institute for the Blind. (2006). Find out about access technology. Royal National Institute for the Blind. How do people with sight problems do everyday things?. Royal National Institute for the Blind. How to guide people with sight problems. Shostak, A.B. (1986). Retirees as techno-guides: a new role as shapers and makers of the future. Journal of Sociology and Social Welfare, 13(2), 306-317. Sloan, D., Heath, A., Hamilton, F., Kelly, B., Petrie, H. and Phipps, accessibility - maximizing the benefit of accessibility guidelines. Proceedings of the 2006 international cross-disciplinary workshop on Web accessibility (W4A '06): Building the mobile web: rediscovering accessibility? Sloan, D., Kelly, B., Petrie, H., Hamilton, F. and Phipps, L. (2006). Using context to support effective use of web content accessibility guidelines. Journal of Web Engineering. Strothotte, T., Fritz, S., Michel, R., Raab, A., Petrie, H., Johnson, V., Reichert, L. and Schalt, A. (1996). Development of dialogue systems for a mobility aid for blind people: initial design and usability testing. Proceedings of ASSETS '96: The Second Annual Conference on Assistive Technology. New York: ACM Press. Trekker. A GPS system for the blind and visually impaired. University of York. Department of Computer Science. Vanderheiden, G. (2000). Fundamental principles and priority setting for universal usability. In J. Scholtz and J. Thomas (Eds.), CUU 2000: First ACM Conference on Universal Usability. New York: ACM Press. Vanderheiden, G. and Tobias, J. (1998). Barriers, incentives and facilitators for adoption of universal design practices by consumer product manufacturers. Web Accessibility Initiative. (1999). Web Content Accessibility Guidelines. Version 1. Web Accessibility Initiative. (2005). Scenarios of people with disabilities using the Web. WebAIM. Experiences of students with disabilities (video). Weber, G., Petrie, H. and Mager, R. (1996). Access to MS Windows for blind users. In J. Klaus, E. Auff, W. Kremser and W.L. Zagler (Eds.), Interdisciplinary aspects of computers helping people with special needs. Vienna: Oldenbourg. White, P. (1999). See it my way. Little Brown. Worthington, T. (2001). Olympic failure: a case for making the Web accessible. INET 2001: Internet Society Conference, Stockholm 5-8 June.


Microsoft word - typhoon season for world markets.docx

Whether or not we are finally at the bottom of what is now formally being acknowledged as “the Great Recession” is hard to tell. After the shocking losses of the past week, I know many in the markets who are praying so. But perhaps most important, the events of the past week may finally mark the end of “policy fudge”. If that is so, then this is a time to celebrate – not that the glo

Roaccutane (istretinoin) consumer medicine information (cmi)

Roaccutane® contains the active ingredient isotretinoin Consumer Medicine Information What is in this leaflet Your doctor, however, may have Vibramycin®, doxycycline prescribed ROACCUTANE for hydrochloride, Doryx®, another purpose. Frakas®, Minomycin®) Ask your doctor if you have any 5. you have severe liver disease questions about why 6. yo

Copyright © 2010-2014 Sedative Dosing Pdf