I will admit, playing Super Liam on the MacBook was rather weird for me, seeing that I first played the original under Windows XP. Porting across could not have been that easy. Well bloody done.
| My personal website. | https://bsteenkampwrites.com |
Brandt (ZS6DI
- 62 Followers
- 64 Following
- 504 Posts
Blind, hard of hearing, one-handed hemiplegic and some would say may be a little eccentric. Happily married to the best wife a guy can ever ask for, except, she's not on Mastodon yet. All opinions expressed are, or reflect my own and does not have anything to do with my professional life. I am also a ham radio operator, using call sign ZS6DI.
Quickly doing an update for the HomePod minis I have, not waiting for software to pull it’s thumb out it’s arse.
I have had a look at the mantis Q 40, but it is fundamentally flawed in a very, very specific way. Humanware believe, all blind people use standard QWERTY, or whatever layout for their language. Not true. I, Having rather severe right side hemiparesis, use the left-handed Dvořák keyboard layout. I would believe, there are right hand Dvořák layout users as well out there. I have brought this up with humanware, but no go. It really is not that hard.
@pawpower I don’t even own a watch anymore, although they are great. I like to be as efficient with my devices as I can, my phone or my Mac can both tell me the time. My M4 Air is great, and I need the power, but for most, the Neo would be perfectly fine.
@pawpower Totally fair, as I said, not for me though.
@pawpower I have an Optelec Voyager, 44 Zyl unit, that I run with my MacBook. Old as hell, but those things just don't break. I also have a braille edge 40, for when I need to go somewhere. No offense ment, but no takers are extraordinarily limited in what they can actually do. Why pay $7000, if a MacBook and a display will do it.
@FediTips I used to, about a year or two ago, but not anymore.
@FediTips Accessibility issue I’ve confirmed on both the Mastodon web interface and a third-party client:
Profile link verification is currently conveyed only visually, through a green color change and a checkmark. VoiceOver does not announce whether a link is verified.
This means that as a blind user, I cannot independently confirm whether my own website verification has succeeded. (1/2)
Verification status is meaningful information, and conveying it by color alone appears to violate basic accessibility principles.
Has anyone found a reliable non-visual way to determine whether a profile link is verified, or is this a gap in the current UI? (2/2)
Also, WCAG 2.2 AAA, is almost impossible, if you do not control the markup directly. I aim for WCAG 2.2 AAA for my own website. from what I know, I think I might have succeeded. If anybody wants to have a look, feel free.https://bsteenkampwrites.com