Straight white male privilege (from the far right) is this: To be able to stand 50 people in front of a school in military uniform with automatic weapons in hand and not be bothered by the police.

(from https://sebsauvage.net/links)

1. Due to color vision deficiencies, it’s a good idea to always complement error messages with an icon
   • Additionally, it might be a good idea to guide users towards specific issues of the form with an error summary.
2. Never cover user inputs
   • First of all, we avoid tooltips that open on hover and display the tooltip only once tapped or clicked.
3. Error message position:
   • they should be placed above input for various reasons, but it costs layout shifts. In doubt, a collapsible accordion instead might be a better idea there.
   • they should be placed inline in tables. One of the simpler patterns is to display the error message in the same row where the content lives.
4. Avoid toast error messages
5. Establish stop-words for your error messages: they should never be used. See Error messages
6. Provide Examples Of Correct Input or guide the user to the expected input. For example, "IBAN starts with the country code. For example, DE or AT.
7. Display Error Summary on the top
   • Additionally, you might want to adjust the favicon and the title of the document if errors do appear,

Using the tool gitfive.

Legit

About design:

1. Less is more: the content will be more important
2. 5x5 rule: Maximum 5 lines of texte for a slide, and maximum 5 words per line.
3. Show, don't tell: group together, use size, color, font, bold, etc...
4. Fonts: Outfit, Montserrat, Lato, Fira, Roboto, Opan Sans, Poxima, Circular
5. Illustrations: Pixabay (https://pixabay.com/fr/), Unsplash (https://unsplash.com), stocksnap (https://stocksnap.io), Undraw (https://undraw.co)
6. Icons: Flaticon, TheNounProject (https://thenounproject.com/)
7. Figma or Adoe XD can help to create the slides

A simple, consistent open-source icon set designed to be used in a wide variety of digital products.

First feedback: 130km/h to 110km/h
Time travel (hours): 3.15 to 3.35
Consumption (liters): 31.23 to 17.18

It seems to be relevant depending of the vehicle of course.

Another testimony:

• 5.7-6.0 liters to 5.2 liters

How to build common ui patterns that are accessible 👍

Create an accessible color palette based on criteria AA

Un mensonge en deux actes

A calculator for everything, every usage.

This is in large part because HTML is a limited hypertext. In particular:

• Only <a> and <form> can make HTTP requests
• Only click & submit events can trigger them
• Only GET & POST HTTP Methods are widely available
• A request must replace the entire screen, leading to a clunky and sometimes jarring user experience

To the last point: the transition API is on its way :)

En dessous de 17°C je ressens le froid au quotidien (à 18°C je me sens encore bien). Et le pire c'est pour le télétravail : sous les 19°C c'est difficile d'être à l'aise.

Idem. Effectivement, un simple chauffage d'appoint peut suffire: 19 degrés est confortable pour le travail. 18 sinon.

LOL. Wrap a IP protocol into HTTP 🤯

Check the interaction is ok

The Selection control ecosystem flow chart has a great tree-choice to display the expected field component.

Which errors or alert message should be used?