All posts by Sallie Goetsch

July 2016 Handout: Accessibility Resources

The good news about web accessibility is that there are a lot of resources out there for developers who want to build accessible websites. Here are a few of the ones I’ve bookmarked.

These are not the result of a comprehensive search, which I’m sure would turn up many more resources, but rather articles I have come across in my regular WordPress and web development reading.

WordPress Accessibility Handbook

Rian Rietveld’s State of Accessibility Presentation from WordCamp Europe

Elise Roy’s TED Talk: When We Design for Accessibility, We All Benefit

Web Accessibility Basics from Marco Zehe

Free Web Accessibility Course from Udacity Accessibility Support Forum

WordPress > Support > Accessibility

The A11y Project


Tota11y Accessibility Visualization Kit

WAVE Web Accessibility Evaluation Tool

Enter your URL to check the accessibility of your website.

Yoast’s Must-Read Accessibility Posts (A11y and SEO)

Carrie Dils: An Intro to Accessible WordPress Themes

7 Things Every Designer Needs to Know about Accessibility

Article on Medium by Jesse Hausler from Salesforce. Doesn’t want to do the content card thing.

Color Safe WCAG Palette Generator

Presentation by Michael Beil: How do I know if my web project is accessible?

More WordCamp Accessibility Videos

tuts+ Accessibility Learning Guide

How to Make Your Website More Accessible (WPMU DEV)

PageGauge: Quickly Assess Your Website’s Usability

How to Create More Accessible Content

WP Accessibility Plugin

San Francisco WordPress Meetup to Host Joost deValk on July 27th

Beyond SEO: Copywriting for Professionals with Yoast

Wednesday, Jul 27, 2016, 7:00 PM

717 California Street San Francisco, CA

94 WordPress Enthusiasts Attending

SEO has gone from a technical trade to being more marketing focused. Joost & Marieke will talk about how to gain great rankings & satisfied visitors by writing good content. Focusing on SEO copywriting has a major pitfall. We give examples and tips on how to write a post that is both readable as well as SEO-friendly.Presenter: Joost de Valk Joo…

Check out this Meetup →

June 2016: Git Version Control for the Complete N00b

Adam LaBarge from Hyperarts introduced us to Git and GitHub: installing Git on Windows and Mac, cross-platform GUI clients for Git, repositories like GitHub, GitLab, and BitBucket, deploying from Git to WP Engine, and other useful tools for developers.

Notes from Adam’s Git Presentation

Git was invented by Linus Torvalds.

What’s different about Git? It takes snapshots of your data as your file changes. Git manages the version you see when you open the file.

Everything is local: all the changes and history are on your machine, so you can work without a network connection. If a teammate’s repo is destroyed, you’ll still have everything.

Git is an “add-only” program–it ‘s very hard to get it to delete anything.

WordPress updates are a key reason to use Git. You don’t want to overwrite working code.

You only want working code on stage and master.

Git is amazing for managing your team code efforts…though it IS possible to overwrite your co-workers’ code, so you have to do it right.

You will thank yourself for having a Git workflow and sticking to it.


Git is basically a command-line app. There is a terrible default GUI, and some other GUIs, but some things HAVE to be done on the command line.

There are install packages for Linux, Mac, and Windows. Be aware that you need to specify that you’re using Git for Windows when searching for help for Windows machines.


If you don’t want to use the command line, you can use something like SourceTree or GitHub Desktop.

The GitHub app gives you a good introduction, but it has some drawbacks, especially if you’re dealing with a huge number of files.


Repositories are a place to save your code but they also offer additional services.

You can belong to multiple repositories on GitHub, BitBucket, etc. You can scan your code for PHP errors in the process of pushing it to your repository.

Git by itself is just versioning, not user management. For user management you need a Git server, either one you create yourself or a hosted server like GitHub.



Fetch gets code from a remote repo, but without merging it into your local repo.

Branches: there should be at minimum master (production), stage (for the staging server, to test), and whatever working branches you want. When you’ve finished testing, merge locally, then push to repo.

Git does not have a pre-defined workflow, so you have to create one for yourself and your team. Don’t MAKE changes on the stage or master branch. Make them in a branch and merge.

SourceTree will let you know if someone else has made changes that you need to pull down. (A pull notification means there’s something you need to pull down.) Ideally, you won’t have two people working on the same branch at the same time, but let’s face it, it will happen. If you’re both working on the same branch and you get a pull notification, stop what you’re doing, merge your changes, fork the staging branch, pull down the changes. Merge his changes to your branch, and if they work, back to stage.

“If you’re not sure what’s going on, make a fork of what you’re working on.”

You can force push your changes and re-set the repository.

