Is ReCaptcha still recommended or is there a more accessible one that
IBM is collaborating with Freedom Scientific to offer organizations a complete portfolio of enterprise accessibility training and eLearning to ensure that all employees – designers, developers, testers, quality assurance, and program managers – are following best practices in accessibility and are educated on current regulations and industry standards.
For more information on the IBM AbilityLab Compliance System and other technologies, visit IBM Accessibility.
(Curated by Lifekludger)
Read full article at Source: IBM Research: Inclusive Technology is the New “IT”
Web accessibility makes it easier for people to use the web. It creates a better user experience for a wider audience. It’s not just targeted towards people with disabilities.
“Web accessibility means that people can use the web. Not ‘people with disabilities’. Not ‘blind people and deaf people’. Not ‘people who have cognitive disabilities’ or ‘men who are colour blind’. People who are using the web. People who are using what you’re building.”
Testing software and websites is a challenge. We need to ensure that the final product is fit for purpose, and as good as it can possibly be. We must also understand it can never be totally free of bugs. We do lots of different types of testing from User Acceptance Testing (UAT) to performance and accessibility testing. All of this is essential to make sure that the final website does everything it’s supposed to do.
Another important aspect of testing the website as it develops is ‘usability testing’ where we ask invite end users to test new designs or functionality of the website. We’ll be writing more about this part of testing in a future blog post.
What is an accessible website?
Often when we try to define what an accessible website is, we default to the position that it’s a website that can be used by a visually impaired person via a screen reader. If your website makes sense and can be navigated when it’s read out by a screen reader then you have an “accessible website”, you’ve ticked a box and your work here is done. Well done, let’s all go to the bar.
In reality, this definition is far too narrow and doesn’t come close to imparting an understanding of the other accessibility issues that can arise. It’s also a definition that makes accessibility as a whole easy to dismiss. Some might roll their eyes and complain a lot of extra work for a very small percentage of users. Others might declare “we don’t have any blind users” as a reason for not making a website accessible. “We’re not marketing ourselves to the visually impaired demographic” somebody might say before dropping their microphone and leaving the room to sustained applause. One brave soul might make the claim they they “don’t have time to test in other browsers or devices”. It’s important to note here that these are not straw man arguments but are in fact real things that I have heard actual, living, breathing, human beings say.
I’d argue this is already an unethical, exclusive, and short sighted approach to web development but it is, unfortunately, an argument that could carry a lot of weight in a business environment where we often have to weigh up the investment of effort and time against the return on that investment.
Here’s how the web accessibility initiative answers this question:
Web accessibility means that people with disabilities can use the Web.https://www.w3.org/WAI/intro/accessibility.php
This is true and I have no argument with it but it’s not a complete answer to the question so let’s start again.