#screenreaders
Live, measured metrics for the hashtag #screenreaders from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #screenreaders
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 05:47 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 05:47 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 05:47 UTCEverything below is measured over the latest 40 public posts (spanning ~2286 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (37) · Spanish (1)
Avg boosts / post: 5.8
Top of the latest posts
Stylized unicode text is decorative noise to a screen reader. Characters like 𝓕𝓪𝓷𝓬𝔂 aren't styled text to AT, they're gibberish pulled from entirely different Unicode blocks. Every dev and designer using these in usernames, bios, or UI
Modern TUIs claim to be minimalist and efficient. But for screen reader users, they're a nightmare. This breakdown shows why text-mode interfaces break accessibility assumptions and what needs to change. #accessibility #screenreaders #cli h
I am having a problem signing in to my Ebay account. It keeps asking me to check a checkbox. I do so, and then, it gives me an inaccessible captcha with no audio alternative. I tried this on Windows 7, 10, and 11, with Firefox and Supermium
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/screenreaders