Whether you create a readme file and a .gitignore file on GitHub depends on whether you’ve already got them on your local.


WP Engine Git Deploy only goes one way, so you really want EVERYTHING in your local Git repo. (Or, well, the repo where you’re keeping stuff, which could be on GitHub or wherever.)

SiteGround’s Git Tutorials

It’s easier to use the HTTPS version than the SSH, because with SSH you have to generate keys. Alas, both WP Engine and SiteGround require SSH keys. There seems to be an assumption you’re going to be working from GitHub so you can generate keys there.

If your code is already on a host, you can push the code from your host to GitHub and then pull it to your local install. (Assuming you have SSH access, of course.)


Don’t be scared to delete Git and start again.

Revert is a pain. Switching branches is easier.

If you don’t commit a change, there won’t be any record of it, so if you want it saved for posterity, commit it!

Before you do anything else, “git status” to find out where you are and what’s pending

The head is the last point of the current branch.

If you find a conflict, humans have to intervene: contact your colleague and decide whose version to use. You have to tell Git you resolved the conflict by re-adding the files.

May 2016 Q & A: Content Audits, 301 Redirects, and Dev Tools

Here are some of the things that came up during our general discussion at the May 2016 Meetup.

What Is a Content Audit?

Sallie mentioned being in the middle of a content audit for a very long site, and someone asked what that was. A content audit is when you review every single piece of content in a site and rate it based on such criteria as

  • Is it current?
  • Is it relevant?
  • Is it on-message?
  • Are there any broken links?
  • What type of content is it? (For example, should this be a press release instead of a blog post?)
  • Does it have a featured image?
  • Does it have an SEO-friendly title?
  • Does it have an SEO-friendly meta description?

On a small site, this can be done in a few hours. You want to do a content audit before building a new site, in order to know what to keep, what to get rid of, how many custom post types you need to create, and what new assets the client needs to provide. You’ll also need that list of URLs so you can set up the redirects.

301 Redirects

When you build a new website for a client–especially one that already has a lot of inbound links and a good Google ranking–you need to set up 301 (moved permanently) redirects from the old URLs to the new URLs. You can also use redirects to make sure that everyone uses instead of (or the other way around), or https:// instead of http://

Redirects are normally set up in your .htaccess file, but there are also WordPress plugins like Redirection and Quick Page/Post Redirect.

If the old site has structured its content logically with pages and sub-pages, you can use regular expressions (regex) to map groups of URLS, e.g, everything with the structure should go under

In some cases that won’t be possible (because not everything that’s under /blog/ on the old site belongs under /blog/ on the new site, for instance), so you end up with a very long list of old and new URLs in that content audit spreadsheet.

In that case, you’re faced with translating your spreadsheet into the proper format to put in your .htaccess file, which could get ugly.

Fortunately, there’s a Batch Rewrite Rule Generator provided by Donat Studios. Paste your spreadsheet columns into the box and get 301s or Rewrite Rules.

Fixing Mixed Content

Once you’ve set up your Let’s Encrypt certificate, you’ll want to install the Really Simple SSL plugin to fixed mixed content issues. (Basically it puts a few lines in your wp-config.php file, which you can do yourself if you prefer.)

Browse with HTTPS

Install the HTTPS Everywhere browser extension from the Electronic Frontier Fonudation to ensure that you get the HTTPS version of every website you visit (if one is available). Works on Chrome, Firefox, and Opera.

Local Dev Environment: AMPPS

Ted was having problems with MAMP, so he switched to using AMPPS. It’s like MAMP with Python and Softaculous included. All those Softaculous apps seem like a lot to include in a package you’re only using for WordPress development, but if you work on multiple platforms, it could be happy.

Local Dev Environment: Vagrant

Daniel was also having trouble with MAMP, so he switched to using Vagrant, a tool for deploying local dev environments. Requires some use of the command line.

Workflow Tool: Yeoman

If you’re already a happy user of the command line, you can save yourself time with Yeoman, though you will have to take some time to use it. If you aren’t working with the command line, figuring this out will probably take you longer than doing things the way you normally do.

Database: MariaDB

Daniel has started using MariaDB combined with PHP 7 for faster, better-performing sites. MariaDB works fine with WordPress without a lot of tinkering. Of course, it’s easier to set up in a local environment or on a dedicated server. If you’re on shared hosting and your host doesn’t provide it, you’re out of luck.

So What’s Wrong with GoDaddy’s Managed WordPress Hosting?

On the plus side, GoDaddy’s Managed WordPress Hosting is a lot better for WordPress than their shared hosting, and it’s competitively priced.

On the minus side, it uses an old version of PHP and there’s no way to upgrade it. There have been issues with staging -> production migration. Some of us find that the WordPress admin is amazingly slow and generally under-resourced: simple things like plugin upgrades can time out, never mind BackupBuddy backups.

