The day was inspired by Joe Devon and has tirelessly been promoted by Joe and Jennison Asuncion — and all thanks to them for their work!

Why Global Accessibility Awareness

The biggest problem facing accessibility practitioners continues to be awareness. When the people responsible for creating content don’t fully (or even partially) comprehend the consequences of their actions, it is almost certain that what they produce will exhibit fundamental accessibility problems. It’s rarely malicious — there are certainly people out there who expressly decide that they are putting other priorities first, but I don’t believe it’s actually out of malice. It’s usually a lack of understanding.

The hope for an event like Global Accessibility Awareness Day is that the impact will be broad enough that it can successfully reach people who don’t already understand the issues — conferences rarely accomplish this, although they help, because those who attend are already involved, in some way, in accessibility issues.

A small change can make a large difference. Something as simple as providing keyboard focus can transform an online purchase from a frustrating and dissatisfying experience to an easy, pleasurable task. (At least, if you like shopping.)

But not everybody knows that.

What can you do to help?

First, talk about the issues. Tweet about them; post about them on Facebook; write a blog post. Get the word out. The more accessibility is talked about the more people will know about it. If you reach just one person who becomes curious and reads a little bit more than you have been successful. Awareness has increased. Cheerio.

Evangelize to your colleagues, if they haven’t bought in. Learn the most common business case arguments, and be ready to defend them. It’s a chronic problem that getting “the right look” commonly outweighs the importance of accessibility on many projects.

If you’re in a position to take part in a Global Accessibility Awareness Day event, please do — I’m not within a thousand miles of one, so I certainly won’t be there, but I’d love to hear about them from somebody who attends!

It’s not just a day

Promoting accessibility awareness needs to be a lifestyle, not just a day. One day of heavy promotion is a great thing — the sheer volume of information greatly increases the likelihood that those who need the information will receive it. But don’t let it go there!

Pulling the world forward to be truly welcoming on all accessibility fronts may be eternal and Herculean, but it isn’t Sisyphean. This is a task we can succeed at, if we keep moving.

Global Accessibility Awareness Day
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

They clearly agreed on one core point: that Google Docs was definitely not ready for users with disabilities. So, the demonstration was more a show of the range of changes which Google has been adding to make their Docs suite accessible.

On the surface, this is great: Google, a major web apps producer, is working very hard at making their products accessible.

But I’ll hope you’ll pardon me if I don’t consider this a reason to party.

What the demonstration really showed me was method of working with accessibility which seemed to amount to reinventing the wheel — doing whatever they wanted to implement a method for their software, then doubling their efforts so that they can use that method and make it accessible.

That Google is working to add essentially their own accessibility API layer between their apps and a screen reader is only mildly disturbing to me. They have the resources to do this, and I do believe, on the basis of the demonstration, that their cloud office suite will eventually be accessible.

What really concerns me is the example they’re setting.

In the CSUN session on Perfect Accessibility, Henny Swan raised a question about providing examples. The specific subject was in respect to organizations with an international reputation in accessibility, not an organization with a generally international reputation for web expertise; but I think that the point applies.

Google, while not particularly known for their accessibility expertise, is well known for pushing the envelope in web development. They build cloud software which can do some very cool things. What it does not do is follow anything apparently similar to standardized methodology — and because of that, as an example, their work is grossly problematic.

I worry that talented developers will look at Google’s methods and see them as a great example — when they may not also have the resources to build an entire accessibility abstraction layer between their ideas and assistive technology.

Now, there are some advantages to Google’s system, as well. Because they are devoting these kinds of resources to accessibility, they’re not only aiming at the possibility of using the Google Docs suite; they’re aiming at a great user experience for users with disabilities.

Nonetheless, a truly accessible interface with Google Docs is still a significant ways in the future. The best experiences currently are either using NVDA with Firefox or Chrome with ChromeVox and JAWS or VoiceOver.

Google and Accessibility. What’s the plan?
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

Comments in square brackets are my own comments while writing. I missed some names or don’t know enough information to identify people in some cases – if you can provide information, that would be helpful.

If you do not want your information personally identified in this document, let me know.

Panel: Kath Moonan, Lisa Herrod, Leonie Watson, Sarah Lewthwaite, Henny Swan

