zichy

Three more facts about the song Clint Eastwood:

1. The drum beat is just the Rock 1 preset of the Suzuki Omnichord: https://www.youtube.com/watch?v=EDX6l9_58RA

2. Del tha Funkee Homosapien wrote the full lyrics in 30 minutes with the help of the book "How to Write a Hit Song": https://www.youtube.com/watch?v=Qq2qSq6NpNY#t=373

3. The first version of the song didn't feature Del, but the British group Phi Life Cypher: https://www.youtube.com/watch?v=ZM-DK3b5yuo

A lefty professor who likes trade unions sounds like a horrible person! /s

Exactly this. In terms of recording quality, my approach would look something like this:

1. Use a decent microphone.

2. Make sure you know how to handle the microphone.

3. Use closed-back headphones.

4. Record in a suitable environment/studio.

5. Consider adding a video track as well.

AI tools can't make okay-ish video recordings suddenly look great.

Yes, I opened the CSS file and there it was.

Think about screen readers.

You may want to look up the CCC‘s founding history.

Do you realize that a forum is social media?

Not sure if you are trolling.

What do you mean by censoring and why did you put transphobic in quotation marks?

You seem to be very sensitive to the idea of people watching out for each other. Maybe you should start watching out for others so you can get rid of your sensitivity.

It is really easy to protect everyone's privacy by not using advanced analytics platforms at all.

As one user said before, this absolutist way of thinking is tiring. Hamburger menus can absolutely be accessible and I would have liked to read how to do so. Here's my take:

  * It uses valid HTML and JS. (You could also make it work without JS as a fallback and I love progressive enhancement, but it's not a requirement specifically for accessibility. Actually, JS can contribute a lot towards accessibility.

  * The toggle button uses either `title`/`aria-label` or visual text in addition to the ≡ icon.

  * The focus states are clearly visible for keyboard navigation.

  * The correct ARIA attributes for the interactive elements are used.

  * Depending on the menu, think about a focus trap/loop.

Bonus tip: While I prefer using `<button aria-expanded>` since I believe it is more accessible for screen readers, you can also use `<input type="checkbox">` + `<label>`. If you have to do it this way, please do no use `display: none` on the checkbox input – this will make it unusable by keyboard. It should be only hidden visually.

Well, if we're talking about links in continuous text, they should definitely be underlined. Otherwise, they fail the WCAG success criterion 1.4.1.[1]

[1]: https://www.w3.org/TR/WCAG20-TECHS/F73.html