syndicate

content/notes/firefox-focus-ring-regression.md

@@ -0,0 +1,15 @@
+---
+title: "Firefox focus ring regression"
+date: 2023-10-31T05:11:06-07:00
+syndicatedCopies:
+    - title: 'The Fediverse'
+      url: 'https://pleroma.envs.net/notice/AbKRMDqztwWekHX4qG'
+    - title: 'IndieNews'
+      url: 'https://news.indieweb.org/en'
+---
+
+Firefox 120 appears to have regressed to its older WebKit-like blue focus outlines; it briefly had dual-color white-and-blue outlines.
+
+I'd previously advised certain sites (sites with background colors that have poor contrast against the focus-ring's blue color) to override the default focus indicators. I planned to temper that advice since Chromium and Firefox adopted focus indicators that appeared visible on a variety of background colors; I suppose I should cancel those plans.
+
+As long as people have to use defaults they didn't choose (e.g. Tor Browser users are stuck with default settings), we have to override them when they're inaccessible. We can't count on users to always have the means to do this: fingerprinting concerns and device-borrowing are facts of life.

content/notes/real-name-policies.md

@@ -0,0 +1,23 @@
+---
+title: "Real name policies"
+date: 2023-10-31T06:31:21-07:00
+replyURI: "https://fosstodon.org/@drewdevault/111329549329662520"
+replyTitle: "Send me your thoughts on “real name” policies in free software contributions"
+replyType: "SocialMediaPosting"
+replyAuthor: "Drew Devault"
+replyAuthorURI: "https://drewdevault.com/"
+syndicatedCopies:
+    - title: 'The Fediverse'
+      url: 'https://pleroma.envs.net/notice/AbKpVF5i61wfz25CPg'
+    - title: 'jstpst'
+      url: 'https://www.jstpst.net/f/just_post/8983/real-name-policies'
+    - title: 'IndieNews'
+      url: 'https://news.indieweb.org/en'
+---
+
+The primary, hopefully-unintended function of a "real-name policy" is to exclude people and make people *less* genuine. Many aren't at home with the name deemed by society to be "real".
+
+There's plural systems. And trans users who haven't made a full break from their deadname(s) yet. And at-risk users who would be doxed by such a policy. And folks who simply feel more comfortable with online handles than meatspace names, for no special reason in particular.
+
+What incredible benefits could be worth shafting all these people? Assuming you even manage to pull it off; see {{<mention-work itemtype="TechArticle">}}{{<cited-work name="Falsehoods Programmers Believe About Names" url="http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names" extraName="headline">}} by {{<indieweb-person first-name="Patrick" last-name="McKenzie" url="https://www.kalzumeus.com/" itemprop="author">}}{{</mention-work>}}.
+

content/notes/wcag-2.2-and-validation.md

@@ -4,6 +4,8 @@ date: 2023-10-06T07:25:37-07:00
 syndicatedCopies:
     - title: 'The Fediverse'
       url: 'https://pleroma.envs.net/notice/AaUoV6qqBhRIAqApxw'
+    - title: 'IndieNews'
+      url: 'https://news.indieweb.org/en'
 ---
 
 <abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.2 removed [SC 4.1.1, Parsing (Level A)](https://www.w3.org/WAI/WCAG21/Understanding/parsing.html). I maintain that valid markup has important benefits despite no longer being required. We may find it *possible* to write good software without static analysis, construct a building without blueprints, or make an accessible website without validation. They remain good practices.