See also Henny’s post on the questions raised for discussion.

Legal:

Leonie: Development of the Equality Act, specifically mentions accessibility of disability services. Section 508 in process; Australia has targeted WCAG AA as achievement guideline. Cases: Budget Airline, Target, Sydney Olympics

Guidelines:

Lisa: Primary audience; can you cherry pick guidelines for your primary audience. Better to get something done than everything?

Education:

Sarah: Discrete skill sets with different pedagogies: hard code and symbolic code (perfectable); about people, and messy realities. Abstract vs. concrete. To what extent must a11y be a research-rich discipline involved with people with disabilities. Is a perfect education possible?

Users:

Kath: Lot of accessibility activity focuses on technical compliance, though starting in 2005 the DRC in UK stated that most issues were outside of WCAG 1 (at that time). Can one claim perfect accessibility without user testing? Should we classify people by impairment: medical model. Usability suggests 6 participants per type of user – how many users does this mean for user testing?

Development:

Henny: Perfect accessibility may not be possible. May not have been involved in scoping or user interface; given wireframes and have to code. If you have a global reputation, what’s your responsibility for your production, given it’s usage as an example? May have to sacrifice one small slice because of other needs. As consultant: when do you allow an exception. Where’s the cutoff? Working with imperfect assistive technology, browsers, technology — can we reach it anyway?

Disability:

Sarah: Can we reach a definition of perfect accessibility? Levels and types of disability vary widely. Medical model of disability vs. social understanding of technological mitigation. Awareness of stigma and cultural bias. Post-structural: other power relations besides economic — family, duties, religion, etc.

John Foliot: Question: We as content producers and developers have a social contract with the consumers of our products. How does that factor into the process. Do they also have a social contract to maintain their tools to access what we create?

Henny: Formula – users should be able to use their assistive technology. If it’s a small edge case, it might be let go – if it has a huge impact, then we need to take responsibility even though it may not be our problem. Creates risk that we perpetuate the problem by supporting low-quality solutions.

Leonie: From a user end, the assistive technology vendors, browser manufacturers, ourselves should all be experts — audience should not have to be. We all have a responsibility, but we may carry more (all three groups) due to the necessary expertise burden.

Jessi: Similar situation with web browsers in general; up to the consumers to stay up to date. If consumers are using too old technology, the user should take some responsibility to update.

Jimmy Chandler: tries to talk to managers/clients by describing usability as a continuum — usable by one person towards usable by all. Want to encourage participants to move as far as possible, and keep moving further. Government Section 508 very black/white — if they can’t achieve standards, sometimes won’t even try. [Note: person next to me nodding; she works with United States government organizations on 508 compliance]

Lisa? Can’t see: Cherry picking guidelines — how do we handle that? Talking about continuum and what impact we have on a project, we can narrow down to specific guidelines for specific stakeholders (content developer, designer, developer, etc.) Large impact on continuum by distributing burden.

Jimmy: Encourages picking small tasks to achieve so progress keeps moving.

Wendy Lawton? electronic document accessibility services: Raises the concept of perfection — no companies pursue it; most pursue “Best practice” Organizations must define best practice and deliver it. Service providers must define their best practices. Best practice is just as cost effective to achieve in most cases as “good enough” If SP won’t provide “Best in Class” they should disclose

Ryan Benson – Problem with statement is that content providers don’t know that (don’t know what best in class is), and user can’t teach a contractor how to do their job. Contractor doesn’t like to be told everything was wrong.

Wendy: Hears this all the time; procurement people (hiring professionals) need to know what to look for when hiring a contractor in order to achieve accessibility. They need to know what quality requires.

Kath: summarize – “Ryan – In real world, contractors don’t have any accessible practices let alone best, why should consultant have to train the contractors under a tight deadline?” Frequently accessibility is a line in the sand and where do we draw that. Is User testing part of best practice?

Steve Faulkner: Implicit social contract between developer, implementors, and implementation of accessibility support within sites. Developers and browsers are on board, but IT vendors are NOT. Need to have purchasers involved in the contract. AT vendors suck millions of dollars out of users, but can’t take time to involve selves in standards definition – NVDA devs are heavily involved, but are the exception

