The computer is one of the most versatile tools of all. Its functionality is limited only by the ability to program and our ability to imagine possibilities. However, there is evidence that it has been very difficult to provide reliable applications that are well adapted to the wide range of options needed to allow access to persons with disabilities. The shortcomings come in seemingly infinite differences. We should not be surprised by this. The human body is complex and can break down in endless ways. Some failures are temporary (eg broken wrist) and some are chronic and persistent (eg deafness, blindness, motor and cognitive impairment). Regardless of the case, people with these problems usually require interventions of various kinds to enable the use of computer applications.
I suffer from progressive neurological hearing loss and as a result I rely heavily on binaural hearing aids in everyday life. My wife has two types of cochlear implants – a technique that still amazes me that works. I rely on subtitles in television, recorded video, and video conferencing. In general, my disability has made me aware of the value of technical responses in helping people with disabilities.
We know a lot about the different types of intervention to improve accessibility. Enlarge images and text, maximize contrast and font style, “screen readers” that verbally describe what’s on a computer screen, transcribe audio for people who are deaf or hard of hearing, Displays The optics to indicate when the arms and hands cannot be used and the list goes on. Some of these features are integrated into computer, mat and mobile operating systems and can be activated to provide the necessary facilities. It is not always easy to know how to do this in a simple way. Perhaps most importantly, those who design computer-based applications may not have the experience or intuition in using accommodation tools to make design decisions that achieve the desired level of utility.
Unless the programmer (or consultant) is an experienced user of screen reading, he may not know how to create a pageWL It can be accessed as much as possible using available screen readers. Users may not be aware of the configuration options that would make the device more useful. Even when we write detailed specifications for color combinations, contrast, font sizes, and scaling adjustments (for example, a file the web Is it still useful when scaling it?) It can happen that the programmer does not have the experience and skill to turn recommendations and patterns into accessible implementations.
This is where the page development tools the web Accessible with templates and usage examples can make a difference. As in the past, the creation of file pages the web Made by typing pages manually the web Marked in HTML and now built with convenient tools and compositing templates, it’s recommended to have compositors that render pages naturally the web can access. There are testing tools, instructions, and page configuration editors the web, but they usually provide only limited guidance or help. Programmers looking to produce accessible applications need a great deal of experience using mechanisms, patterns, and conditioning tools to achieve the desired goal.
The author writes according to the new spelling convention
Fenton G. Cerf is one of the founders World wide web. May 19 is World Accessibility Awareness Day