I am unable to view or even edit my sent posts in TweeseCake with Blob.cat! I have no idea why. Maybe, it's different enough from Mastodon (the actual network that TweeseCake is meant to work with) that it won't allow me to do it. Sometimes, I honestly have half a mind to just give up all social networking accept Dreamwidth, because it's the only place that is completely accessible. I don't have to beg developers to make things screenreader-friendly, or hope it will work with this client or that website because I can't do x on the main one, or that y feature that worked on one site will be accessible on the next one. It just works. Say what you like about Facebook, but the Basic Mobile site (not app) worked. I hardly had any problem with it. Then, they closed it, and I left because their main site is a nightmare to work with. Now, I'm in the Fediverse, feeling as if I'm using the main Facebook site all over again!

I don't blame the administrators of friendica.world or blob.cat. It's not their fault. They're just working with what they have. Both are wonderful human beings who have been very kind to me. It's not even the fault of the developers of both sites. It makes sense, when you're a small business or a single developer, not to know about things such as accessibility. I just wish more people would learn and/or write things in semantic html or offer some kind of text-only or basic version of their site. I know that Deque University and Geeks4Geeks teach accessibility and teach html with accessibility included, respectively, but I guess other sites and books don't. As for TweeseCake, this is an excellent client for the blind that works well with Friendica and probably even better with Mastodon. But again, it's by a single developer. While changes are coming, people do have lives and other committments, and one person can't be expected to work as quickly as a huge company.

By the way, my Dreamwidth account is here. I must update it slightly, as I have some new entries to post for the month.

dandylover1.dreamwidth.org
#accessibility #Akkoma #blind #Dreamwidth #Facebook #Fediverse #fediverse #Friendica #html #Mastodon #NVDA #ScreenReaders #SemanticHTML #TweeseCake #WCAG #Windows

Yay! I'm on Blob.cat! I am happy to note that almost all of it is accessible, minus one or two minor issues. I have a feeling this is not an instance problem, but an Akkoma problem. Even as a non-programmer, I am also fairly certain that this can be fixed easily. No one needs to rewrite the entire front end, as with Friendica. Basically, in the Profile and Settings, and on the main page, there are some buttons and check boxes that are not labelled properly. The check boxes under Settings, for example, just say "check", without stating if they are checked or unchecked. However, when they are unchecked, there is something labelled simply "button" that appears. There are other buttons for things such as post visibility default, but while they are labelled i.e. "Unlisted", "Public", etc. there is no way to tell which button is checked. In the profile, the Bio section appears blank, even though I filled it out during registration and can read it when I go to my profile without trying to edit it. Finally, on the main page, there are two things labelled simply "button". I think they have something to do with emojis. But that's really it! Everything else is accessible with NVDA, and I love the feature set! I really hope these tiny things can be worked on, because it would make everything truly perfect!

By the way, here is my profile page. I haven't written anything yet, as I was only approved recently.

blob.cat/dandylover1

#accessibility #Akkoma #blind #Blob.Cat #Fediverse #fediverse #Friendica #html #NVDA #ScreenReaders #SemanticHtml #WCAG

*This is a note for those who wish to follow me. First, please read my profile. Secondly, subscribers are those who follow me, but whom I don't follow in return. Friends are those who follow me and whom I follow in return.

People who will never be accepted: Minors. I don't feel comfortable having anyone under eighteen (preferably twenty-one) follow me, even as subscribers.

People who will always be subscribers: Those who constantly write about politics, who always use obscenities, anti-capitalists, anarchists, extreme leftists and rightists), religious fanatics, those who hardly post in English, only post about technology and/or games (not including accessibility), or medical/mental issues.
Note. I'm not talking about having a bad day or posting once about politics. I'm talking about those who barely post anything else.

People who will always be friends: Those who post about high culture (classical music, good literature, art, history, theatre, wine, coffee, tea, snuff, fine dining, etc.), male fashion, nature, pets (especially cats), plants/gardening, good news, writing, and daily life (without constant drama).

I tried to post this to the Friendica support forum, but it kept timing out when I entered my information. I am now attempting to subscribe to their e-mail list. However, I thought I would write this here so that those who know coding, etc. might be able to offer a solution, or at least, to pass this on to the developers.

I joined Friendica in October of 2024, when Facebook decided to shut down their Basic Mobile site (not app). I am totally blind, and their main page is a nightmare to use with a screen readre (NVDA in my case). I chose Friendica because of the huge character limit, the ability to edit and delete posts, local posting, extensive profiles with keywords, and the ability to connect with all sorts of accounts in the Fediverse. For the most part, I am enjoying my time here. However, I am noticing a lot of inaccessibility on the Friendica page. I am not a programmer, but I'm guessing this is at the core of the software and is not due to the instance I'm using (friendica.world). I am also guessing that the page is not written in HTML5 and does not follow WCAG guidelines, though I may be wrong about that. If not, I strongly urge the developers to review them and implement them if possible. If so, perhaps, some changes can still be made that would make this a more screen reader-friendly site. Note that I tried this with Firefox and Supermium (a direct fork of Chrome).

