When looking for a job, it can be tricky to know what to ask for in terms of salary, especially for underrepresented minorities, who are routinely under leveled and underpaid. So I thought it would be useful to share my salary history since becoming a software engineer, in hopes that it will help someone at some point.

The author of https://carol.gg/salary/ shares their salary too

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!

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.

1. Having an "inbox" notes to capture ideas in form of napkin, receipt, voice recorder
2. Literature notes: When you consume content, take notes of what you don’t want to forget or what you want to use in your own writing. It is recommended to make them atomic. Make sure to include the bibliographic details, author & source at the very least, so you know where you got the idea from.
3. Permanent notes: every day, you should go through the inbox and seek to refine the fleeting & literature notes. Making connections and turning them into permanent notes.

One idea = One note
One note = One idea

4. Navigation: an index allows you to navigate in the zettelkasten; keyword notes can also be used as link.

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.

People do not experience the same sense of the flow of time. For some, only now and not now exists.

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.

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.

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.