fuchsiaaaaaaaaaaaaaaaaa
(boosts highly appreciated)
I'd like to read up on best practices for #accessibility on web stuff, both static pages and web applications. Are the Mozilla resources on ARIA the best there is?
#a11y
@f0x imo the best way to be accessible is to not use JavaScript and keep your content as simple as possible. Bonus points if you put alt tags on all of your images and add a "skip to content" link upfront that links past the nav et al
@sir yes, for static site (blogs etc) that is definitely my go-to way. For actual web *applications* that's not really an option
@f0x sourcehut manages to be a pretty complex and featureful application without javascript or webshit
@sir again, this is not what I was asking for.
@f0x if you question your assumptions about what good software looks like, you will find it much easier to make it acccessible.
@f0x While I don't know the ins and outs of development, design to avoid emoji spam - screen readers read them off descriptively so when users insert them repeatedly into text strings or draw stuff with them it spits out a lot of garbage. Also, avoid pictures of text outside of simple logos - screen readers will not be able to read it unless it is also tagged with a separate description.
Links I got from joepie91:
https://imgur.com/gallery/f2vj5
https://accessibility.blog.gov.uk/2018/05/15/what-we-learned-from-getting-our-autocomplete-tested-for-accessibility/
https://github.com/colorjs/make-color-accessible
https://github.com/pa11y/pa11y
https://www.w3.org/WAI/standards-guidelines/wcag/