Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://macaw.social/users/sommer/statuses/113499092084836157">Sommer Panage (sommer@macaw.social)'s status on Monday, 18-Nov-2024 01:32:13 JST</a><a href="https://macaw.social/@sommer" title="sommer@macaw.social"><img src="https://gnusocial.jp/avatar/115267-48-20230427213200.webp" width="48" height="48" alt="Sommer Panage" style="position: absolute; left: 0; top: 0;">Sommer Panage</a><div><ul><li></ul></div></section><article><p>Grateful to <a href="https://mastodon.social/@muan">@muan</a> for sharing her story. So often companies let <a href="https://macaw.social/tags/accessibility" rel="tag">#accessibility</a> become an unsupported labor of love from one or two employees who care deeply—without resources, title, or training. This has happened to me as well as others I know. </p><p>It’s unfair to people who rely on accessibility. </p><p>And so companies skate by with this model until “something” happens: a law suit, a major acquisition, etc., only then to start taking aaccessibility seriously. <a href="https://mastodon.social/@muan/113494844740565000" rel="nofollow noreferrer">https://mastodon.social/@muan/113494844740565000</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4017511#notice-7850596">In conversation</a><time datetime="2024-11-18T01:32:13+09:00" title="Monday, 18-Nov-2024 01:32:13 JST">about 9 days ago</time> <span>from <span><a href="https://macaw.social/@sommer/113499092084836157" rel="external" title="Sent from macaw.social via ActivityPub">macaw.social</a></span></span><a href="https://macaw.social/@sommer/113499092084836157">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: files.mastodon.social</div><h5><a href="https://mastodon.social/@muan/113494844740565000">Mu-An (@muan@mastodon.social)</a></h5><div> from <span>Mu-An</span></div></header><div>Attached: 1 imageI started doing accessibility at GitHub when it had a flat structure (2013) and no one was telling me what to do. In my free time I will just browse the issue backlog and find things I could do. Eventually, I found that there are tons of accessibility issues that are just stale, and a lot of them were just like: this icon button isn’t labeled. I looked at them and thought oh that’s easy. I will fix it.At one point I added so many aria-labels that AT users got mad that they’re getting misused.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Sommer Panage (sommer@macaw.social)'s status on Monday, 18-Nov-2024 01:32:13 JSTSommer Panage
- Mu-An
Grateful to @muan for sharing her story. So often companies let #accessibility become an unsupported labor of love from one or two employees who care deeply—without resources, title, or training. This has happened to me as well as others I know.
It’s unfair to people who rely on accessibility.
And so companies skate by with this model until “something” happens: a law suit, a major acquisition, etc., only then to start taking aaccessibility seriously. https://mastodon.social/@muan/113494844740565000
In conversationabout 9 days ago from macaw.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: files.mastodon.social
  Mu-An (@muan@mastodon.social)
  from Mu-An
  Attached: 1 image I started doing accessibility at GitHub when it had a flat structure (2013) and no one was telling me what to do. In my free time I will just browse the issue backlog and find things I could do. Eventually, I found that there are tons of accessibility issues that are just stale, and a lot of them were just like: this icon button isn’t labeled. I looked at them and thought oh that’s easy. I will fix it. At one point I added so many aria-labels that AT users got mad that they’re getting misused.

Public

Embed Notice

HTML Code

Corresponding Notice