Curtis Wilcox

Digital accessibility developer in higher ed

Language: English 🇺🇸
Location: Boston, Massachusetts USA
GitHub: https://github.com/extra808

Last Notes

2026-07-01 14:50:54 CEST

- reply

If the '137' in that sea of version data is the Firefox version number iceraven is equivalent to, Firefox didn't add support for `font-variant-emoji` until version 141.
Given they're decorative, no icon at all seems like an okay fallback to me.
`https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/font-variant-emoji`
@npub1jpy…yfwv @npub1gly…x4dg @npub1t46…wpm3

2026-07-01 13:59:03 CEST

- reply

I was getting the fallback in Firefox as well, same versions (also in Firefox 151.0.1 for macOS).
@npub1jpy…yfwv
https://s3.c.im/media_attachments/files/116/844/587/939/868/218/original/8b2bc2245c5fcc42.png

2025-08-12 14:20:37 CEST

- reply

Printing and scanning are both handled by OS systems, individual apps don't need to be looking for networked devices.
@npub1jpy…yfwv

2025-04-12 00:51:03 CEST

- reply

Microsoft Edge for all platforms added a Page Colors setting in the Fall, it affects it like Windows Contrast themes do. It has the same theme choices as Windows, plus "White." It doesn't have a UI for creating custom themes.
Firefox's Manage Colors setting also does `forced-colors`.
I collected information about testing the color and contrast user preferences on a page. The two above browser features are user-friendly ones, unlike the Chromium's emulators in the DevTools Rendering pane.
https://codepen.io/ccwilcox/full/YPzraqb
@npub1ftx…yzsr

2025-03-06 02:00:07 CET

- reply

It's more of a "man bites dog" story, the U.S. has more actual disputes with Mexico.
An article I saw had Mexico agricultural imports at about $39 billion. Still a lot.

2024-12-18 14:24:25 CET

- reply

The question is about designing a low contrast *mode*, when a site has different themes users can choose from.
The only guideline I can think of is color combinations in a low contrast theme should still meet WCAG color contrast guidelines.
The problems with users relying on their display brightness include:
1) The brightness of some displays doesn't go that low.
2) Brightness controls on some displays are difficult to use.
3) Changing display brightness changes all colors equally so bright things become dimmer but already dim text could become unreadable.
@npub197g…q2n4

2024-12-10 18:33:39 CET

- reply

Scalzi writes both serious and funny SF. Of the funny ones, "Redshirts" won a Hugo award but I think I preferred "Kaiju Preservation Society." If it matters, the latter is available as a part of Kindle Unlimited.
@npub1x59…gect

2024-10-03 14:08:49 CEST

- reply

I think styling links based on their destination is seldom useful and have some accessibility challenges.
The external link example is missing `::after` but it would add the name of the Unicode character, "Northeast arrow with variation selector 16," to those links, pretty annoying for a screen reader user.
All major browsers now support alternative text in `content` but that's new so a fallback is called for.
```CSS
a[href]:not([href^="https://shkspr.mobi" I])::after {
content: "(external)";
content: "↗️" / "(external)";
}
```
https://caniuse.com/mdn-css_properties_content_alt_text

2024-09-28 16:43:37 CEST

- reply

The macOS Keyboard Navigation toggle doesn't change keyboard navigation inside Safari viewports, you can have it on and links still won't be included in the tab order, only Safari's "Press Tab…" preference changes that.
The Keyboard Navigation toggle does change keyboard navigation of controls on the Safari browser window (Back button and such). It does the same to Chrome but Firefox's browser controls are always keyboard navigable.
@npub10u2…dp4q

2024-09-28 16:28:00 CEST

- reply

Apparently Safari added "Press Tab to highlight each item on a webpage" as a preference in 2011.
https://osxdaily.com/2011/08/14/enable-tab-key-navigation-safari/
Before then and even today, when that's not enabled, you can still include links in the focus order by pressing Option+Tab instead of Tab.
@npub10u2…dp4q

2024-09-27 21:30:36 CEST

- reply

I think the Mac vs. Windows difference goes back to their origins in the Eighties.
The Mac made the mouse a mainstream input device, it was GUIs and mouse-first interaction from Day One.
Windows was a layer added on top of DOS, a command-line OS. Having a working mouse was not guaranteed and using command line, at least a little, was a necessity until at least Windows 95.
Therefore by default macOS only provides keyboard operation for the most commonly desired tasks.
@npub1d4w…2d8t

2024-09-27 19:46:07 CEST

- reply

You can tell us what exactly is different on macOS about enabling Keyboard navigation and enabling Full Keyboard Access (FKA).🙂
All I've noticed about FKA is it provides a more visible focus indicator and it's enabled when VoiceOver is enabled.
@npub1d4w…2d8t