Thread with 7 posts
jump to expanded post
Today in βseeing the cracks in every wallβ: why do web accessibility APIs actually just not fucking do anything whatsoever
What's even the point of annotating a blogpost with accessibility markup if it won't even do anything?
Will not elaborate, sorry; suffice to say a situation was encountered where something done for sighted readers' enjoyment caused a webpage to become unusable for screen readers; the ARIA markup was added; and then it turns out the ARIA markup does nothing at all on this laptop?
This feels a lot like when we discovered that the most basic of things in Japanese typography β furigana positioned to the right of vertical text β actually still doesn't fucking work in modern web browsers, because they're made by white dudes in San Francisco, always, forever.
Or, you know, like how we are constantly reminded by our multilingualism and living-in-the-European-Union that nobody who writes software has ever step foot outside of a monolingual America-centric existence, clearly.
it's bleam
@hikari this works?
<span style="writing-mode: vertical-rl"><ruby>ζ₯ζ¬θͺ<rt>γ«γ»γγ</rt></ruby></span>