note
· · to read

I’m pleasantly surprised to find that Vimeo now has a much more accessible player. I plan to check out #PostPublish after I’m done with my next meeting. I will announce if it’s captioned. If you’re not already a PostStatus member you should be. Best WordPress newsletter around.

note
· · to read

Friendly public service announcement to all corporations: Sponsorship of the #NFB19 convention is not a shortcut to the accessibility of your websites or apps. That sponsorship money would be much better spent on doing the actual work of making your websites and apps accessible to everyone.

read

· · to read
Facebook's Image Outage Reminds Us How Bad Social Media Accessibility Really Is by Kalev Leetaru
Facebook’s brief image outage earlier this week exposed the general public to just how bad accessibility really is in our modern visual-first social Web. While governments and the technology community are investing heavily in AI bias, they care little about accessibility bias.

I don’t use Facebook very much these days, so I heard about the media outage from the outside. And yes, while there have been improvements, and while I’m not placing blame on Facebook’s accessibility team, the accessibility isn’t great even when the AI so-called alt text functionality is working. The best alt text is text which exposes the context of the image being described, and this is down to content creators. This incident is a prime example of why accessibility advocates and consumer organizations should not be using Facebook as their primary distribution platform. If you must use something like Facebook, then you have a responsibility to make the content you host there as accessible as you can by learning how to add alternative text to your images and, (if you’re using Facebook Live), to transcribe that content and host those transcriptions somewhere else until you can make arrangements to use either a different third-party platform or your own platform, otherwise known as your own website.

reply

· · to read
A post from Greg McVerry by Greg McVerryGreg McVerry (quickthoughts.jgregorymcverry.com)
@cswordpress Wow, thanks for pointing this out! Was commenting at #IndieWeb organizing meeting that we have a strong #a11y presence, especially among people who use screen readers. Would love to learn more about your voice and journey. Maybe make a section here: https://indieweb.org/accessibility?

I agree that there is a strong accessibility presence within the Indieweb community. The focus on semantic HTML is the catalyst for this in my opinion. The backbone of accessibility is semantic HTML, which at its heart means using HTML elements as they were intended to be used. Thanks for making me aware of the accessibility page on the Indieweb wiki. Adding some information there could be useful to others. I’m getting back into the swing of writing things on my own sites again, and I still have several Indieweb tutorials to finish. Tiny steps.

read

· · to read
I Am Cookie Dough by Allie Nimmons
I was always told I had to go to college. I was “gifted” so learning came easy and I enjoyed it.  From ages 6 to 18, I went to competitive accelerated schools designed to churn out college students. It was a narrow path I’d been set on, without encouragement to explore beyond.

These posts are often times the highlight of my week.

read

· · to read
Inaccessibility of CAPTCHA
Various approaches have been employed over many years to distinguish human users of web sites from robots. The traditional CAPTCHA approach asking users to identify obscured text in an image remains common, but other approaches have emerged. All interactive approaches require users to perform a task believed to be relatively easy for humans but difficult for robots. Unfortunately the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users. Research findings also indicate that many popular CAPTCHA techniques are no longer particularly effective or secure, further complicating the challenge of providing services secured from robotic intrusion yet accessible to people with disabilities. This document examines a number of approaches that allow systems to test for human users and the extent to which these approaches adequately accommodate people with disabilities, including recent noninteractive and tokenized approaches.
read

· · to read
How accessibility trees inform assistive tech by Hidde de Vries
The web was designed with built-in features to make accessibility possible; these have been part of the platform pretty much from the beginning. In recent times, inspectable accessibility trees have made it easier to see how things work in practice. In this post we’ll look at how “good” client-side code (HTML, CSS and JavaScript) improves the experience of users of assistive technologies, and how we can use accessibility trees to help verify our work on the user experience.
read

· · to read
Understanding SC 3.2.1 on Focus by Raghavendra Satish Peri
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) The intent of this success criterion is to make sure that any unwanted actions are not initiated when focus moves on to an element. For example during tab navigation or shift tab navigation if user focus moves on to a link & a modal is triggered this fails this check point. Here user did not initiate this action; it was initiated when user focus moved on to a particular element.
read

· · to read
Inclusive Content Strategy: How to Ensure Your Content is Accessible to Everyone by Deborah Edwards-Onoro
At the February 2019 Accessibility Talks online meetup, AmyJune Hineline, Drupal and WordPress Community Ambassador at Kanopi Studios, spoke about inclusive content strategy, what it means, and how to craft content that is accessible to everyone.
read

· · to read
The Anatomy of Accessible Forms: The Problem with Placeholders by Deque Systems
Instructions help users to submit forms successfully. However, if the instructions are provided with a placeholder attribute, then the user might not be able to use that instruction effectively.

Yet another example of the need for HTML elements and attributes to be used as intended by the specification.

