Menu
Here’s another great example of how a simple change to a user’s computer setup can make a big difference, in this case using keyboard assistive technology. Read on for a summary of this 2018 case study from the University of Bordeaux.
It’s possible to type with your tongue using tiny sensors worn in the mouth. This post presents text entry rate results from a recent study, including two people with cervical spinal cord injuries.
For about 30 years, researchers have experimented with different ways of typing with your tongue. The Tongue Touch Keypad from the 1990’s used a tiny keyboard embedded in an orthodontic-style retainer. A newer approach continues to use the orthodontic-style retainer, but now embeds inductive sensors that are activated by moving a small magnet attached to the tongue. How well can you type with this sort of tongue computer interface? Read on for results from a recent study.
Morse code can be a very effective way to type using only two switches. And now you can use it on an iPad, creating some new possibilities for people who are switch users. This post shows you how to set up and use Morse code on the iPad.
Morse code dates back to the early 1830’s, and has been used in assistive technology since at least the 1970’s to support typing using one or two switches. As switch access methods go, it has the potential to be quite fast– one study measured a Morse code typing speed of 12.4 words/minute for a person with a C2 spinal cord injury, using a sip/puff switch for the dots and dashes. Fast forward to 2019, and Morse code is having a bit of a moment. One question that comes up frequently is whether you can use Morse code to type with switches on an iPad — Yes, you can! Read on to learn how.
2018 was an unusual, fun, and interesting year for Koester Performance Research. Here are some highlights of KPR’s work in the past year.
Wishing you all a Happy New Year! In the spirit of a new year’s energy, I took a look at KPR’s activities in the past year. 2018 was unusual, in that we’ve intentionally not been engaged in a large funded project, in order to leave some space and see what might take shape. One overarching goal this year was to share more of what we’ve learned and developed with the wider world. To that end, we revamped the KPR website, incorporated a blog, and set up new systems for communicating with people who are interested in what we’re doing. It’s still a work in progress, but has been enjoyable and seems useful so far. We also continued research, development, and service work within assistive technology. Read on for a few specific highlights.
Continuing our series on examining text entry rate data for people with physical disabilities, we look today in more depth at the statistical distribution of those data. A histogram is a great tool for visualizing a distribution and providing insights into a dataset.
As promised in our previous post, today we’re going to delve more deeply into our dataset of text entry rate across 177 individuals with physical disabilities. (If you haven’t seen the infographic and read about the creation of this dataset already, you might want to read that earlier post first.)
Continue reading “Text entry rate data: what can we learn from a histogram?”
We gathered the available data on computer text entry by people with physical disabilities and created this infographic. Results suggest that there is a long way to go to better support computer users with disabilities.
Sajay Arthanat and I continue organizing the available research evidence on text entry rates (typing speeds) for people with disabilities. I shared an overview of the findings in an earlier post. Here, I’ve added two new studies to the dataset and created an infographic describing the distribution of text entry rate across 177 individuals. Continue reading “Text entry rate for people with physical disabilities [Infographic]”
![Text entry rate for people with physical disabilities [Infographic]](https://kpronline.com/blog/wp-content/uploads/2018/06/text-entry-rate-infographic-cropped-1200x628-opt-1200x628.png)