Weeknotes – series 07 episode 05
- Author Benjy Stanton
This week has been stressful. If the ‘how much I’ve moaned at my partner scale’ is anything to go by, then it’s probably about 7 out of 10.
The product I’m working on is heading towards a private beta, and I’m constantly worrying about things we could be doing better. I know it’s part of a designer’s job to be thinking about ways to improve quality and better meet user needs, but I think I let it get the better of me this week, and I let my worries spill over, and perhaps distracted others on the team with things that didn’t need to be addressed yet.
But, it definitely hasn’t been all bad…
I’ve been going round various external show and tells, showing our latest prototype to stakeholders across the wider organisation.
Many of the people at the show and tells represent our users, so it’s been good to get a sense of their reactions. Their feedback and questions were positive (if a little reserved). Previously the prototype has been described as “clunky” and nobody said that this time. Phew.
I’ve done the same presentation 3 times now, and there’s even a recording of me doing it, so I’ve been immortalised on the department’s Sharepoint for generations to watch.
I was reviewing a screen this week and spotted that it contained many links without
href attributes. That's the bit of the link that tells browsers which page to go to when clicked.
I wanted to report this issue, but first I wanted to gather some evidence and resources about why this was bad practice and how it could introduce barriers to users.
Here’s what I found out about links without
- the links rely on CSS to work, so if CSS is disabled, or customised by the user, then the links might not look or act as expected
- extra code is needed to make the links work with keyboard navigation
- link styling can be unpredictable on Windows High Contrast Mode
- the links can act unexpectedly with some screen readers
Read more about this in links, missing href attributes, and over-engineered code by Martin Underhill
This page by The Ally Project is also good primer on creating valid and accessible links.
Bluesky is open
Bluesky seems to be emerging as the place for government digital people to migrate to, now that Elon is ruining Twitter. If you want to try it out, it’s open for anyone to sign up to…
Bluesky is far from perfect, but I really hope we (as a community) find somewhere that rekindles the spirit of early Twitter.
Reading (and listening to)
- Design and uncertainty by Vicky Teinaki
- What Can a Website Do? By Dave Rupert
- Weeknotes No.56 by Michael Cattell
- Essential Service Design Secrets by Jo Carter
- Podcast: Designing content for Welsh language users by Robert Mills and Nia Campbell
A few things that I didn’t get round to reading, but don’t want to forget about…
- Making a character count component more accessible by David Cox
- What's new in WCAG 2.2 by AbilityNet
- Getting started with manual accessibility testing by Martin Underhill
- In Loving Memory of Square Checkbox by Niki
- Major new work: harmful design in browser choice by Cennydd Bowles and Harry Brignull
- Coronavirus Extremely Vulnerable People by Joe Lanman
- Weeknotes 09/02/2024 by Heledd and Alex at Natural Resources Wales