Sally Cain, Royal National Institute of Blind People — Lot of AT being developed for people who don’t want to learn Windows environment, but they aren’t being supported outside. People can’t do their shopping, because the AT vendor of the product hasn’t made changes to provide outside support. AT gives simpler experience, but doesn’t have sufficient support for real-world tasks.

Jim Henna? – Applauds Steve, but dislikes blame games. Came across inaccessible service, AT blamed browser manufacturer; browser blamed AT. It’s not clear enough – (could be because AT not involved in standards? JCD)

Kath: Subject Up to user to update; references Antonia Hyde? — strong points is that if onus goes on user, it can really exclude people with learning disabilities.

Derek – UK association for blind? Association arranged meeting of companies to sit down — nobody actually said anything.

Lainey Feingold: “Cherry Picking” should be called “Priorities” — from a legal perspective, Priorities indicates intent to continue – “picking” doesn’t come across well; more like a final decision. Legal doesn’t look for perfection, though they want it, they look for priorities in line with needs of user base.

Lisa: Is prioritization “perfect” accessibility — doesn’t believe there is such a thing.

Leonie: What happens if you don’t “nail” all of those issues? Is that a risk due to proscriptive legislation with exact definitions of accessibility.

Henny: At what point do you determine that you’ll launch despite some being unable to use it — but if you don’t launch, NOBODY can use it. The line is constantly shifting.

Glenda Sims: Has to deal with this a lot, always describes it as would be willing to stand with them in a court of law to defend their decisions — avoid that punch in the gut. If you’re willing to defend the decision, you can probably go ahead.

Ian Pouncey: Usability testing is a great way to tell whether it’s accessible or not — user testing a measure of access. From an engineering perspective, not very scalable! Not enough testers, too many things to test. Very few tests get tested in any way shape or form.

Henny: One strategy: BBC has had a brain drain; they are focusing on high profile, key products, and putting effort and training into testing those products — documenting everything, and pushing that knowledge back into the organization. Corporate needs to retain these skills and knowledges, eve, if people leave.

Kath: Vodafone — not currently best in class, but trying very hard. Some products will take a year to get out to market. Lots of user research and testing — strategy – trying to bake working with disabled users into their standard usability tests, from all stages — from product creation through end testing.

John Foliot: Disclaimer personal opinion — tag on to Glenda. When he’s doing evaluations, primarily thinks about everything as being task oriented. Perspective is a) can I do the task and b) how painful is it. At what point is it too painful, regardless of being compliant. Petty issues like heading order doesn’t really make a practical difference. Differentiate failure from annoyance.

Lisa: User testing – works as an independent consultant, many different orgs. Small web agencies, non profits, etc. Has been running compliance/technical audits up front, then looking at those results to conclude how to run user testing and evaluations. Every project includes user testing working with people with disabilities among others — seniors, etc. Audit gives developers some work, then user testing refines focus and can greatly improve usability of sites.

Henny: Notes #PerfectAlly tweet streams; couldn’t keep up. Notes should take the steps to file bugs, talk heavily with major vendors — they frequently are open to considered and constructive feedback.

Karl Groves: re Ian Pouncey — disagree that large scale doesn’t scale, requires good Project Management and great planning, but is possible.

Henny: Need to learn from reports and test results, same code across different products should be reusable.

{Unknown}: Consultant — teams have picked base platform which is fundamentally inaccessible — address this issue early rather than piling band-aids. Can be a major problem. What do you do if you’ve inherited fundamental problems?

Kevin Chao: In regards to accessibility in general; various products, services, standards, countries — difference between different national standards makes the issue complicated.

Sarah: Question of international standards is interesting — vast majority of disabled people in very low-income non-Western countries. Are we really talking about a technological elite among people with disabilities? What about mobile-first countries where access to people with disabilities may be very low? Are we exporting expectations about disability which may not be as useful to individuals in these different locales?

Shadi: Specific area is developing countries – this question is big. Lots of research gaps and open questions. Doesn’t think there’s a real export of expectations, but the issues are very diverse and different. Don’t get to talk about accessibility of systems; lucky to have systems. Distance education programs can have very beneficial use [where technology is available]

