#accessabilitymatters
Live, measured metrics for the hashtag #accessabilitymatters from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #accessabilitymatters
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 · mastodon.online (Mastodon public tags API) · fetched 2026-09-30 15:08 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-09-30 15:08 UTCNo related tags with measured usage found for #accessabilitymatters.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-30 15:08 UTCEverything below is measured over the latest 12 public posts (spanning ~2135 hours).
Posting hours (UTC) — busiest: 22:00
Languages: English (11) · Dutch (1)
Avg boosts / post: 2.3
Top of the latest posts
#Disabledjoy #access #nature #birdwatching #accessabilitymatters I love this piece about bird watching and accessible trails for folx who are blind: https://www.sciencefriday.com/segments/blind-birder-accessible-colombia/ Juan Pablo Culasso
There was an attempt... This is why you almost never see any wheelchair users or vision impaired individuals utilising public spaces in Australia. Even newly constructed features aren't always fully adapted for everyone's needs... #accessab
I try to use only Camel case hashtags, but most hashtags in the system are plain written (all under cast), even #camelcaseyourhashtags. So the list that comes up when typing one is mostly useless. Would be nice if there is a way to transfor
#accessabilitymatters across platforms
every network with a public tag surfaceFollow #accessabilitymatters straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/accessabilitymatters