2026-05-05 22:22 UTC
i absolutely love @11ty and what they’re doing with @fontawesome to try and make open source more sustainable!!
one thing i am very interested to know tho would be how accessible build awesome pro is. whether wcag and atag were considered during the design and development of build awesome pro with all these features with complex user experiences 😬🤞🏻 https://mastodon.social/@fontawesome/116500155282329632
Replies (1)
-
@zachleat@fediverse.zachleat.com 2026-05-06 14:01
@elly@front-end.social @11ty@neighborhood.11ty.dev @fontawesome@mastodon.social Thank you for the support!! We’re in *active* development on this new platform and having an accessible editor is a very important goal. We did talk about WCAG a little bit yesterday on the stream (if you caught it): https://www.youtube.com/watch?v=XBMSvupE7Bc But maybe the strongest case I can make is our Accessibility Statement (which has been on the site for a very long time): https://www.11ty.dev/docs/accessibility/