Leonie: Legacy technology is huge issue. Go back to the supplier of technology to get better accessibility – don’t underestimate the power as purchasers and procurers. Big strides have been made forward in last five years. Amount you can tackle in house can be intimidating but impressive. In house can give you fabulous front and back end products which you may not be able to get from a 3rd party product if that product doesn’t natively meet your needs.

Denis Boudreau: Believes that the very fact this is happening means that panel/environment believes that imperfect accessibility is acceptable. Probably a good thing, we’re moving out of accessibility [elitism]/perfection, which can slow down take up for accessibility. Getting all web sites a little accessible much better than 10 web sites which are perfect — 

Kath – Trying to be perfect can make us pedantic

{unknown} – Lot of research in communication technologies in development/mobile telephony – information science. Doesn’t entirely address accessibility issues, but addresses barriers with simple technology as area of literature to look into.

Linda Dardarian — Law doesn’t require perfection if it creates undue burden.

Should Accessibility be Perfect – session notes
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

So, I’m sitting at CSUN 2012. It’s after the keynote, but before the first sessions of the conference – and some of the very key points of difference between the marketing and accessibility world are making themselves very clear. Most of the conferences I’ve attended in the past were marketing-oriented – and even where the subject of the conversations are similar, the overall impulse behind the issues is radically different.

The simple fact is that marketing is fundamentally business-oriented. It’s about moving your or your client’s business towards what counts as success for that business. Usually, that means greater profit: higher sales, better ROI, lower expenses.

The world of accessibility is oriented towards the success of the individual who uses your business. Instead of focusing on the profitability of business, accessibility pursues optimizing the experience of the user. This approach certainly can and should lead to improved ROI or higher sales — but it’s not how it’s advertised, and it’s not the goal.

The issues and needs may have a lot in common, but having a different core motivation makes for a radical difference in approach.

Great intentions, road to hell paved with

In marketing I have long observed a tendency to compromise the end-user’s experience for the opportunity to increase business opportunities. However great the intentions of a business owner, they can easily be swept away by the perceived opportunity to increase their business.

With a definite lack of available statistics which can reliably expose the real economic impact of users with disabilities on the web, this is a difficult argument. Is it a lack of empathy? Is it partially because the physical environment of a store forces the business owner to directly confront the visitor with disabilities whom they have disenfranchised, an experience which doesn’t exist online?

The disembodied user effect is well known in social media. The willingness to treat people online as objects rather than as people is damaging in many environments, and the arena of disabilities is almost certainly among them.

What can the accessibility world do to make this real for business owners? Improving empathy may be one path. Producing real, concrete statistics demonstrating the impact a lack of accessibility has on a web-based business may give additional working fodder.

But educating businesses may not be the best path. Educating marketers — possibly the class of service most heavily employed by businesses with a web presence — could have a truly inspiring impact. Where do business owners turn first when they’re looking to develop their web presence? Marketing. In the business world, a web site is fundamentally a marketing tool — so perhaps that’s where education and research needs to go.

Bringing the world of marketing to a point where it views a simple accessibility failure like inserting keywords into an alt attribute as a threat to the web site’s users, rather than as an opportunity for search engine optimization could have far-reaching impact.

An aspect of the problem for many web sites has to do with long-term business development. A business may hire an accessibility expert to review their web sites, make suggestions, or re-work their web site, but when they hire a marketing firm for long-term web site development, they can lose their accessibility very quickly if that marketing company doesn’t also have a firm grasp on accessibility.

Marketing is a necessary service for most businesses. Accessibility needs to be understood as an equally necessary partner to any marketing efforts.

We need to have a talk with marketing
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

So, I’m in need of a few people who are skilled developers with strong CSS, JavaScript and/or WordPress/PHP experience. I’ll maintain this list as people I trust to do high-quality customization work with My Calendar (or with other work, potentially).

Mostly, this will be CSS/JavaScript work. There may be occasional needs to PHP customizations, but that will probably be more rare.

If you’re interested in being on this list, please contact me. Provide a couple of work samples where you’ve done CSS/JavaScript work. If possible, an actual instance of customizing My Calendar would be very beneficial.

This isn’t likely to be a flood of work – but what I’m getting is more than what I can do.

Thank you!

Looking for developers for My Calendar customizations
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

