@mahryekuh Well if I can help with any context/thoughts, albeit outside of that specific market, let me know.

@mahryekuh In what other way(s) do you think you'd like to enter the accessibility industry? Beyond integrating it into any software you make, which is obviously a critically important thing in itself.

@mahryekuh For what practical purpose, though?

@mahryekuh Huh. I've evaluated the mark-up of thousands of webpages and I don't think I've ever seen this in my life. This attribute on the html tag specifically, that is; I've obviously seen all the other OpenGraph stuff in meta tags and such.

@mahryekuh I wasn't sure what rucola was! I think they call it rocket in the UK.

@mahryekuh Beyond that, despite my thoughts on the other thread, this is a good article on the topic.

@mahryekuh You have a typo:

> Be aware that I will use the words "link" and "anchor" to refer to the HTML <a> attribute, ...

"attribute" should be "element".

I'd also suggest hiding the line numbers in code snipets with `aria-hidden`, because they prevent screen readers from conveying indentation properly. A solution that makes the line numbers more accessible would of course be better, but I don't know of one on the web.

@carlton I don't think they're directly comparable.

Django has a canonical set of official docs to refer back to, as well as the code itself. Many tutorials are written to make those things more approachable, or tie multiple strands together in ways people may not find obvious. The information quite often (though not always) does already exist elsewhere, and that state of affairs provides a nice progression story for people wanting to dive in in more detail.

In accessibility, a lot of the literature out there is reactive rather than proactive. I include WCAG in this, which many people might point to as a canonical work. But in truth, it was written as an attempt to make sense of very messy things and get them down in writing, but the scope is extremely limited (and quickly becomes outdated). And with less content overall, there are less opportunities to cross reference.

That last point might sound like I'm encouraging more writing, rather than less. But there is a huge imbalance between "basic" topics that have been written to death, and more advanced ones that have zero resources (mostly because people get paid to consult on those and don't/can't write anything down).

@mahryekuh

@mahryekuh Also, just to be explicit:

Having worked with you, it's a joy to meet a developer with such a positive accessibility focus, who brings so much willingness to learn to the table. I don't want to discourage knowledge sharing, but people who take too much responsibility on their shoulders provide a constant story of burnout in the accessibility space. @carlton

@mahryekuh I guess I don't agree that your name absolutely must be on something just because you're the one "slapping down" some rules or suggestions. You didn't want to write it, and someone else already did. But I'm not a blogger... shrug.

https://adrianroselli.com/2016/01/links-buttons-submits-and-divs-oh-hell.html

@carlton

@carlton This is one of those accessibility 101 things that's been written about tens of thousands of times. As much as I enjoy Marijke's writing, the accessibility community has a problem if it needs individual developers to keep regurgitating the basics again and again. I see some discoverability parallels with the content in your latest newsletter here... @mahryekuh

@mahryekuh There have been many recent discussions in this house about how utterly underwhelmed I am by pumpkin spice and cinnamon. So I'll pass... but enjoy!

@mahryekuh I feel a bit conceited liking this post, but... Communication and distillation of ideas are hugely important to me, so thank you so much for saying this.

This has to be in the running for most useless email I've ever received:

> Hi, <redacted email address>,
>
> We could not issue a certificate for your domain <redacted subdomain>.<redacted domain>.
>
> If you have any questions, please contact us at [email protected]

That's literally it. No reasoning as to why it failed, whether they'll try again, what I should do about it... WTF?

@mahryekuh Which book?

@mahryekuh You're welcome.