Reading Time: 10 minutes My Basic User Journey (BUJ) content tool guides our design thinking of digital information and flow between our user and our business. Is it still useful today?
An inclusive price update
Reading Time: 5 minutes Content design is an empathetic UI and UX craft. Presenting a price reduction from $y to $x needs work with inclusive HTML and CSS. It’s not all done in Figma.
Primary to tertiary button hierarchies
Reading Time: 8 minutes Arrays of Primary, Secondary, and Tertiary interactions are a familiar pattern. Does their content, taxonomic, and visual design assist or compound our experience?
Including emphasis
Reading Time: 5 minutes HTML offers a choice of emphasis for individual words and blocks of content. Let’s create an inclusive experience of emphasis beyond using an em tag.
Inclusive nested list nomenclature
Reading Time: 7 minutes The native HTML list nomenclature and a lack of punctuation are a barrier to some of our readers. A little CSS and JavaScript improves the inclusive experience.
Fun image erections
Reading Time: 4 minutes Browsing my favourite YouTube channels, I found an ideal lunchtime project. Online Tutorials featured a snatty CSS image erection effect. It made me think of a 4-fold flyer I created for an art show. It was ideal to play with.
How do we make legalese accessible?
Reading Time: 23 minutes Legalese and compliance copy is the pillar of trust when customers agree to our terms. It’s the specialist language of law. How do we make legalese accessible?
Pffft to embedding PDF inside HTML
Reading Time: 5 minutes Why embed a PDF inside our HTML? Isn’t it odd? Our digital medium is HTML. It’s a wonderful space offering accessibility, beauty, inclusion, and versatility.
An elephantine dislike for off-the-shelf CMS
Reading Time: 4 minutes I dislike off-the-shelf content management systems (CMS). They allow anyone to publish content to the Web. That’s fantastic! If only you would deploy them accessibly!
When compliance fails to include pie (case study)
Reading Time: 22 minutes An accessibility engineer complied with WCAG SC 1.1.1 and broke 13 others. This case study closes the gaps between accessible and inclusive assessment design.
Divided over slashes
Reading Time: 6 minutes We should stop writing the “and/or” conjunction. Its visual meaning is ambiguous and the audible experience is horrible when announced as, “and slash or”. We can design an improved experience.
Readability testing with ice cream
Reading Time: 2 minutes When specialised vocabulary exceeds a readability score of Grade 8, then replace it with something that doesn’t. I found the ideal phrase is, “ice cream”.
Golden Bullets
Reading Time: 4 minutes Demonstrating an improved and inclusive UX of lists for visual and non-visual readers
Choose the right medicine
Reading Time: 5 minutes Thinking about those lozenge-shaped UI components designers use for filters and refer to as pills or capsules, and how to code them – properly.
Happy Writing
Reading Time: 2 minutes Replace your brand’s negativity with positivity. Words and phrases are as important to our users’ mood as your graphics. Happy writing!
The ‘One day’ Award – Shortlist 2021
Reading Time: < 1 minute One Day everyone will know when their best visual design decision results in a poor content experience. In the meantime, let’s lament the loss of common sense.
Altruistic Alternative Attributes
Reading Time: 5 minutes We must understand when to include an alt value and when so, what to include in and how to write that value. That’s not necessarily simple. It’s emotional.
Stupid Questions?
Reading Time: 4 minutes There really is no such thing as a stupid question. Is there? <-- Yes. That was a stupid one.
Are Frameworks Evil?
Reading Time: 3 minutes Frameworks don’t need to be evil. Only their masters can make them that way?
Is HTML better than Markdown? Yes
Reading Time: 4 minutes When we write web content in valid vanilla HTML, the Internet is a far more inclusive product. I argue to drop Markdown and write to, or into HTML.