Mostly, I use TweeseCake to access the site, but there are some things I can't do with that client. All of the following refer to the site itself.

1. There is a list of links at the top of the page that acts like a menu. This causes many problems while trying to perform basic tasks, particularly editing posts and handling notifications. I can't always activate said links/menu either.

1A. I can't stress how frustrating editing posts is. It sometimes takes over ten minutes. The "edit" option is a link/menu, and it can only be found via another menu. Once I finally find and activate it, I hear the sound indicating that I have entered focus Mode. Usually, this means that I am in an edit box and can type. However, in this case, I am taken back to the main page, as if I never entered the option to edit my post. Using e to try to find an edit box doesn't help, as it just sends me to the replies to different comments. So I am forced to find the post, and start all over again. The only way I can do this successfully is to try to tab through the links/menu at the top of the page (when it works), then through other posts, until, finally, I am placed in an edit box where I can type.

1B. When I go to the Notifications" link, I have to tab to "Mark all System Notifications as Seen". This isn't even a regular link, as I can't copy and paste the text from it. Once I tab to and out of that, I can then read my notifications. But here is what I have to do if I want to see follow requests.
1. Try to get the notifications link to work, then click on it.
2. Tab to marking notifications.
3. Perform a search for the word follow.
4. Click on the link of the notification that someone wants to follow me. I open this in a new window, to try to keep the original one available.
5. Make my choice as to whether to approve that notification, then close that window.
6. Return to the main window. Only now, I am not where I left off. Instead, I am placed back at the beginning of the page and the Notifications menu is not open.
7. Repeat steps 1 through 3.
Ideally, I should be able to go to a normal notifications link, perform steps 3 through 5, then return back to the link, and perform steps 3 through 5 again, as many times as necessary, without having to repeat 1 through 3.

1. I can't just go to the site and enter an edit box to post. I must go through a menu to find the link to do so. Yet there is an edit box for searching for content, tags, etc.
2. Some pinned posts don't always read properly. I can see my name, when I posted, that it's pinned, a public message, tags (if applicable), buttons for resharing, etc., and the number of comments. But I cannot simply read the post itself. ""Comments" is also a button, not a link. Even when I expand them, I still can't see my post, and finding the button again to close them takes a lot of time, as posts also have their own buttons. Note that unpinned posts are read properly.
3. While the process of editing my profile is completely accessible, finding the edit option might be slightly confusing for new users, as it requires entering yet another link/menu, this time with the user name as the title..
4. If I go to a profile of someone not on Friendica (usually Mastodon) and wish to reply to a post, after I enter my credentials, it takes me back to my profile, not to the relevant post. It only worked once.
5. The Friendica app for Windows is basically the site itself. I don't understand this at all.

If you want to see a truly accessible site, try this link. I don't work for them, though I do have an account there.

dreamwidth.org

Please, if any changes can be made, I urge you to do so. The site is otherwise a pleasure to use, but my frustration at not being able to easily perform such basic tasks is increasing.

#accessibility #blind #coding #Chrome #Developers #Dreamwidth #Facebook #fediverse #Firefox #Friendica #HTML #HTML5 #NVDA #ScreenReaders #TweeseCake #WCAG #Windows

As a grammar prescriptivist, I take writing and proper use of words very seriously. I recently saw a post about ending text messages with full stops. Apparently, some think this is a bad idea. No. It's called using punctuation correctly! Perhaps, they should read a few grammars instead of playing their silly video games! The same is true of netspeak, textspeak, corporate spaek, and abbreviating everything. Likewise, I have no use for political correctness. I refuse to use words such as visually-challenged, vertically-challenged, etc. I will say blind (or visually impaired if the person has some vision), short, fat, etc. Unless I'm writing poetry and am seeking flowery words for things, I call them what they are. Neither do I see any difference between saying "a blind person" and "a person who is blind", for example. I also have no time for so-called gender-neutral words, unless they honestly make sense and are actually descriptive, such as firefighter or police officer. But I'm just as likely to say fireman, policeman, waiter, steward, actor, chairman, etc. and change the gender when necessary. I refuse to use the singular they. There are two sexes (gender is for grammar). You're either one or the other. This absolutely doesn't mean that you can't change your sex. If, for example, I meet you as a woman and you change to a man or are a drag king/queen, I will certainly change my use of pronouns when discussing you or talking about you, either permenantly or temporarily, as the case requires. But unless you literally have multiple personalities or are a machine or an inanimate object, you are neither a they nor an it, and you're certainly not some made-up pronoun such as xe. I would never cause harm to those who use such words. I would just consider them to be silly or confused. If the sex is unknown, or if a sentence can apply to both sexes, I use the masculine, simply because it's grammatically correct to do so.

#English #gender #grammar #language #prescriptivism #properEnglish #sex #texting #writing