That would be awesome indeed: using @scope (.classname)
to specify styles that only applies from this class.
In the meantime:
.visually-hidden:not(:focus):not(:active) {
border: 0;
clip: rect(0 0 0 0);
clip-path: inset(50%);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
white-space: nowrap;
width: 1px;
}
A company buy a concurrent. Then they do not put effort into creating new content or the one existing on it.
It is sad for the users, Digitalocean.
CSS tricks is indeed full of resources.
Basic validation can be done with HTML/CSS and the CSS selector :user-valid or :user-invalid pseudo-selectors
Update the styles of the web pages with custom ones :)
It contains all the gotcha we can find with the flow and cross axis, minimal width, align-content, margin auto, etc...
You need to be using the appropriate elements (s are your friend!), and managing the appropriate attributes and their values to make truly accessible user experiences.
The idea: uses CSS to detect accessibility issues.
The author uses different code snippets for it. One ensures the outline of the focus is never clipped. Another makes sure that not expanded content (aria-exanded="false"
) is not displayed. Another one targets aria-invalid elements. A busy container is not displayed in CSS, etc...
Every time you come up with a style that reflects a state or property of something (open, closed, expanded, collapsed, on, off, checked, disabled, busy, locked, selected, sobbing uncontrollably), do not use a class.
And an argument against utility-classes such as Tailwind: If you use these tools, you still need to know CSS. On top of that, you may need to know the tools’ syntax in order to incorporate any CSS that goes beyond what they offer. If you build these tools, please consider how you can use CSS that promotes and reinforces good and accessible underlying HTML syntax.
It provide a good example: this semantic HTML
<button
id="navbar-toggle"
type="button"
aria-label="Toggle menu"
aria-controls="navbar-menu"
aria-expanded="true"
></button>
<ul id="navbar-menu" aria-labelledby="navbar-toggle"></ul>
should be styled as follow in CSS
/* State: closed. Click to open. */
#navbar-toggle[aria-expanded="false"] {}
/* State: open. Click to close. */
#navbar-toggle[aria-expanded="true"] {}
Just as before, it turns out that the class name was completely redundant. In fact, because we reached for a class name prematurely, we forgot to communicate the right semantics at the markup level.
The benefits of min-width: 0;
while overflowing with flexbox
As it turns out, links are not focusable in Safari if they have 0 dimensions. Adding 1px padding, border, or width and height fixes the issue.
A flexbox playground in which code and a nicer UI can be toggled.
A quick win is to use font-variant-emoji: emoji;
Another drop-in css library that authors wished to have to start on every new little website.
Everything that does not have to be JS anymore, and there is a lot !
I didn't know about the accesskey attribute :)
A paper-style imitation library
Now I get it. As often, the container of the node matter.