![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Is there any kind of across-the-board best-practices guide for accessibility in web development?
(I'm thinking about tags and whether screen readers try and ignore them and whether that harms the Authentic Tumblr Experience for non-sighted people - because some of the tags are tags, but some are instead marginalia. Or, in tanb...... slime man terminology, "marg targs."
I'm aware that that particular thing's not the first priority! It's just, for optimization purposes, I was thinking I might try to ruin the subversive thrill that comes from misusing tags by classifying some tags as marg targs and thus not trying to index by them, which led to thoughts about whether the marg targs should/could be marked up differently somehow so as to be caught by screen-readers.)
no subject
Date: 2015-11-07 03:01 am (UTC)no subject
Date: 2015-11-07 05:21 am (UTC)i wonder about going old-school-markups-for-marginalia? which I'm on post-op meds right now so it's hard to tell if that will make sense in the morning. but. like footnotes almost? or something something. also giving them a break between words so the screenreader doesn't freak out when pronouncing them.
no subject
Date: 2015-11-07 08:43 am (UTC)It wouldn't stop people using tags tumblr style entirely, though: look at the Ao3, which has the author's notes serving a similar purpose, in contrast to the summary, and still gets tumblr style tags sometimes. But it would make making marginalia easier.
I hope that made sense I am super tired.
no subject
Date: 2015-11-07 03:05 pm (UTC)Like what a lot of sites do with their navigation -- have a "skip to content" link at the very beginning of the page, visually hidden by the CSS, but screen readers will land on it first.
Also, I love the idea of having separate sections for "site-wide tracking tags" and "just for your own blog tags". Have wished for a long time that Tumblr (and Dreamwidth, for that matter) had a functional way of splitting those up.