Read The struggle is real: Self-serve SEO or pay for page rank? by Laura Legendary (Accessible Insights Blog)

To plagiarize the 80’s pop ditty, everybody wants to rule the world. When it comes to achieving any sort of visibility on Google, there’s not a great deal of room at the top. In fact, d…

A few thoughts of my own.

At the risk of ruffling the feathers of the SEO community, as a blind entrepeneur I’ve found that focusing overly much on the mechanics of search engine optimization detracts from the rest of my business.

Things like Google Analytics, for example, are almost completely inaccessible, and so tracking that kind of data is something I don’t do at this point. I’ve also made a point of not tracking any metrics that prove to be not beneficial, and I’m focusing on creating content that my visitors find useful.

Sometimes, (a lot of the time), that’s shorter posts, curation of resources I use, and (once my writing muscles are up to snuff again), the occasional longer tutorial.

I think that, if you’re concerned about ranking in the search engines, then you will have to be prepared to either spend a lot of money to hire someone to do it for you, (and there are only a handfull of people or businesses I would trust with that task), or you’re going to have to spend a lot of time keeping up with algorythmic changes, along with possibly hiring someone to read and interpret your analytics data.

Things like well-structured content, though, continue to be relevant, even despite the algorythm updates.

Read Block Links, Cards, Clickable Regions, Etc. by Adrian Roselli (Adrian Roselli)

Whether you call them cards, block links, or some other thing, the construct of making an area of content clickable (tappable, Enter-key-able, voice-activatable, etc.) is not new. While hit area size is mostly a usability issue, marketers often want a larger click area around their calls to action (CTAs) to…

Read A Decade of Heading Backwards by steve faulkner

The question why is it OK to have a substantial set of authoritative semantic HTML definitions misdirect developers for so long?
And then there is the question What do we do with


Read Focus On Beaver Builder Accessibility – Is the End Product Accessible? by Claire Brotherton (A Bright Clear Web)

Someone recently asked me about how accessible the Beaver Builder page builder is. Beaver Builder is a very popular page builder for WordPress that lets user

This was written at the end of last year. I’m glad to see the improvements BB has made with regard to accessibility. I’ve given them a lot of criticism in the past and it’s only fair to also highlight when they’ve improved.
Read Accessible unethical technology by LAURA KALBAG (Laura Kalbag)

I’ve written a little section on accessibility for the Ethical Design Handbook. I’m really grateful that Trine Falbe asked me, as well as including a section by Aral talking about Small Technology and our Ethical Design Manifesto from the days.

Read Usability Testing Popular Shopify Themes by Nic Chan

In recent years, there has been a sharp increase in the number of lawsuits filed in response to inaccessible websites. As a developer who works primarily with Shopify, I have seen an increase in questions from merchants related to accessibility, some of them from merchants who were facing lawsuits themselves.
As Shopify is popular with small business owners who can’t afford a custom-built store, I began to wonder about the state of Shopify themes. What sort of options were out there for a merchant looking to purchase an existing theme from the theme store, and what could I safely recommend to merchants so they could have an accessible storefront from the beginning? I decided I would conduct some basic accessibility testing of all the themes on the homepage of the theme store to get an overview of what the theme landscape looked like.

This post doesn’t reflect thorough accessibility testing of any of these themes, but I think it’s a good starting point for anyone who’s using Shopify for their site, and wants to at least start on the right foot.
Read My thoughts on Gutenberg Accessibility by Marco Zehe @marcoinenglish (Marco’s Accessibility Blog)

WordPress and Gutenberg project leaders: You want WordPress to be a platform for everyone? Well, I’d say it is about time to put your money where your mouth is, and start getting serious about that commitment. It is never too late to change a public stance and get positive reactions for it. The doors aren’t closed, and I, for one, would whole-heartedly welcome that change of attitude from your end and not bitch about it when it happens. Your call!

Marco’s being pretty modest in his description of his abilities and what he does for a living, and I’ll save you the time of reading a multi-page biography which would probably border on hagiography (I have a ton of personal and professional respect for Marco) by saying he knows what he’s talking about and should be listened to.

And this is probably as positive as continued critiques are going to get.

There’s so much worth quoting from this post that I had difficulty picking the best excerpt, so I’ll add my thoughts on the other options below, in a slightly different order than they appear in the original post.

… what I see here is a repetitive pattern seen in many other projects, too. Treating accessibility as a bolt-on step at the end of any given cycle never works, will never pay off, and never lead to good inclusive results.

That statement holds true no matter how many slogans or how much positivity you pile on top of it. And I keep bringing up the positivity thing because it’s particularly galling when WordPress leadership preaches inclusion, everyone, and the like, only to have the bits that are inconvenient ignored or dismissed as mere negativity when it comes down to brass tacks.

The fact that a bunch of currently fully able-bodied people have actively decided to not be inclusive from the start means that a lot of decisions requiring a certain amount of both empathy and expertise need to be made at lower levels, and pushed into the product via grass root methods, which are often long and cumbersome and only lead to slow results. These can be very tiring.

This whole situation is crap. The fact that a bunch of us essentially have to stick around because if we don’t the accessibility won’t happen and we have to fight against the laziness of leadership, (and let me be clear here, by leadership I mean the decisionmakers, which doesn’t include most of the people working on Gutenberg, even the designers and developers who carry the title of lead), is demonstration all by itself that accessibility/inclusion isn’t a priority.

I don’t know why other accessibility advocates stick around despite this, I can only speak for myself.

I stick around although with more built-in intermittent breaks out of (1) pure stubbornness and (2) the desire to ensure that people with disabilities are just as able to have an open, independent home on the web just like everyone else and (3) the self-interest I started with.

People with disabilities shouldn’t have to be stuck with Facebook or Twitter, with all their problems, because the benevolent dictator of one of the largest free software projects makes promises, implied or otherwise, about inclusion and “everyone” which he then finds inconvenient to keep.

I once kept a job for two years after the software I needed to do that job became inaccessible because I refused to accept termination and a severence package in lieu of the accessibility issues being resolved. I used that time to hack on WordPress and learn my way around it, and I have benefited greatly from that initial learning and the assistance and friendship or even family of the WordPress community.

If I could manage to keep that job until I could leave on my terms, I will figure out how to stick with WordPress either until things get better or I leave on my terms.

I’m definitely not walking away while that piece paraphrasing my original HeroPress essay is still up on I still stand by a lot of what’s there, especially the bits about the community, but if I go along to get along, or don’t speak up about this stuff when I think it’s warranted, then essentially I provide an easy way for that piece to be used as promotional material or evidence of a claim that is more like an ideal to be striven for as long as the circumstances are just right.

I don’t have any intention of serving as a token.

I realize all of the above probably sounds like I’m being an arrogant jerk, although I don’t intend arrogance at all, and I hope the people who know me and who have interacted with me also realize that.

I’m thankful for the rest of the accessibility advocates in this community especially, and the rest of the accessibility team who work so hard on a daily basis and never complain when surely they could be doing other things with their free time.

And I’m thankful to the accessibility advocates outside the WordPress community who have spoken up on these issues.

Finally, I’m thankful for Marco joining the discussion.

Yes, I’m tired. But if I can manage to keep a job for two years and leave on my own terms and only on my own terms, I can stick around and help everyone who has spoken up and sacrificed their free time win this. We’ll do it eventually.