Access all Areas

I attended Cordellia Yokum's Usability for everyone: Are you excluding some users from accessing your website? workshop at CAST 2022.

As I can't do justice to a packed and interactive five-hour session in a short post like this, I'm going to simply drop bullet lists and links from the notes I took here.

Accessibility

Not just about disability
Auditory, cognitive, neurological, physical, visual
US: one in four have some disability
Small screens, elderly users, slow internet, poor lighting conditions, etc
SEO benefits from being able to access content
Accessibility is not a project. Like Quality, improve it incrementally and continually

Assistive technologies

Screen magnifiers (e.g. web browser zoom)
Text readers (e.g. blind and partially-sighted, ADHD, dyslexia sufferers)
Speech recognition software
Head pointers, motion tracking (often for paraplegic users)
Single switch entry (e.g. sip and puff mouth operation; keyboards with "quick buttons")

POUR

Perceivable
Operable
Understandable
Robust
Quick (and interactive) reference
Filter aggressively for your immediate need
Covers test ideas, success criteria, fail criteria
Baseline AA, cherry pick from AAA (for most contexts)
Some judgement calls may still need to be made

Perceivable

Text alternatives for non-text content (e.g. text button, alt, captions)
Content that can be presented in different ways without losing meaning
Make it easy for users to see and hear content (e.g. use landmarks for navigation)

Operable

Navigation of components; make all functionality available from the keyboard
Time to read and use content - "you have three minutes to finish your purchase"
Don't make people sick or ill when using your page (e.g.seizure inducing images)
Don't let people get trapped in the content (e.g. can tab across all fields)
HTML5 with Semantic Elements gives much of this already
Subverting the intent of HTML (e.g. Div as button) causes problems.

Understandable

Text is readable
Content appears consistent and predictable
Often about form inputs and labels
Behaviour that is flagged
Errors that make sense

Robust

HTML code is valid
Don't abuse JS and DOM updates because you can
Use HTML5's semantic elements and get benefits out of the box
Linters can help, but dynamic content won't usually be checked by them

Oracles

WAI-ARIA
WCAG
W3C HTML validator
Contrast Finder
aXe extension
Lighthouse extension
WAVE extension
Accessibility Insights extension
Chrome Dev Tools, Accessibility section in element mouseover
Chrome Dev Tools, Accessibility Tree in Elements pane

Colour

Contrast has strict pass/fail rules
... but they are still contextual (e.g. gradient, font size, interactivity, opacity etc)
Use pure hex numbers don't lighten with CSS
Sometimes perception is not the same as the standards
Remember colourblindness
Remember different states of page elements (Dev tools can force states)
Get the designers to use tools e.g. Figma plugin
CSS prefers-color-scheme (respects Dark mode)
Avoid large blocks of pure red (because seizures)

Motion

Migraine sufferers, users with ADHD can be affected
Need to give people the ability to reduce motion
CSS prefers-reduced-motion respects preference settable in OS (e.g. Mac "Reduce Motion")
Limit any flashes to max 3 (because seizures)

Alternative Text

Provides value for screen reader, SEO, and slow connection
Different rules for different elements (decision tree)
Empty alt attribute stops screen readers verbalising the URL (!)
Link to deeper description when you have a complex image (e.g. chart)
Audio and video: consider transcripts

Zoom and Reflow

Keeping the website responsive in zooming or magnification
Simple heuristic step up to +400% zoom, inspecting at each increment
Avoid horizontal scrolling: hard to navigate; context is lost
Images should be resized for the page
Page elements moving to be in the viewport is fine

Keyboard navigation

Web Accessibility in Mind guidelines
For vision (including focus) and mobility-impaired users
Also power users
Safari - has some weird preferences on keyboard navigation
Interesting conversation around defaulting keyboard focus
... into search box in modal dialog vs new page vs results)

Forms

Using for=id allows label text to link to the page element with name
Group by role to aid navigation
Remember the difference between submit button and a link
Disabling a button until fields are filled blocks readers
Attribute aria-disabled (ref) allows focus but still notes it as disabled on the page
Clickable div element might look like a button (!) but screen readers don't see it

Error Handling

Colour should not be the only indicator of a failure or required
Use aria-live to announce issues
Announce issues at the top and on the specific elements
... with jump links from the top to the issue
Be explicit about how to fix them

Autocomplete

very helpful to those who have to type with mouth etc
reduces mistakes generally

Comments

Meet Me Halfway?

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Beginning Sketchnoting

In September 2017 I attended Ian Johnson 's visual note-taking workshop at DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

Not Strictly for the Birds

One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito...

Don't Know? Find Out!

In What We Know We Don't Know , Hillel Wayne crisply summarises a handful of research findings about software development, describes how the research is carried out and reviewed and how he explores it, and contrasts those evidence-based results with the pronouncements of charismatic thought leaders. He also notes how and why this kind of research is hard in the software world. I won't pull much from the talk because I want to encourage you to watch it. Go on, it's reasonably short, it's comprehensible for me at 1.25x, and you can skip the section on Domain-Driven Design (the talk was at DDD Europe) if that's not your bag. Let me just give the same example that he opens with: research shows that most code reviews focus more on the first file presented to reviewers rather than the most important file in the eye of the developer. What we should learn: flag the starting and other critical files to receive more productive reviews. You never even thought about that possi...

ChatGPTesters

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the T...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report. Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia. ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Software Sisyphus

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "How can I possibly test 'all the stuff' every iteration?" Whoa! There's a lot to unpack there, so let me break it down a little: who is suggesting that "al...

Hiccupps

Search This Blog