Forge allows vanilla #Jira development but it also means packaging wasm versions of Doom and Quake is possible.
Other #weba11y projects too, like DuckDB. Want to run SQL queries on a subset of Jira data without Atlassian Analytics? Or WinAmp?

🚨 The State Department’s Font Flip:
A Step Back from Accessibility 🧑‍🦯❌♿
—ditching accessible Calibri as "woke."

Earlier this week, the U.S. State Department announced its decision to abandon Calibri—the sans-serif typeface adopted under the Biden administration—in favor of Times New Roman. The internal memo framed this as a "return to consistency," but I see it as something deeper: a symbolic retreat that elevates tradition above accessibility, inclusivity, and the promise of open standards. As someone who values thoughtful design in public institutions, I find this choice disheartening, yet it compels us to examine what typography truly demands in a digital age.

Typography transcends mere aesthetics; it fundamentally shapes how we read, perceive authority, and feel included in vital conversations. When a government agency alters its typeface, that shift signals its core priorities. The reversion to Times New Roman, a serif font rooted in print-era conventions, risks turning typography into another cultural flashpoint. I sincerely hope this does not herald a broader precedent, but instead sparks a return to evidence-based decisions that serve every one.

From Courier to Calibri: A Brief History of State Department Fonts

The State Department’s typography has mirrored the evolution of bureaucratic communication. For decades, Courier New—a monospaced font introduced in 1955—reigned as the default, embodying the analog world of mechanical typewriters, carbon copies, and precise diplomatic cables. Its uniform spacing delivered egalitarian functionality, aligning every character perfectly for legal drafts and official forms.

In the 1980s and 1990s, as computers reshaped offices, Times New Roman took over. Crafted in 1931 by Stanley Morison for The Times of London, this serif typeface excelled in dense newspaper columns and fine print, projecting the conservative professionalism suited to diplomacy. Yet it was engineered for ink on paper, not the glowing pixels of screens that define our era.

