One insight into the accessibility of a web page is how a screen reader reads the page out loud. The VoiceOver screen reader provides training in its use. The training shows how to navigate on a page, but the example raises more questions than it answers.
When a website is not designed to be accessible to users with disabilities, may that be a sign of additional trouble? The case of Vemo Education is an example of that being true.
Two days ago the U.S. House passed a bill making it harder to enforce disability rights. Is that an attack on the accessibility of the web, too? Unlike some, I think it is, but it could make web accessibility stronger.
About to finish a retraining program in web development, I’m not partaking in job-seeking anxiety or rehearsals aimed at boosting interview-taking prowess. One of my strategies is to get good enough at a specialty to be useful, and then offer to help. The rest will follow naturally. Or will it?
I may have discovered the thing that most makes me enjoy being a Learner at Learners Guild: It allows me to be a shameless perfectionist. I can “refactor” ad nauseam, and nobody complains.
Web accessibility is being downplayed by the Trump administration, but others are picking up the slack, further increasing the incentives for website owners to make their sites friendly to users with disabilities and below-average digital fluency. I’m working on a tool that helps you make your résumé accessible, too.
My Calculator was already superior to the Mac’s in some ways. During my 36th week of web development training at Learners Guild I widened the gap by adding features to make it more accessible for users with varying abilities and disabilities. The world of web software needs help in achieving high quality, and even more help in making itself broadly accessible.
Continuing to study web software accessibility, also called “a11y”, I have tried to inject more geezer-friendliness into a website.