http://wordpress.tv/2014/11/14/cory-miller-how-simply-clicking-publish-changed-my-life/

This lightning talk was given at WordCamp San Francisco last year. I’m sharing it because I’m pretty sure I’m not the only one who’s a raging perfectionist, and I also know that I’ve had some ideas or even just things to say that I’ve left unexecuted or unsaid because I didn’t think they were good enough, and we all need a reminder not to let that happen. The takeaway from this talk is to not let the perfect be the enemy of the good. We all tend to be the most critical of ourselves, and if we let whatever we’re working on or want to work on not make it to the light of day because it’s not perfect, then we’re missing opportunities to help ourselves and more importantly, to help others.

Just pressing publish, (writing something and getting it out there, shipping a personal or client project, or just reaching out to someone we’ve never talked to before), doesn’t mean we won’t fail. But it also means if we don’t publish, we won’t succeed either. So don’t let “it’s not good enough” determine whether something you’ve created gets out there.

Mika Epstein has a post on why you shouldn’t use copy protection to try to protect your content. This of course applies to websites. I think you should go read the post, but the short version is this: It doesn’t work.

If you look at the post, you’ll see some very easy ways to get around said protection: Developer tools. These are the tools developers will need to bring up if we’re going to help you fix problems with your site, especially when we’re answering questions in the WordPress support forums. By disabling right-clicking, (which is what copy protection relies on), it’s harder for us to open those tools. But it’s not impossible.

One of the other methods used in copy protection is disabling copy/paste capabilities. This breaks things for adaptive technology users in all kinds of ways, basically resulting in “We can’t read your content.” If we can’t read your content, we’re not going to visit your site. And we’re going to tell our friends about it. Who will also avoid your site, tell their friends, you get the picture.

Stealing content is not cool. We all pretty much agree on that, content thieves obviously excluded. But given that the standard methods of copy protection don’t work in the first place, people who create websites have a really good reason not to use it.

Nothing can replace the eyes of a skilled professional when it comes to web accessibility testing. This is because so much of determining a website’s accessibility is subjective enough that an automated tool cannot help you when it comes to making definitive judgments about whether disabled people who visit your site and interact with it can actually use it.

But before I tell you why automated web accessibility testing is bad in more detail, I want to tell you what it’s good at, because despite not being a complete solution, there are some aspects of accessibility testing they excel at.

Piles of Code

A good web accessibility audit involves an in-depth, manual look at all the generated source code that makes up a website. Doing this is the best way to find out if problems exist, where they are, why they’re occurring, and how to fix them once they’re found. Doing everything manually is great if the website I’m working on is small. But once websites started becoming larger, web accessibility professionals needed a way to quickly scan through thousands of lines of generated source code to get a basic idea of where things stood.

This is where automated tools come in. They help by providing a general layout of the accessibility landscape, and they provide a list of things which need further attention in a manual audit. When you’re staring at a page that contains hundreds or thousands of lines of JavaScript, HTML and CSS, (like, for example, the Yahoo homepage or the Facebook homepage), automated tools can be a great help. On large sites, there really is no other way to find all the errors than automating the task. This includes sites that are using a templating system, such as WordPress sites. When conquering these, you’ll need to use an automated tool that crawls the entire site to get the assessment done. When I began working on Utility Pro, running it through an automated tool was the first thing I did in order to find out what I needed to start work on first, and in what priority.

Some errors don’t need human inspection

One of the best examples of errors that an automated tool can save time on is images without alternative text. In cases where there is no alternative text, an automated tool is used to document every occurrence, instead of an auditor manually going through and finding each one. But in cases where images have alternative text, and it’s not meaningful, a manual audit will find these and suggest meaningful text.

An automated tool lays the groundwork for a manual audit

The most appropriate way to use an automated web accessibility tool is not to generate a comprehensive list of pass or fail judgments on the site being tested, but to give an auditor a list of things that need a closer look. A good tool will provide a list of errors with line numbers and snippets of code that’s causing them. This information helps an auditor decide whether the problem really is a problem, so they can then tell the client why it’s a problem and suggest ways to fix it. More importantly, it’s a good way to find patterns of errors, which then helps an auditor determine the best way to help the client integrate accessibility best practices into their workflow.

Automated web accessibility tools can also help find exceptions in an otherwise accessible site. I’ve created sites or added content which contained good markup, but since underlying tools may change what happens to that markup, I’ll run the site through an automated tool and sometimes find errors I hadn’t realized were introduced. So in short, automated tools are great for sanity checks, and make sure that a manual audit doesn’t miss the obvious.