As a result, I’m putting together this article to talk a little about how to structure an accessibility review, in all the practical ways — how you address coming up with a quote or estimate, ways to structure your research and site inspection process, and dealing with long-term follow-up.

• Specify the scope of the audit
• Identify “show-stoppers”
• Estimate or quote the project
• Plan your audit process
• Schedule a follow-up

Figuring out scope

Although the ideal is to perform an accessibility review which identifies every problem on a site and specifies solutions, that’s not always practical. In fact, it’s sometimes utterly pointless — it depends on the ultimate goal of the review. The review process for a site which is considering a redesign is radically different than for a set of templates intended for a web site still in development.

Setting goals at the outset is key. Are we looking to identify key areas for improvement? What are the resources available for fixing problems? If an aspect of the site is rife with major problems, is it best to identify every problem within that area, or simply describe the general issues and recommend finding a new solution?

An initial review does not need to identify every problem. One route I’ve frequently used is to specify a multi-stage review process: an initial review, in which I note major issues and provide guidance on fundamental principles of web accessibility, and a follow-up in which I re-check the site and, if desired, provide further guidance and detail for continuing development.

Identifying “show-stoppers”

What’s a “show-stopper”? Essentially, that’s a function of the site which is so completely inaccessible that there is no value to identifying the problems — instead, you should just describe what would constitute a good solution and recommend replacement.

It’s not uncommon for this to arise at the very earliest stages of the review, when discussing scope. If a site is using a CMS or a framework which is fundamentally rendering it inaccessible, you may want to begin by recommending redesign of the site. However, due to the common usage of external resources to provide video, interactive widgets, or social media (to provide a few examples), it may be that there are elements in use which won’t stand out right from the beginning.

Rather than performing a detailed exhumation of a fundamentally broken aspect of the site, it may be in the best interest of all parties to simply flag it for replacement and discuss that possibility with the client.

Why is this section part of the business structure? Because spending hours reviewing replaceable services is a poor use of your time and your client’s money. You should be looking for ways to improve your client’s site without costing them an arm and a leg!

Coming up with a fair estimate

It’s difficult to provide a good estimate on what a large-scale accessibility review is going to require, in terms of hours or dollars. The larger the project, the harder it is to quote. Keep in mind, however, that what you’re quoting is not generally going to be based on the number of documents on the site — rather, it will be based on the number of unique templates, forms, and navigation structures found on the site.

It is entirely possible that the site you’re reviewing will have 12,000 pages, most with images containing improper alt attributes. However, as an accessibility consultant your time is better spent identifying one or two representative examples and explaining how to properly use the alt attribute than it is painstakingly identifying every single inappropriate attribute throughout the site.

For this reason, you should be looking at the site as a process, not as a collection of pages. The ideal process of the site can be described, greatly simplified, in four steps:

1. The visitor arrives at the web site, which can happen at any place in the site.
2. The visitor will attempt to move to another point on the site, which may be another part of the same document
3. The visitor will begin a goal, which may be a purchase, a form submission, or the acquisition of information
4. The visitor will successfully complete that goal, and be notified of the results.

This general outline describes any visitor to a web site — as a consultant, your job is to identify each barrier they may encounter while completing the process. You don’t need to look at every single page of the site in order to see the shape of the problems — if you can’t navigate using a keyboard on one page, you probably won’t be able to on any other page, either!

With this knowledge, it becomes readily apparent that a web site which has 12,000 pages but uses only one navigation structure, one template, and has only a single form will be much more quickly reviewed than a site with 120 pages which uses 5 templates, provides ecommerce, and has different navigation structures depending on what area of the site is being used.

A 100% complete audit must allow for the possibility that each page may exhibit different problems. After all, if you haven’t looked at a page, you have no way of knowing how different it may be from what you’ve already seen. However, in all probability, pages of a site will be at a fairly consistent level of accessibility. The pragmatic approach — mindful to your client’s budget needs — is going to be a selective audit, not a complete audit.

Plan your Accessibility Audit Process

Now, once you’ve done this a few times, you’ll probably have the basic approach down cold. Every web site is different, however, so that isn’t going to completely free you from doing some planning. You still need to decide what your approach will be. Two example starting approaches could be process-based testing or issue-based testing.