note
· · to read

I think I’ve figured out a solution to my Twitter difficulties, specifically trying to manage two accounts. I have EasyChirp open in the browser for my personal account, and Open Tween open on the desktop for my work account. I suppose I could just use a private window in the browser as well for the other account, but as far as I can tell, you can’t respond to direct messages using EasyChirp, so I need a way to respond to those along with viewing two accounts at the same time. I have no idea what I’m going to do about managing the other accounts I have access to/manage. Open Tween will handle multiple accounts, but I’m still trying to figure out how you tell which one you’re sending from. Standard tweets are still easier from my websites. I already have the tabs open and it’s just easier to send from there. No character limit, plus all the other Indieweb advantages, while reading/retweeting from Open Tween/EasyChirp. Yeah, this is really complicated and hacky, but I think it’ll work.

note
· · to read

I’m not one to throw around the “not-a-real-accessibility-advocate” label, but if someone exhibits a pattern of excuse-making for inaccessibility on behalf of themselves or others or both, they need to hand in their A card. Same if that extends to encouraging fellow people with disabilities to accept excuse-making for inaccessibility. If you do all three then you probably need to be taken to the proverbial woodshed because excuse-making for inaccessibility is never, ever acceptable. Either you believe it’s OK to discriminate or you don’t. It’s that simple. Signed: Someone who was once rightfully taken to the woodshed.

note
· · to read

Oh cool. I logged into micro.blog on my laptop, (which I haven’t done in a long time), and there’s a discussion of markdown versus HTML going on and it’s civil as usual. I’m team HTML because I find it much simpler than Markdown. In other news, I’ve started using My Fitness Pal again because it syncs with my Apple Watch and, (for that ecosystem), it’s the most accessible food tracker I’ve found. I started tracking my food again on Monday and I’ve made some slight changes to my diet, but I’m not expecting any losses this week. Because of the goal I’ve set for myself, I have a calorie allowance of 1870, which is amazingly hard to spread out over a day while I’m still collecting things like dishes and cooking gear. I’ll be happy if I don’t gain anything, but I don’t suppose I’m going to be too disappointed if I do. I’m still gettiing back into the habbit of keeping track of what I’m eating and drinking, so I suppose I’m cutting myself a little slack on making changes. The book challenge is going forward, although I need to spend some time with Goodreads logging the ones I’ve finished since I last logged one. I’ve finished the Prey Series, but it’s not all logged yet, and I’ve started rereading the Scott Harvath series by Brad Thor to introduce John to that series. I have some Audible credits to spend, so I picked up the next book in the Kill Chain series by William Hertling, Kill Switch. It’s the sequel to Kill Process, which I thoroughly enjoyed. I think this is enough for now, more next time.

291 Easterly Pkwy, State College, PA 16801

79 °F Mostly Cloudy

note
· · to read

Current status: Looking around the Podtrac dashboard to see if I can delete my address and phone number, which it required for registration and autopopulated, correctly, without asking my permission. I am very much not amused right now. There are zero, absolutely zero reasons why podcast statistics should require anybody’s personal details like that. If those details are sought, then permission should be explicitly asked. If those details are going to be autopopulated then explicit mention of where they’re being pulled from should also be made, and permission to autopopulate should also be asked for. This kind of shit is why people hate big tech so much.

note
· · to read

I just spent over an hour fighting with an admin consul with a pretty much inaccessible UI and a metric fuckton of settings. I really don’t care at this point why things on the web end up inaccessible or how it happens. If you put things on the web that are inaccessible you can go fuck yourself and you can do it until your shit is accessible. If you are a person with disabilities urging dipplomatic restraint in accessibility negotiations you can go fuck yourself too. I am tired of this shit. All I want to do is get my work done without a ton of shit, without having to fight with screen readers and browsers and switch back and forth between the best combinations and I am tired of negotiating and educating. I want to live my fucking life why is this so Goddamn much to ask? Fuck!

note
· · to read

Dear creatives with disabilities, including musicians. So-called exposure by way of contest, competition and, (in a lot of cases), volunteer work is bullshit. Don’t run after it. Your time and talents are just as valuable as those of your abled counterparts, and any person or organization trying to trick you with promises of exposure or large impact in exchange for free work is a vulture worthy of your contempt. Your time and talents do not become less valuable just because you may be unemployed now or because you’ve been unemployed for a long time. Dear people and organizations: People with disabilities are not a source of free labor.

note
· · to read

Shoutout to all the automatticians currently slogging through the VIP Go outage, from the people on the front lines dealing with customers to the people behind the scenes in the proverbial basement who are usually never noticed until something goes wrong. Support and server maintenance are often thankless jobs, but without people like you this stuff doesn’t run. I don’t work with y’all, and I’m not a customer, but I see no reason why we can’t support each other from afar.