I’ve been forcibly upgraded to iOS 13.2. Yes, it finally happened.
I was just pleasantly surprised by the fact that VoiceOver audio is no longer send to a paired bluetooth speaker. I forgot that was a new feature of iOS 12.
I was not so pleasantly surprised by VoiceOver repeating “space space” at its loudest volume even though its volume isn’t set there.
Thankfully it didn’t wake the sweety up. He’s out like a light.
The first complete Siddur (prayerbook) I ever used was the 1949 edition of Hasiddur Hashalem, translated by Philip Birnbaum and published by the Hebrew Publishing Company.
I still love that prayerbook, despite its stilted English.
Since the Hebrew Publishing Company basically hasn’t existed since 2016, all of their works have entered the public domain through a combination of a lot of the works being published before 1975 and several more of the works having reached 75 years since the death of their authors, which automatically puts them in the public domain.
One of the things I always wondered about is why Birnbaum spends a significant portion of the introduction to HaSiddur HaShalem essentially trashing the work of every translator who came before him.
Why would you spend something like 5 or 10 dense pages basically subtweeting every other translator?
Since all these works have entered the public domain, now I know why.
Apparently this is a thing they all did up to a certain point. There are limits, (for example, everybody’s wives and kids are off limits, and nobody’s Jewish status is questioned), but other than that, everything’s fair game, personal or professional.
It is, (or was) apparently a long-standing tradition which seems to have been set aside for the most part after the Holocaust and then is completely gone by the 70’s.
And it apparently started around the first time the prayerbook was translated and edited in America.
Brittish translations, on the other hand, are on the surface more polite, however the insults are basically “bless your heart” to the Americans and a lot more backhanded to their fellows in Britain, specifically England.
The Scottish make the Americans look like they’re having milk and cookies together.
All of this is fascinating to me.
I missed this earlier in the year, but apparently the NFB is partnering with Be My Eyes as self-described blindness experts.
Sorry NFB but if you’re declaring yourself an expert, you’re not an expert.
Why do I have a feeling this is going to be just as useful as WordPress experts?
I can see it now. All the disability related posts featuring hard-core federationists in the comments sections are going to come with tons of “as a blindness expert” in the comments aren’t they?
That’s all we need. Thought leaders ultiplying at gremlin-like rates.
Points to the first person who comes up with a stealable designation for these ever-multiplying thought leader gremlins, extra if the word gremlin is involved.
I’m writing this because the trend of blind people using Facebook Live is unfortunately spreading.
So, friendly reminder to blind people who are using Facebook Live that it still doesn’t support captions or transcripts and we don’t know when or if it evere will.
I get wanting to do video, and I’m not saying you shouldn’t.
But if you care about accessibility, then you shouldn’t be using a platform that makes it pretty much impossible to not actively discriminate against an entire class of people, in this case deaf and hearing impaired people.
We can sit here and talk about positive impact and other buzzwords all day long. But you can’t good intention or positive impact your way out of this as long as you’re using Facebook Live.
We can sit here and say “don’t do dos and don’ts because it hurts feelings” all day long. But there are somethings that really are as simple as “do” and “don’t” when it comes to accessibility, and prioritizing convenience over one of the most critical and impactful aspects of accessibility by choosing to use a platform that explicitly doesn’t support captions or transcripts is one of those things.
So, if you really do care about accessibility, such that all the hell-raising about inaccessible apps and websites really is more than just looking out for your own interests, don’t use Facebook Live.
Today I learned that Bridgy Publish will pass alternative text attached to photos when syndicating to Twitter.
I’m using Micro.blog’s crossposting feature but I want to play with photos more and the fact that it passes alt text through to Twitter is a really good reason to switch back.
I love learning about accessibility improvements to web-related things I love.
Especially indieweb things.
I got breakfast from Dunkin Doughnuts for myself and the sweety this morning.
Mmmm Munchkins. I haven’t had these since forever.
Not gonna do this every day by any means because it would get too expensive, but it’s definitely a very nice treat.
OK, post properties do not carry over.
I need to think about how I want to resolve this. It’ll take some code.
I think the links themselves would carry over, but then we’re back to the problem of contrast issues for low-vision people viewing from the Facebook app, and there’s at least one of those who likes this page.
Photos I believe I’ve figured out. I’ll either need to attach a featured image using the standard featured image box, or add them directly to the content.
Checkins should be OK because location and weather data get attached automatically to the content, so there will be something, even if it’s just a weather status.
I’ll need to figure out how I want to work around book posts and other similara content.
I just accidentally closed my browser and lost a ton of work. How’s your Friday going?
This post is a test of how post kinds will display when sharing to Facebook.
I’m biting the bullet and letting WordPress.com manage syndication to Facebook since I really don’t want to rangle Facebook and Facebook seems to be giving Micro.blog a hard time by (seemingly randomly) discontinuing publishing to Facebook pages.
Specifically, I want to see if I can publish without manually adding a custom message and still have the contents of titleless posts post in their entirety to Facebook.
There’s a bit of an issue for low-vision users of the Facebook app on iOS at least when you post just the title of a post and the link without an accompanying message.
I seriously doubt Facebook is going to do anything about this, since they pretty much don’t listen to their accessibility team unless someone somewhere in management decides it’s time to throw them their occasional bone, so I’m trying to mitigate it from my end.
I of course have zero control over the styling of the app, and I can’t pass those kinds of changes through from my websites.
Apologies in advance to those who are following me on Facebook while I test this.