If you’re going with a process-based testing procedure, you’ll start by selecting a process – any process. The path to make a purchase; getting to the Privacy link in the footer; sending a contact message. Follow that process all the way through in painstaking detail, isolating the accessibility issues encountered along the way.

With issues-based testing, you’ll instead pick an issue – such as keyboard accessibility. Work your way through the entire site, noting keyboard-relevant issues as you go. Then move on to the next issue and start your hunt over.

It may seem like I’m describing a very pedantic way to thinking about conducting an audit — you know that you will ultimately do both of these in their entirety. However, the reason for having a plan is simple: you need to avoid the trap of the scatter-plot approach. If you don’t have a system, you’re far more likely to end up missing problems – either because you failed to consider keyboard accessibility over here; or because you forgot to check the contact form when you were reviewing contrast. Having a plan and a process will help you avoid these gaffs.

Schedule a Follow-up

It would be nice to believe that when you’ve written and sent your painstakingly thorough accessibility audit to the client you are done with the project. Sadly, we don’t always live in that pleasant fantasy world. (Although, to be honest, in my fantasy world an accessibility audit would consist of nothing more than a smiley sticker and the phrase “Good Job!”)

Unfortunately, no matter how detailed you made your report — the report doesn’t fix the web site. The client’s developers need to do that. Or, as is sometimes the case, the client’s developers will fail to absorb the principles of the document…and while fixing the problems you described, will create new accessibility issues. Or, they’ll implement a fix which shunts the problem somewhere else, rather than resolving it entirely.

This isn’t a guarantee – there are developers working out there who don’t know accessibility, but immediately catch on to the concept once the issues are presented to them. But there are also developers who…don’t.

Planning at least one follow-up review is important. You’ll also need to make yourself available to answer questions from the development team while they work through your suggestions.

The follow-up review should be a quicker task than the initial review. You can spot-check to see how the developers worked with your suggestions. If you like what you see, you can probably be fairly satisfied. If you see problems, you may need to keep going. If you see a lot of problems, you may need to give the client a call before continuing.

In Summary

Performing an accessibility audit requires many skills: an eye for detail, a strong sense for when an accessibility issue requires fixing, and when it requires replacement, and the ability to describe accessibility concepts in language developers can respond to. Join those skills with sound business planning and a personal investment in your clients’ success, and you’re ready to go!

How to structure an accessibility review
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

Is it possible to make a plug-in with accessible output, guaranteed, every time? Is that compatible with a desire to provide flexible software which developers can use for a wide variety of possible needs from a design and functionality perspective?

What I’ve found is that I can unquestionably make a plug-in which is capable of creating accessible content. However, I’ve also discovered that in order to really make a plug-in flexible, it can’t have too rigid of an output: it needs to allow the user to customize the structure and content at a pretty significant level.

As a web site developer, this is certainly something I always want: whenever I find myself using a plug-in which doesn’t have built-in templating for the output, I can be pretty certain that I’ll be making edits to the core plug-in files. The HTML produced is rarely what I really want. My conclusion from this is that if I want to create plug-ins which will be used by sophisticated developers, then they need to be very, very flexible.

The downside to this, of course, is clear: if you can change the output, you can break it. As a result, every one of my plug-ins which creates web site output has equal potential to be accessible or inaccessible: and I can’t guarantee the results. Additionally, the core content of the site can only be as accessible as the theme surrounding it — so even if the plug-in is configured with my defaults, that doesn’t guarantee any particular level of accessibility.

I’ve had to accept that. But it does mean that I’m constantly seeing implementations of my plug-ins which, while well-done in general principle, just don’t meet my ultimate wishes for accessibility.

But I wouldn’t turn back. I’d like very much to be able to enforce accessibility; but realistically, I can’t do it. There are too many factors.

My User’s Guide to My Calendar includes a short section on the principles of Accessibility; hopefully, a few people will gain from that fact. The fact is that accessibility requires education: you can’t force accessibility on somebody by providing accessible software unless you also take total control over the look, feel, and function of that software, and that’s not the way the web works. With education, you can help move people towards making their own decision to support accessibility in how they customize their software; so that’s what I’m hoping for.

