Notices by Mayank (hi_mayank@hachyderm.io)

firefox will now track your searches by default and you'd have no way of knowing they're doing that unless you look for this random blog post on their website: https://blog.mozilla.org/en/products/firefox/firefox-search-update/

it does look like you can turn it off at least.

@aral this talk is excellent! you really have a way of telling an engaging story

@binarydigit some of those websites look incredible!

i still can't believe this is something mozilla made https://www.mozilla.org/en-US/firefox/family/

@aral i wrote a blog post you might find handy if you're looking into bun https://www.mayank.co/blog/bun

@aral@mastodon.ar.al one small suggestion: you might want to create a ToastWrapper that's always in the page, because live regions should generally be present *before* sending updates

see https://www.sarasoueidan.com/blog/accessible-notifications-with-aria-live-regions-part-2/#make-sure-the-live-region-container-is-in-the-dom-as-early-as-possible and https://www.scottohara.me/blog/2022/02/05/are-we-live.html

@aral how does a screen-reader user get notified of the toast message?

The easiest way to introduce #CSS cascade layers into your existing codebase today:

1. Move your CSS resets into a layer named "reset".
Because the selectors in your reset should already be pretty weak, there should be almost no net effect.

2. Move (some of) your third party styles into a layer named "thirdparty".
Third-party styles should already have lower priority than your own styles, so this again has very little impact.

All the rest of your styles can continue to stay unlayered.

@tixie i have some more 😄

@aral i'm curious about the choice to use JS interpolation syntax (`${SLOT}`) inside the fragment markup, vs just using HTML (`<my-slot>` or `<Slot>`) 🤔

proton halved the price of their password manager because they made too much money

https://proton.me/blog/proton-pass-price-change

would anyone be able to tell me difficult it is to contribute code to browsers? specifically to browser devtools (which are web-based afaik, and therefore fits my skillset)

is the entire process documented somewhere? from initial proposal/discussion, all the way up to implementation and release?

there's so many little UX improvements that can be made in devtools (across all browsers!), and i feel like community contributions can really help for these relatively low-risk tasks

@rimu you probably want to use the prefers-contrast media query for that, rather than `title`

cool but obscure api: "alternative stylesheets" https://developer.mozilla.org/en-US/docs/Web/CSS/Alternative_style_sheets

@aral browsers should be publicly funded/owned. they're too important to be controlled by corporations

for those in the back: alt text stands for "alternative" text, which means it should be sufficient on its own in absence of the image.

if your alt text misses or fails to emphasize the most important parts of the image, it's not "alternative" text, it's just text.

maybe the fundamental disconnect here is that instead of seeing disabled people as human, techbros see them as a problem that can be "solved" by using more computers

if you're gonna use AI to generate alt text, at least verify it before posting

i've found two instances in the last 24 hours, where someone used AI-generated alt text that *completely* misses the point of the image

worse even, both of these individuals bragged about it, as if they deserve some kind of award for generating shitty alt text

@fuchsiii @GreenSkyOverMe 👀

tech is dominated by cis white dudes, and tech blogs more so. in more specialized domains (like accessibility), it's even worse.

when writing my last blog post, 90% of the resources i linked to were written by white dudes.

if you're part of a group that's underrepresented in tech, i would love to see your blog. if you don't have one, consider starting one (i can help!)

@andrewt see https://tech.lgbt/@jenniferplusplus/110810004825031334