I’m glad to see popular voices in the web space reflecting on how the web is seriously broken as a whole with regard to accessibility, but then there’s a part of me that’s screaming “Hey, accessibility advocates have been screaming at the top of our lungs about this for decades.” Not only have we rewarded the wrong things on the web, (aesthetics over everything else and at the expense of everything else, for example), but I think in a lot of ways we’ve rewarded the wrong voices. So many times it’s the not-so-popular voices who have been telling us what we really should be hearing, and because we think it’s too hard or not enough of a priority, (see internationalization and localization, or security, or accessibility, or translation), we put it off until we have something like the recent WebAIM survey of how abysmal the state of accessibility with regard to websites is to publicly shame us into doing the right thing. Maybe one day we’ll learn.
Dear fellow screen reader users. If you’re tempted to declare something accessible because you can use it, please keep this in mind before you make said declaration. “Works with my favorite screen reader” or “works with all screen readers” or “works with a particular screen reader as long as you use object navigation or route your Jaws cursor to your PC cursor” are not measurrable accessibility indicators. Accessibility is not just about screen reader users. Accessibility is about all people with disabilities. And the gold standard, inclusive design, is about everyone, including people with disabilities.
Happy thirtieth birthday World Wide Web. You may be held together by peanut butter and goblins, but you’ve provided so much joy and prosperity for all of us who have careers thanks to you. I promise to promote your health through the standards that make you great and enjoyable for everyone on this earth, and to encourage everyone who builds things on your foundation to do the same.
Read ( )
The trend under discussion in this long read is very real and results in all sorts of problems, including metric tons of technical debt and support costs. this is what happens when what I’ll call Shiny Object Syndrome takes the place of good decision-making.
Bookmarked The Mailto Link Generator by Michael Mckeever (Mailto Link Generator)

Mailto link code and markup generator with subject, body, cc and bcc. Quickly and easily generate code for those annoying mailto links.

Clickable email addresses which allow your site’s visitors to send you email, (otherwise known as mailto links), can be quite handy, and they’re easy to generate if you type HTML as if it’s your first spoken language. If you don’t do that, they can seem like the hardest thing to create, and you have a couple of options for creating them: Google what you need and then save that information in a place you’ll hopefully remember, or just use this mailto link generator. Simply fill out the form appropriately, generate the HTML you need, and copy and paste. Note that if you’re doing this using a WordPress installation, you’ll want to switch your editor to the code view if you’re using the Classic Editor, or use the custom HTML block if you’re using the editor as of WordPress 5.0. You can also insert your generated mailto links in the custom HTML widget for use in any widgetized area your theme provides. See this post for a complete guide to WordPress widgets, which includes a section on the custom HTML widget.
Read Grep for forensic log parsing and analysis on Windows Server IIS by JAN REILINK

How to use GnuWin32 ported tools like grep.exe and find.exe for forensic log file analysis in Windows Server. In this article I’ll give some real live examples of using these ported GnuWin tools like grep.exe for logfile analysis on Windows servers. The article provides three example, as an alternative to LogParser, because finding spam scripts fast is often very important.