So, what does it mean to write an accessible plug-in for WordPress? I can’t control the administrative interface entirely; because the fundamental interface is the WordPress core, and I can’t just evade that. I can’t control the output, in either structure or design; and even if I could control what exists within the parameters of the plug-in’s output, I can’t control what surrounds it.

So an accessible plug-in is just a plug-in which is able to used accessibly; a plug-in which doesn’t actually implement a specific lack of accessibility. Somehow, that’s a little depressing, but you take what you can get.

The overall lesson to take from this is that no plug-in is actually going to give you an accessible web site. But hopefully, it’ll give the possibility of an accessible web site.

Accessible WordPress Plug-ins: what does it mean?
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

These are plug-ins designed primarily for developers, really — although a novice user can probably get something out of them, even so. They aren’t terribly complicated; they’re just designed as plug-ins which are used for developing new web sites.

About My Content Management

The first of the two, My Content Management, is a tool which creates a suite of custom post types intended to fulfill a variety of special content needs which are common to many web sites. Obviously, these can be done using normal pages, as well — or dedicated plug-ins for the specific content, but I like to have the option to use a standard, common interface. Using this plug-in, you can have an FAQ, Testimonials, Staff Members, an artist’s Portfolio, etc. — all using the same interface.

If you normally develop web sites and then train your client’s to maintain the site themselves, it’s a tremendous help to have a standardized interface for all the content they need to add!

The plug-in features highly customizable templates for three different views of each content type; shortcodes to display the content; widgets for lists of content; special custom field support for the content; and custom taxonomies for each content type.

About Content Progress

This is really a simple plug-in, but particularly useful during the early content development stages for any web site. Content Progress adds a flag to the posts list view which allows you to easily pick out which pages have not been completed. For large sites, this can be particularly handy when you need to keep track of what has and hasn’t been taken care of.

There are two automatic labels: marking pages which have no content or which have very little content, since these are common indicators that content still needs to be completed. Since these are obviously not a complete picture of the site, there are also two manual flags, to specifically mark pages as completed or incomplete.

Hopefully, developers and content creators will find these plug-ins useful!

• Download “My Content Management”
• Download “Content Progress”

Two new content development plug-ins for WordPress
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

In point of fact, My Calendar version 1.9 is ready to go. It’s packaged up, ready to be shipped out. (Well, promoted to the subversion repository. Whatever.)

However, I’m not ready to launch it yet — and this is just because I’ve been very short of time recently, and I don’t anticipate this changing soon. I don’t believe that there are any major bugs in the release — I’m sure there are small ones, despite the time I’ve spent on testing, but probably nothing earth-shattering. However, I have to be realistic — I don’t know this for sure. And because of that, I need to delay the full launch. This isn’t because I’m worried about the possibility of problems, particularly. Rather, it’s because on the off-hand chance that there are problems, I simply don’t have the time right now to be able to deal with them responsibly.

That’s a worrying position – if I launch, and there’s a major problem, I may not be able to fix it promptly. No matter how confident I am in the preparation of this version, that’s clearly grounds to delay. Unfortunately, I’ve been delaying for a long time; partially because I keep adding new features, and partially because I’ve been too busy for a while.

So I’m making this available here, now — version 1.9.0 can be downloaded now. I’m launching it here, instead of through the WordPress repository, because I know that many, many fewer people will get a hold of it here. This means fewer potential problems, and it’s much more likely I’ll be able to deal with any problems responsibly.

Since you don’t have easy access to the changelog, like you would at WordPress.org, here are the changes which apply to the new version:

Additions:

• template editing for list, grid, mini, and single event output.
• pop-up box is now draggable.
• date format option for grid mode, week view.
• templating for details link text.
• templating for event URL link text.
• location filtering from shortcode.
• image upload option for events
• day class to calendar date headings and cells
• individual instances of repeating events can be edited
• feature to add multiple occurrences of an event simultaneously. (concept from Dave Heitzman)
• feature to mass edit information for groups of events (concept from Dave Heitzman)
• stored URL for locations (contrib by John Colvin)
• recurring daily events on weekdays only (based on contrib by John Colvin)
• optional templating for all event output formats
• individual event occurrence iCal export
• numerous additional template tags
• Option to use custom location filter fields as data control
• Shortcode to generate list of saved locations
• Network administrators can control whether sub-site calendars contribute only to a central calendar, only to their own calendar, or whether site administrators can make that choice.
• Upgrade notice information in dashboard for future upgrades.
• implementation of WordPress text diff to compare your styles and scripts against my current released versions
• Option to skip a defined number of events in upcoming events lists.