The few dollars you save versus SiteGround or A2 are probably not worth it. If you need inexpensive WP hosting you can try Tap, which is $5/month for the pro plan.

May 2016: Let’s Encrypt and WordPress Hosting

Update October 2016

Since the time of the meetup, Flywheel has started offering free Simple SSL certificates and WPEngine has added support for Let’s Encrypt.

Let’s Encrypt provides free SSL certificates. This is a fantastic service, especially since Google has used https as a ranking factor since 2014.

Unfortunately, in most cases you have to install the certificates using the command line, and you can only do that if you have root access to your server, which many hosting companies don’t provide.

There’s a list of web hosting providers that support Let’s Encrypt on GitHub, but they define “support” pretty broadly.

Let’s Encrypt for cPanel

If your hosting company uses cPanel, or you use it yourself on a dedicated server, there’s a plugin to automate Let’s Encrypt installation. It costs $30 for a single server and $150 for a hosting company, and from their docs it looks to be what SiteGround is using. Ask your hosting company to install it if they haven’t already.

Let’s Encrypt for Plesk

If, on the other hand, your hosting company (or your dedicated server) uses Plesk, there is a Let’s Encrypt plugin for Plesk on GitHub to create an auto-install/auto-renew tool similar to the one for cPanel. (Thanks Eric for this link.) now provides Let’s Encrypt certificates for all its customers. That’s great for anyone who has a site, but not likely to make much difference for most of the members of this Meetup or their clients.


SiteGround provides easy installation and automatic renewal of Let’s Encrypt, and it’s very easy to use. It’s not, however, compatible with SiteGround’s version of CloudFlare, so you have to deactivate SiteGround’s CloudFlare and go to Cloudflare directly.

Install Let's Encrypt from the Security section of SiteGround's cPanel


Pressjitsu started offering automated Let’s Encrypt certificates in December 2015. Just fill out the request form.

Pressjitsu Let's Encrypt request form


Although you have to manage your own server with Cloudways, they do provide automated Let’s Encrypt installs (see tutorial).

Installing Let's Encrypt at Cloudways


DreamHost has its issues, but they jumped on the Let’s Encrypt bandwagon early. They use their own customized platform rather than cPanel, so they had to develop their own tool, but they went ahead and did it.

Add SSL through DreamHost control panel


It’s not that surprising that Pressable would be planning Let’s Encrypt integration, since Automattic is a sponsor of Let’s Encrypt and a majority stakeholder in Pressable.


I’m happy to report that Let’s Encrypt integration is the pipeline for Pagely, the company hosting this very website, though I don’t know the timeline. They, too, have a custom site management platform rather than using cPanel.

WP Engine

WP Engine is one of the best-loved WordPress hosts, and for a good reason. I dropped in and asked their support staff about plans to incorporate Let’s Encrypt.

WPEngine has no immediate plans to support Let's Encrypt

Because WP Engine uses its own client dashboard platform, rather than cPanel, they would have to write their own software to automate installation of Let’s Encrypt certificates. That’s not to say it couldn’t be done or that they won’t do it, but they’d have to dedicate time to build the tool and it’s not in the immediate pipeline.

A2 Hosting

Since A2 hosting is a sponsor of this meetup, it seemed like a good idea to include them here. They have a tutorial for installing Let’s Encrypt on their semi-managed servers, but what about their shared hosting? (The Turbo option is optimized for WP at a competitive price.) It appears they use cPanel so ought to be able to include the cPanel plugin above. As of February they were “working on it”:

An email this morning from A2’s director of business development confirms that it’s almost ready:

We are in fact in the final staging of testing the cPanel plugin for Let’s Encrypt. We should have it available to our customers within a couple weeks.


Andy Melichar
Director of Business Development


GoDaddy provides tutorials for setting up Let’s Encrypt certificates for their cloud servers and VPS and dedicated servers, but what about their WordPress managed hosting and their shared hosting?


Flywheel has become very popular with WordPress developers, but what about their Let’s Encrypt support? I’m waiting for an answer…


HostGator uses cPanel, so could theoretically install the Let’s Encrypt for cPanel plugin, but so far they haven’t and the support staff doesn’t seem to know much about it.


Despite numerous requests from their customers and the fact that they use cPanel, InMotion had no plans to automate Let’s Encrypt certificates as of May 4th. I recommended the cPanel plugin to them on Twitter and got this response:

Generate a Certificate

If your hosting company lets you enter certificate information for SSL (or will do it for you) you can use the Get HTTPS for Free generator, but it requires some command line work, and you have to renew the certificate yourself. This has been done successfully on Bluehost.