Menu
Our free AT-node for access website is back up and running. How fast can people with physical disabilities type when using different assistive technologies? Use AT-node to get evidence to enhance your understanding.
AT-node is a website that organizes the available research evidence on text entry rates (typing speeds) for people with physical disabilities. We built it a few years ago, and recently it had not been working due to necessary platform changes. I finally got around to fixing it, and now you can run AT-node for Access again.
Continue reading “AT-node revisited: explore the data on typing with assistive technology”
Check out some KPR highlights for 2019, including our top 5 blog posts for the past year. Best wishes for 2020 to all!
We’re working on some new ways to visualize the text entry data within AT-node, and we need your feedback! Take a look at some designs and let us know what you think.
Using third-party code, such as Bootstrap, Google Charts, shopping carts, and the like, to boost your website’s functionality is powerful and often necessary. But it can also introduce some accessibility problems, and those aren’t always easy to fix. Here are some tips on dealing with these issues.
This is the third in our series on testing and improving the accessibility of KPR’s websites. Previous posts focused on how we conducted systematic do-it-yourself accessibility testing and how we fixed the accessibility problems we found. Some of the toughest challenges involved dealing with third-party code. This post presents the main problems related to third-party code and gives some details about how we fixed them.
Continue reading “Web accessibility: challenges with third-party code”
We recently tested the accessibility of KPR’s websites. Here’s an overview of what we found and how we fixed it. Spoiler alert: tests revealed some major web accessibility issues.
We’ve been working on testing and improving the accessibility of KPR’s websites. The first step in this process was conducting systematic do-it-yourself accessibility testing, which we described in an earlier post. This post presents the main problems revealed by the tests and gives some details about how we fixed them.
Continue reading “Web accessibility testing: what we found and how we fixed it”