Bug fixes:

• jump box was displaying in week/grid view.
• some potentially repeatable IDs (code validation).
• ‘Administrators see all options’ did not work.
• Fixed timestamps on main calendar objects
• Squashed e_notice errors.
• category limiting did not work without permalinks due to GET variable conflict with WordPress core
• Missing nonce in database upgrade routine
• Mini calendar simultaneously displayed single event view when visited.
• Link generation for details view did not work if calendar link parameterized
• Issue with weekdays only calendar if day of week set to start on Sunday
• Issue with retrieval of user-specific settings
• Issue with accessing styles and javascript if My Calendar installed in non-standard directory.
• Problem in Today’s Events widget when Holiday restrictions are enabled.

Changes:

• replaced all default icons with 24-bit transparent PNGs
• jumpbox output to automatically scope to the oldest dates in the database.
• iCal output to output event for complete current month
• RSS output to prioritize newly added events
• holiday skipping/fifth week customization moved into event manager function
• new ‘close’ icon for pop-up box; added close icon and scripting to mini calendar pop-up
• copy in several places; updated template tags.
• location lists sorted by location label (contrib by John Colvin)
• Eliminated calendar heading option
• default style resets no longer stored in global variables, instead stored as files.
• Map links now trigger the driving directions dialog in Google Maps
• New default stylesheet, refresh.css

My Calendar Version 1.9.0 is almost released
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design

by Brian Bondari and Everett Griffiths

Read more about this book at Packt Publishing » or Buy it at Amazon

At root, this book is an excellent overview of the techniques and issues which will be encountered by any developer — however experienced — when they are authorizing a plug-in using the WordPress plug-in API in WordPress 3. In particular, I appreciated the emphasis on organization and coding best practices. I’ve worked with plenty of plug-ins, and there’s a lot of ugly, unmaintainable code out there. (And I’ve written some of it, too!) The fact that anybody looking to develop a plug-in who uses this book as a major reference will also get a guide to some best practices in writing software is a definite bonus.

The authors are very realistic about the limitations and benefits of the WordPress plug-in system. They observe that WordPress has a great deal of flexibility when it comes to coding style and organization — and the result is that there’s a low resistance to entry. Great for beginners, but it does mean that trusting the code you find is something you shouldn’t do blindly. Clearly the authors want to emphasize that anybody looking to begin developing plug-ins should give some significant thought to the sustainability and quality of their work. Kudos to them!

The book doesn’t cover an enormous number of different API functions, but it does give a good overview of the key hooks that are needed to get started programming for WordPress. Given the scope of what can be done in WordPress, it’s really a better solution to solidly introduce some of the core techniques rather than try and cram a huge number of concepts down the throats of their readers.

I found the systematic approach taken by the book to be extremely effective — I appreciated that the book intentionally had the reader introduce common errors into their plug-ins. Having encountered most of those issues by accident somewhere along the line, it’s tremendously valuable to already have been made aware of some key elements.

I do think that this is a good book, and very worthwhile for the beginning plug-in developer. There are a few additional areas which I would have liked to have seen covered, however.

Although the book is very thorough in addressing programming best practices, it doesn’t address the quality of output code at all. Valid HTML, consistent use of elements, semantics, and accessibility are all issues which deserve a significant mention in the programming of a WordPress extension — however easily the plug-in can be maintained, if it doesn’t produce high-quality output, this can be a major disadvantage for the plug-in. It is very dissatisfying to install a plug-in which does exactly what you need it to, but produces output which can’t easily be styled or doesn’t meet the standards required for your web site.

Nonetheless, there are no other issues which I felt were truly missed — the book is well-written, thorough, and methodical. I can highly recommend it to anybody looking to start authoring WordPress plug-ins.

Note: although this review was not paid, I was provided with a free review copy by Packt publishing in exchange for the review. It was definitely a worthwhile trade!

Book Review: WordPress 3 Plugin Development Essentials
Copyright 2004 – 2011 Joseph C Dolson, Accessible Web Design