And now, the bad

Most of the bad things that get mentioned about automated web accessibility testing are related to the subjective nature of accessibility. There are also numerous ways to make a site more useable for people with disabilities that an automated tool will never alert you to. Automated tools can offer false positive and false negative results, and they have a lot of trouble with dynamic features, which have become more and more prevalent on the web and are not going away any time soon.

Now for some statistics

While working with WordPress and the Genesis framework, I’ve found that automated tools give me about twenty percent accurate results when it comes to web accessibility best practices. Thirty percent of what the tool finds I can use as guideance for further manual review. That leaves fifty percent that is straight up manual review. That fifty percent includes everything related to forms, and, since automated tools can only test HTML and CSS, also includes JavaScript, AJAX, and any other client-side scripting.

Does this mean you shouldn’t use automated tools?

I don’t mean to suggest by any of the above that you should never use an automated tool. But the thing to keep in mind is that an automated tool is just that, a tool. It can help with productivity, and helps with the accuracy of the final report. They also help with getting started with the basics of accessibility and can help developers and designers begin learning about it. But when using automated tools, in order to get the most milage, you’ll need to be well-trained in accessibility, understand how to read their results, and remember that what that tools tells you is not the final say in determining whether your site is accessible.

One thing that often comes up when performing an accessibility audit of a website, is the lack of the alt attribute when it comes to images. Fortunately, this is something that can be easily fixed, and you can start adding it to your images right now and see an immediate improvement in the accessibility of your site. In this tutorial, I’m going to explain what the alt attribute is, how and why to use it, and how you can do so using WordPress.

What is the alt attribute?

The alt attribute is part of the HTML tag which is used to insert images into web pages. Alt is short for alternative, and it defines text that is displayed as an alternative in case an image doesn’t display correctly in a browser. It also gives search engines and screen readers an idea of what the image contains. For screen reader users, it means the difference between “graphic img1000000000” or something similar and “graphic man holding a football” or other similar descriptive text.

What kinds of images need alt attributes?

You may be thinking that if there’s an image, it needs an alt attribute. However, this is not always the case. For example, if an image is decorative, such as images used solely for creative effect, the alt attribute should be left blank, like this:

In the case of an image that’s used as a bullet, you can use this:
*

Two ways to add an alt attribute in WordPress

If you’re using WordPress, you have two options for adding the alt attribute to your non-decorative images. The first is to manually add it to the tag. If you’re using the text editor, and manually inserting your images, it looks like this:
brief description of your image
If you’re inserting media using WordPress’s built-in media library, this gets a little easier. When adding the details for your image, there is a field that allows you to enter an alt attribute. Adding some meangful text to this field will ensure that your alt attribute is added without much work.

What counts as meangful text and how long should the text be?

The final thing to keep in mind when you’re adding alt attributes to your images is to make sure the text is meangful. For instance, if you have an image of a woman standing at the check-in counter at an airport, instead of labeling that image “woman,” try labeling that image something like “woman standing at airport check-in counter.” Also, keep your descriptions brief. Don’t use any more than fifty characters. If you need to add a longer description, in WordPress you can add this longer description to the caption field. There’s also a caption attribute you can use if you’re adding it by hand.

The alt attribute is an easy way to increase the accessibility of your website and content, and it’s also an easy way to help the search engines and other people get a better idea of what you’re saying with your images. If you’re going to use images as part of your content, (and you should), make sure that everyone can enjoy them. After all, you’ve spent a lot of time either finding those images or creating them yourself. With an alt attribute for each one, you can ensure the widest possible reach for your work.

If you’re using the Genesis Framework and a and a child theme, you may have noticed that there are some credits appearing at the bottom of every page in the footer. You can change these credits so that they appear exactly how you want them to, with the links you want. In this tutorial, I’m going to show you how.

This tutorial uses a customized version of the Centric Pro Theme, but this code snippet will work on any Genesis child theme.

First, the original code

Here is the original code with the original credits from StudioPress:

//* Customize the credits
add_filter( 'genesis_footer_creds_text', 'sp_footer_creds_text' );
function sp_footer_creds_text() {
echo '

';
echo 'Copyright © ';
echo date('Y');
echo ' · My Custom Link · Built on the Genesis Framework';
echo '

';
}

Next, the modified code

And here is that same code with my modifications:

//* Customize the credits
add_filter( 'genesis_footer_creds_text', 'sp_footer_creds_text' );
function sp_footer_creds_text() {
echo '

';
echo 'Copyright © ';
echo date('Y');
echo ' · Customer Servant Consultancy Inc. · Backed by WP Engine, · Built on the Genesis Framework · using a highly customized version of the Centric Pro Theme';
echo '

';
}