By the early 2000s, legibility studies championed sans-serifs like Arial and Calibri for digital dominance. In 2023, the Biden administration embraced Calibri precisely for its superior on-screen clarity, accessibility, and visual ease—aligning with best practices from the GSA and Department of Education. Part of the humanist grotesque family (think Helvetica's lineage, tracing back to Akzidenz-Grotesk in 1898 or Highway Gothic on U.S. road signs since 1948), Calibri marked genuine progress. The sudden pivot back to Times New Roman strikes me as nostalgia over necessity, undermining hard-won advances in inclusive design.

The Return to Times New Roman: Symbol Over Substance

Officials tout this revert as tradition preserved, but I contend tradition must yield to accessibility. Serif fonts shine in print, yet on modern screens—especially low-resolution or small displays—they falter for those with low vision or dyslexia. The British Dyslexia Association and Bainbridge Group on Visual Legibility affirm that sans-serifs, with their clean, uniform strokes, ease reading and curb fatigue across diverse users.

Consider Times New Roman's subtle distinctions between "I," "l," and "1"—they blur digitally, inviting confusion. Bainbridge and MIT’s AgeLab research underscores how uniform strokes and open apertures accelerate comprehension in electronic documents. By clinging to this proprietary relic, the State Department bypasses free, open-source gems like IBM Plex, Source Sans, or Lato, which offer transparency and adaptability. Thailand’s 2006 font competition, producing 13 national standards, proves governments can innovate boldly. This choice feels like a step backward, favoring the familiar over forward momentum.

The Science and Soul of Accessible Typography

Accessible typography is human-centered design at its core, backed by decades of research into font shapes, spacing, and character clarity for all readers, impaired or not. Fonts like OpenDyslexic, with weighted lower halves to prevent letter inversion, and Atkinson Hyperlegible, which sharpens distinctions between confusable characters like 0/O or 6/b, lead the way. Developed by the Braille Institute of America with Applied Design Works, Atkinson enhances accuracy and speed for dyslexic and neurotypical alike, all without aesthetic compromise.

Here’s my personal preference: Atkinson Hyperlegible is my favorite—it captures the open, modern inclusivity government design demands. Best of all, its SIL Open Font License makes it free and available for public, governmental, and educational use, unlike the corporate shackles of Calibri or Times New Roman.

Why Accessibility Matters in Public Typography

For institutions like the State Department, clarity is no luxury—it's a democratic imperative. Diplomats, journalists, and citizens alike deserve documents free of strain, legible across aging eyes, reading differences, and global devices. Times New Roman, born for 1930s newsprint, dismisses these truths, broadcasting detachment from digital realities. Accessibility isn't political posturing; it's practical humanity, the bedrock of public-spirited communication.

---
References

- British Dyslexia Association. Dyslexia Style Guide 2022: Creating Dyslexia-Friendly Content.
- Braille Institute of America. Atkinson Hyperlegible Study. (2021).
- Bernard, M. et al. “A Comparison of Popular Online Fonts: Which Size and Type is Best?” Usability News, Wichita State University (2003).
- Morison, S. A Tally of Types. Cambridge University Press (1939).
- MIT AgeLab. “Typography and Visibility on Digital Displays.” (2014).
- Shaikh, A. (2007). “Impact of Typeface Design on Legibility and Reading Comprehension.” Behavior & Information Technology.

#InclusiveDesign #StateDepartment #Courier #TimesNewRoman #Calibri #A11y #Typography #Accessibility #A11yMatters #DesignForAll #WebA11y #StateDeptFontFail #FOSS

#HTMLの最良の秘密: `<output>`タグが示す未来のWebアクセシビリティ✨ #HTML5 #WebA11y #FrontendRevolution #十12

doping consomme blog

Controversial opinion, but I think WCAG 2.0 and WCAG 2.1 should be marked as superseded by WCAG 2.2. There are zero reasons to use the former 2, and anyone who needs to use 2.0 or 2.1 (because they live in 2018) can just ignore the new provisions in 2.2.

There is zero use in dragging the old versions and their supporting documents around.

#weba11y #a11y #accessibility

🚨 New article just dropped!
Accessibility overlays are marketed as quick fixes—but they often create more barriers for disabled users. I explain the risks, my personal experience, and what real accessibility looks like.
Read here: https://taylorarndt.substack.com/p/accessibility-overlays-are-not-the
#Accessibility #WebA11y #InclusiveDesign #BlindTech #DisabilityRights
Accessibility Overlays Are Not the Answer: The Illusion of Compliance in the Digital Age

Accessibility Overlays Are Not the Answer: The Illusion of Compliance in the Digital Age

Taylor’s Substack
Hey #a11y #webA11y folks, suppose I have a form with a button that opens a mini-form in a popover or dialog. Does it make sense to stick things like `aria-required` or `aria-invalid` on that button if things in the mini-form are required / invalid?
Bluesky

Bluesky Social

Hey #a11y folks, suppose I have a form with a button that opens a mini-form in a popover or dialog. Does it make sense to stick things like `aria-required` or `aria-invalid` on that button if things in the mini-form are required / invalid?

On one hand, this feels semantically wrong? The button itself is just a trigger and can't really be "invalid" in anyway. On the other, since the actual invalid elements are in the popover or dialog, there's no other indication of this state (apart from manual descriptions).

#aria #web #weba11y #accessibility

Please don't auto-close accordion sections! You're gonna make me sick. 😣

https://ashleemboyer.com/blog/should-accordions-auto-close-sections

(*whispers* I think you should avoid accordions 99% of the time but that's a different topic for a different post.)

#Accessibility #A11y #WebAccessibility #WebA11y

Should accordions auto-close sections? | Ashlee M Boyer

Only if you want them to be harder to use.

ISO feedback!

Launching new mini services this week. Creating example deliverables now.

What you want to see in the example if you were considering one of these services?

Already on my mind:
- Related WCAG SC & level
- Priority/impact of issues
- Clear steps how to fix
- How to validate fixes

#Accessibility #A11y #WebAccessibility #WebA11y