Defining a subset of the web that removes a lot of complexity :)

Provide a local index of sites complying with the requirements above, so that sites can be found without the use of an external search engine.

How does this scale? How is the index sorted? That was originally the answer provided by search engines.

If a state is important enough to indicate visually, it's probably important enough to expose to assistive technologies.

With an example such as <a href="/about" aria-current="page" class="current-page">, we now have two meanings that convey the same information: the aria attribute and the class. This can leads to bugs while refactoring.

Another example is provided with dropdowns or toggle buttons, and sorted table columns.
Mentions to :disabled or aria-disabled, :invalid or aria-invalid, aria-selected, role="tab", and the list can go on!

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.

Even if the subscribing form includes non-binary participant , advertisers have in contrast an "Unknown".

While Google doesn’t allow ads to exclude men or women from jobs, housing, or financial products, they did allow advertisers to exclude the “unknown” category, leaving those outside of the gender binary excluded as well.

Just the way this data gets labeled already shows how much of an afterthought gender diverse people were.

#idea #project: create many categories that fit better than male, female and "unknown". A better list?

If we don’t include and prioritize people from minoritized groups in our design and tech practices, we risk not only collecting incomplete or incorrect data, but also processing and using it in biased and harmful ways.

Integrate a rust game compiled in wasm into sveltkit

Overlord, Neptune, Fortitude, ...

Et encore, il y aussi le front de l'Est, le Pacifique, etc...

Une opération peut avoir une ou plusieurs sous opérations.

Une opération est définit par son nom. Elle a une date de début et de fin.

Utile au besoin, l'État a publié le registre

Il existe aussi une #API dédiée https://api.gouv.fr/les-api/api_carto_codes_postaux

You build things thinking you know what people want and how they’ll use it but they’ll often surprise you.

I distinguish 2 cases:

• I build for me, so I don't care about feedback
• I build for others and the user feedback is gold

An index of the web.

92 editors, ~ 1 million categories and ~ 3 million websites

When you develop a major new feature, product, anything, one of the defining characteristics is that you don't know what you're building. The only way you know what you're building is if you've built it before.

This leads to a problem: If you don't know what you're building, how do you know where the rough edges are? How do you know what the design demands, and what technical decisions to make?

It has both UI and cli. It can be useful someday.

The 512KB Club is a collection of performance-focused web pages from across the Internet. To qualify your website must satisfy both of the following requirements:

1. It must be an actual site that contains a reasonable amount of information, not just a couple of links on a page (more info here).
2. Your total UNCOMPRESSED web resources must not exceed 512KB.

A single irreducible unit or component in a larger system.

This definition makes sense to me:

• an atomic note describes only a singular idea or concept (that can not be split without breaking its sense)
• an atomic habit is a regular practice that is small and easy to do
• Atomic design reduces design down to their foundational building blocks of all user interfaces

Or the limit of altruism:

As lovely as it might seem, our selfless actions usually get prioritized above looking after ourselves.

We will go to unending lengths to look after the ones we love, and even the ones we don’t. We are empaths, we want the best for everyone, so we do our best to try and give them that, usually to our own detriment through self-neglect.