Skip to main content


Hello @Nolan Darilek, thanks for reporting this, I am sure this is very helpful information. I think @Steffen K9 🐰 upgraded #Friendica recently, so maybe this was a problem introduced with the latest update.

I think @Hypolite Petovan might be interested in this or can point us towards someone who can fix this.

Also I think the devs are always happy about insight from people using screen readers, maybe if you're interested in supporting the development in this direction you could get an account on https://squeet.me, which is run by @Michael Vogel and he usually runs the latest development release on that server, which means you'd get changes before a stable release and could report issues for screen readers before the release was done. Which I am sure would be very helpful.
Cool, thanks.

It's interesting that I've essentially seen 3 themes in a short amount of time--last week the one I've used for a long time, briefly last weekend when the headings and ARIA representation agreed, and now. The second to third change seems like a major upgrade, but I thought we were running 23.04 last week. The hotfix didn't make a theme change, did it? Anyway, that's why I'm wondering if a settings change or something on my end may have done it, though I can't correlate a settings change with why the heading level might change.
It's great having a screen reader user on board! This at least means that Friendica is not completely inaccessible.

I had a quick look at the code. We do have "h4" and "h5" in the system but this hadn't been changed literally for years.

I think that we have to work at the headings, since it seems that this is done quite messy. For example it seems as if we aren't starting with "h1" at all. Where do you expect having headings? Only for each starting post or also for each comment? Or should the comment get a lower heading? So for example "h1" for the page header, "h2" for rhe subtitle. Then "h3" per starting point and "h4" per comment?

I also realized that we have got a problem when a post itself contains headings. What should we do then? Making them "h5" and "h6"?

Or should we possibly omit the headings at all and find some other way to make navigation possible?

Do you have got a github account? I would like to have it noted there, since I think that this here will lead to some more and longer work.

Thanks for pointing out the problems!
When you are already active on github, it would be great if you could open accessibility issues.

Concerning content warnings: In the social media settings you find "Enable Content Warning". When you disable this, then content warnings are expanded automatically.
I know. Unfortunately, opening/fixing accessibility issues on open source projects could easily become my full-time job if I let it. I know folks are doing their best in most cases, so often times I try just working with what I have rather than pointing out every way it could be better.

I'll open a few for these, though. I also just found that clicking a profile link in a comment header pops up a dropdown that I can't navigate, which would definitely challenge someone who didn't know they could just search for the link to view the local contact. I'll report those this week sometime.
Yeah, I guess that there is really a lot to do, if you reported each and every accessibility issue. I'm in some dilemma here. On the one side I don't want to spend your time - but on the other side I really want to make the system more accessible. I know that there are people out there that are doing this for a living. But sadly we don't have got any budget. I heard that especially Apple devices are really good for testing this stuff - but I don't have any.

So take your time, report something when you want to. There is no pressure.
OK, figured it out. Firefox nightly keeps doing this thing where it opens my history sidebar on a page and I can't figure out why. It may be visually obvious, but the only way I notice is if I tab into the page from the toolbar and focus lands in the sidebar. Naturally, this isn't how I use the web. 😀 Anyhow, if the history sidebar is open, I think it changes the rendering somehow such that everything gets an h5. Closing the sidebar got everything back to the second, better version of everything where the headings were nice and I could navigate more easily.

Sorry for the noise, but at least the bug fixed itself--the best kind of bug IMO. 😀