What is this doing and how do I change it?

This code is made up of a filter, and a function with some echo statements. A filter is a function that changes another function. Instead of having to rewrite the function you want to change, you can use a filter to change the function by taking a piece out or adding a piece, and it’s one line of code instead of an entire function.

So in this case, we already have a function called genesis_footer_creds_text, and we want to make some changes to that function with our new function, sp_footer_creds_text. The original function lives in the core of the Genesis framework, and changing it this way saves us the time we’d spend finding the original function, copying it to the child theme, and then changing it. We can use sp_footer_creds_text to make only the changes we need while leaving the rest of the genesis_footer_creds_function intact.

As part of the sp_footer_creds_text changes, we have some echo statements. Echo statements are used in PHP to output text to the screen. In our case, they’re being used to output the copyright statement and some links. As you’ll notice in the code samples above, they can take HTML markup.

The first statement echoes, (or outputs) the beginning of the HTML with classes from the CSS so the credits will display properly with their appropriate styling. The second echo statement uses PHP time and date parameters so that the current year is automatically generated, which means we don’t have to change it every year manualy. It also includes the link to the copyright holder, and it can also include text with no link. There’s also some code that generates some punctuation. You can’t just write the punctuation in because PHP uses half the punctuation marks in the English language to do other stuff. So we have to tell PHP that we actually want to output the punctuation to the screen, not interpret it.

A note on copyright

According to U.S. copyright law, (here), the year of first publication also has to be visible in order for copyright to be valid. There is a shortcode you can use that will help with including the first date of publication: [footer_copyright first="201x"] where “x” is the last digit of the year of first publication. Thanks Gary Jones for the tip.

The rest of the echo statements contain links to the Genesis framework, and, in my modification, the link to the child theme I’ve modified. You can add as many of these as you like.

The final echo statement outputs the closing HTML markup so that we don’t end up with open tags and break the display. Finally, we close the function with a curly bracket.

If your child theme already contains a function that customizes the credits, you can remove that function and use this one, or customize the function that’s there. And of course, all of this goes in your theme’s functions.php file, since it controls how something is displayed on your site.

An Alternative Function with Shortcodes

As I mentioned in the copyright note above, there is a shortcode you can use to generate your copyright statement. There are also shortcodes you can use to generate the link back to StudioPress and the Genesis framework, as well as the child theme link. Here’s a function using those example shortcodes.


add_filter('genesis_footer_creds_text', 'custom_footer_creds_text');
function custom_footer_creds_text($creds) {
$creds = '[footer_copyright]' . get_bloginfo('name') . ' • Built on the [footer_genesis_link] powered by [footer_wordpress_link]';
return $creds;
}

In the above function, shortcodes are being used to generate the current year of the copyright statement, the blog name, the Genesis framework link, and the WordPress link. All of these shortcodes have attributes that can be used. For instance, for the [footer_copyright] shortcode, you can use the “first” attribute to specify the first year of publication, like this:

[footer_copyright first="20xx"]
Within the quotes, add the first year of publication, such as 2005.

Customizing the credits at the bottom of your Genesis powered site lets you add a more personal touch, and gives you just a little bit more control. If you have any questions about this tutorial, feel free to leave them in the comments.

The short answer to this question is no, and there are two reasons.

  1. It violates the WordPress trademark
  2. It confuses users

The Trademark

The WordPress Foundation, the organization tasked with protecting the WordPress trademark, has set very specific guidelines about when and where the WordPress trademark can be used. Using WordPress as part of a top-level domain, (for example, WordPressisawesome.com or anything that is not WordPress.example.com), is strictly prohibited. Strictly prohibited as in “under no circumstances.”

It Confuses Users

Users know, (or learn) that they can go to any site with WordPress as part of the domain name to find information and resources that are part of the official WordPress project. If other business use WordPress as part of their domains, this creates confusion for users because the confuse the business with actual WordPress.

What if I Didn’t Know?

If you’re reading this post, or if someone else has made you aware of what’s here through other means, you know that you have to do something with your WordPress domain. You can redirect it to another non-WordPress domain name, but you can’t promote that domain. You have to promote the new one. Ideally, you should turn the WordPress domain over to the foundation, or at the very least, let it expire.

Offering WordPress-based products and services is a wonderful thing. There’s plenty of work to be had, and if your product or service is a good one that helps others and/or benefits the community, it will get noticed. Just ensure that you do right by the trademark.