Getting to the root causes of usability errors and accessibility problemsUser Vision

Perception–Cognition–Action (PCA) analysis is a method of uncovering the root causes of usability errors and accessibility challenges in systems. By understanding these underlying issues, designs can be enhanced in order to avoid hazardous situations and cater to a wide array of user needs.

The approach is particularly recommended for medical devices, and is described in the international standard IEC 62366 on the application of usability engineering to medical devices. But this powerful technique can go so much further than that. It can help us understand how to improve usability and accessibility for a wide range of products.

My article for the User Vision website describes how the Perception–Cognition–Action approach works, how it aligns with established accessibility best practice, and how we at User Vision have applied it to transform a complex medical system used by both patients and healthcare practitioners.

I will also be speaking about the technique at this week’s UX Edinburgh meetup, which is an accessibility special in recognition of Global Accessibility Awareness Day. If you are around on Thursday 16 May at 18:30, it would be great to see you there.

Access for all — my final plea for human-centred designLizzie Cass-MaranWebsite and Communications Blog

Last month our brilliant colleague Lizzie Cass-Maran left our team after more than 10 years. In her final blog post for our team’s blog, she has written this plea to keep humans at the centre of all our decision-making.

For the past few years I’ve been working with Lizzie, I’ve always been impressed at the impact and quality of the work she has delivered in often challenging circumstances. She is a key reason why Website and Communications has such a strong user-centred culture.

Moreover, her impact stretched far beyond our own team. She influenced human-centred approaches across the entire university. She has played a genuinely leading role in our communities of practice. The effective digital content training that she has designed ensures that our content editors will continue to create well-written content that meets users’ needs.

Most recently, she did most of the heavy lifting in a project to revolutionise the university’s editorial style guide. The outcome of this is that, for the first time, we have a unified style guide that is designed for use across all content, print and digital, being managed across organisational silos.

Our team genuinely will not be the same without her.

HTML: The Inaccessible PartsDave Rupert

Following on from Gov.UK’s revelation about <input type="number">, Dave Rupert has compiled a list of other bits of HTML that can cause inadvertent accessibility issues.

There are some cases where even using plain ol’ HTML causes accessibility problems. I get frustrated and want to quit web development whenever I read about these types of issues. Because if browsers can’t get this right, what hope is there for the rest of us.

Not that we should give up, of course.

Why the Gov.UK Design System team changed the input type for numbersHanna LaaksoTechnology in government

Numeric keypad interface

The Gov.UK Design System team have discovered that using the HTML element <input type="number"> creates some surprising problems in certain environments.

Some of the limitations in assistive technologies such as Dragon Naturally Speaking are disappointing but unsurprising.

But Chrome deciding to convert large numbers to exponential notation is rather more eyebrow-raising. Then there is Safari adding commas to long numbers that are in fact credit card numbers. You have to wonder about some of the decision-making among browser vendors.

Accessible polling cards: Keeping it low-techLizzie Cass-MaranWebsite and Communications Blog

Polling cards of different colours and shapes

How do you make participation in workshops and training sessions as accessible as possible? My colleague Lizzie Cass-Maran has created these low-tech voting cards (using letters, colours and shapes to include as many people as possible) that are easy to make yourself — and a lot less fiddly than some of the technology solutions out there.

Why much of the internet is closed off to blind peopleJames JeffreyBBC News

Visually impaired person using the web

The most notable thing about this article is the sorry list of weak excuses offered up by businesses who can’t be bothered to make their websites accessible.

“…a blind person can always ring Domino’s toll-free number and order that way…”
Why should they have to?
“…there is no clear objective guidance on what constitutes an ‘accessible’ website.”
O rly?
“The online environment was never intended to be covered by the ADA…”
Says who?

How about just doing the basics that will help include your customers, and your fellow human beings?