aria-label
and aria-labelledby
are exclusive. So they can be enforced for components in typescript:
type ToggleSwitchProps = {
name: string;
checked: boolean;
handleToggle: () => void;
size?: "sm" | "lg" | "base";
classNames?: string;
} & ({ ariaLabel: string; ariaLabelledBy: never } | { ariaLabel: never; ariaLabelledBy: string });
To my surprise they didn’t use skip links when they were presented one. [...] They didn’t understand the purpose of these links.
He explained that when he clicks on a link, for instance to an interesting article about skip links, he expects the first thing he encounters to be the article itself.
Instead of a "Skip to content", a "Skip to navigation" could be better.
Both Figma and Photoshop are for people who believe the web looks like an image.
Semantic HTML is a must. Because there is UX with HTML :D
Another thing our design tools really don’t give a shit about is accessibility. And to be honest, I think most of our industry doesn’t really care about accessibility as well.
Looks also valid to me.
The specialists who helped the architect in making sure it was certified did nothing else than ticking boxes. And this is exactly what most of us do when we think we make our sites accessible. We tick the WCAG boxes.
Don't Use Fixed CSS height or width on Buttons, Links, or Any Other Text Containers | Ashlee M Boyer
Use padding, relative line-height and a flow layout instead.
"When we design for disabilities we make things better for everyone"
The last version of the WCAG released the 5th of October
The studied website https://www.cop28.com/
As UI evolves, I think we will come one day with a UI library that can be customized entirely (hello white label design system).
Being able to test features on it should also be possible. It don't understand how all accessibility criteria can be tested though.
Le guide d'Orange contenant un certain nombre de ressources
One of my favorite things to do when stumbling upon a web page that uses an accessibility overlay is to use the overlay to increase the font size. I'm giving a 99.9% guarantee that this will cause the formatting on the page to break at some point. Couple that with increasing the line height and the letter spacing and you get a 100% return on your investment. Probably need to install a second overlay to fix this problem.
What happens on web pages when these three values are changed?
There are no shortcuts on accessibility at the moment
Why is there the first rule of ARIA? Because ->
I didn't push the thought to this point! The distinction between the focus indication area and the contrasting area is also pertinent.
How to make an accessible skeleton with ARIA ?
Note that the skeleton pattern hides a bad design where the UI is slower than expected. So avoid it as much as possible.
- Check if the image really needs a description. Maybe it is decorative. The W3C alt decision tree(opens in a new tab) is an excellent resource to help you categorize your photos.
- Avoid writing "Image of", "Icon of", or "Picture of". Screen readers announce the presence of an image. Adding these words inside your alt is unnecessary.
- Keep it as short as possible. Be specific but not overly descriptive.
- Try to put the most essential information at the beginning of your description.
allyphanta11yphant teaches web accessibility, one step at a time, broken down into manageable pieces. We call these challenges. You won't need to read large amounts of text to complete those. Instead, you will learn by applying the concepts in code. Get started with your first web accessibility challenge and improve your skills.
A first approach of ARIA with a toggle button