Shifting Left: How CMS accessibility Can Help - A11yTalks
What Makes a Good Screenshot? - TPGi
Do you use screenshots when loggin issues? They can really help to clarify problem areas. Ian Lloyd provides pointers on what makes a useful screenshot.
Dialogs, modality and popovers seem similar. How are they different?
A deep dive into the semantics, behaviours and characteristics of some of the most common user interface elements of websites today.
Don’t Override Screen Reader Pronunciation
When many devs, testers, and authors first start listening to content through a screen reader, they are surprised to hear dates, pricing, names, abbreviations, acronyms, etc. announced differently than they expect. With the best of intentions (or branding panic) they may seek to force screen readers to announce content as…
Three attributes for better web forms
Better UX through better HTML: inputmode, enterkeyhint, and autocomplete.
Aligning Jakob Nielsen's 10 Usability Heuristics with the WCAG 2.1
This article shows how Jakob Nielsen's 10 Usability Heuristics align with the Web Content Accessibility Guidelines (WCAG).
AI-Generated Images from AI-Generated Prompts
As the world’s leading expert on a people-first approach to computer vision, I am dedicated to providing insights that enable designers, developers, and copywriters to create accessible images at the highest possible velocity. A velocity so high, in fact, you can almost hear the point whistling over their head, like…
I tried out SyntheticUsers, so you don't have to
Using AI as a replacement for interviewing actual users is a brilliant idea if you want to look like you made an effort, but are really looking to fill the page with superficial, stereotyped bullshit.
FIX Color Contrast – Accessibility in Web & UI Design
📄 Download the PDF Cheat Sheet: https://pmty.pe/color-contrast
Don’t make my mistake – Learn what’s crucial and required about color contrast for text and UI components for your next design project.
💌 Subscribe to the weekly Font Friday Newsletter:
https://pmty.pe/newsletter
💡 Typography Coaching Call
https://pmty.pe/coaching-call
🎥 Eric Egger’s YouTube Channel:
@yatil
Chapters:
0:00 Intro
1:18 Why web accessibility?
2:50 Color contrast for text
3:57 Color contrast for UI components
5:03 1 Add a border
6:03 2 Add additional signifiers
6:37 3 Consider the context
7:42 YouTube filters pass accessibility
8:44 YouTube search box fails
9:09 Action steps with color contrast
#accessibility #webdesign #typography
%2Fcdn.vox-cdn.com%2Fuploads%2Fchorus_asset%2Ffile%2F24539835%2FP10_Colorblind_Leading_the_Blind_236587.jpg?width=92&height=&ar=&mode=&format=avif&dpr=2)
This is what it looks like to be colorblind
Pro tip: when you meet a colorblind person, don’t repeatedly point to things and ask what color they are.
Video zeigt, warum die Bedienung des ICE-4-Rollstuhllift fast 10 Minuten dauern kann
Der ICE 4 der Deutschen Bahn besticht durch ein technisch besonders ausgefeiltes kaum wahrnehmes Design des Rollstuhllifts. Die Bedienung gehört jedoch mit zu den komplexesten im Bereich der Mobilität – mit entsprechenden Nachteilen. Fahrgäste, die den Lift brauchen, sollten ein Training haben.
How People with Disabilities Use the Web
Updated W3C Resource
Checklist - The A11Y Project
A beginner's guide to digital accessibility.
This checklist uses The Web Content Accessibility Guidelines (WCAG) as a reference point. The WCAG is a shared standard for web content accessibility for individuals, organizations, and governments.
JAWS, NVDA, and VoiceOver Braille Viewers
First, a very important qualifier — this does not represent how Braille display users experience the web. All this post does is show how to enable the Braille display emulators in JAWS and VoiceOver. This can be handy when testing issues reported by users and you do not have a…
CSS-only Widgets Are Inaccessible
Usually. I originally titled this InacCSS-onlyible. I even made this typographically, er, distinct image. Then I realized it was silly and will instead use the neologism in a talk so I can hear the groans IRL. Interactive widgets powered with only CSS are relatively common as people are playing with…
Windows high contrast mode and focus outlines or: My focus indicators were inaccessible
In order to make my website’s keyboard focus outlines pretty in Safari, I inadvertently broke things for people who use Windows High Contrast Mode.
Exposing Field Errors
This post is about exposing field errors programmatically. I have already shared some opinions (such as a caution about displaying messages below fields or avoiding default browser field validation), but this post dives into using ARIA to convey them to screen reader users. With fields that produce error messages on…
Accessibility vs emojis
At an emojis best, they can add fun and context to a post or message. At their worst, they can cause frustration and abandonment.
Uppercase copy and paste. The problem and a questionable trick — Vadim Makeev
If you copy one of my article titles, you’ll probably get “ARTICLE TITLE” in uppercase. Why would I name my article like that? It’s not me, it’s browsers and specs again.
Why we care more about effectiveness than efficiency or satisfaction
We look at how GDS defines usability and why we think effectiveness is more important than efficiency or satisfaction.
Best Selling Accessibility
A consideration on how to sell accessibility services
Chartability
A beginner's guide to manual accessibility testing - Pope Tech Blog
Learn how to do manual testing with a keyboard, screen reader, and zoom testing.
My ideal accessible components resource is holistic, well tested and easy to use
To improve accessibility of the web as it is today, I feel we dearly need accessibility guidance that is holistic, well tested and easy to use.
If that's the case, you may wonder, why does APG focus on ARIA only? There's no bad intent here… I think it is simply because it is written by a subgroup of the ARIA Working Group. That Working Group specifies ARIA and it has a deliverable to show how to use it. This makes good sense. But again, it isn't ideal if the intention is guidance that helps developers build the very best for users with disabilities (which I think is the goal we should really want to optimise for). Nobody seems to have that as a deliverable.
‘Developer experience’ is a phrase sometimes frowned upon, especially when contrasted with user experience. If we had to choose between them, of course, user experience would be the first choice. But the choice isn't binary like that. If the stars are aligned, one can lead to the other. Companies that make developer-focused products (like CMSes, versioning control, authentication, payment providers, databases etc) usually have a dedicated “developer experience” department that ensures developers can use the product well. Among other things, they try to reduce friction.
I believe effective accessibility guidance answers “how easy will this make it for people to get it right”, and probably also ”how will this avoid that people take the wrong turn”.
YES!!!!
In this post, I've tried to lay out what my ideal accessibility guidance looks like. The gist of it is: make it easier for people to get accessibility right. And the opposite, too: make it harder to get it wrong. I feel the closer we can get to that, the more accessible interfaces can become. I think this is the way to go: guidance that is holistic, well-tested and optimised for developer experience (or, more broadly, the experience of anyone touching web projects in a way that can make or break accessibility).
Tooltips in the time of WCAG 2.1 | Sarah Higley