…a few billion dollars here, a few trillion dollars there, and pretty soon you’re talking about real money.
Please see my article on the business case for a content accessibility strategy..
…a few billion dollars here, a few trillion dollars there, and pretty soon you’re talking about real money.
Please see my article on the business case for a content accessibility strategy..
(This is a ‘refresh’ of a previous blog on Universal Content Design, with some updated information related to content management–and content marketing– best practices).
A Plea For Your Patience
Please bear with me. This blog is about content (management | marketing) , though due to references to education, architecture, etc., I must ask that content-management (marketing) practitioners suspend disbelief for at least a few paragraphs. It should become evident on why the Universal Design for Content is important to you.
Mr. Smith Goes To Kalamazoo
Several years ago, I entered a graduate program in educational technology in which I chose special education as my minor. Due to my background in publishing and Web consulting, I became enchanted (obsessed) with server-side solutions for the delivery of learning materials in accessible formats. For me, a key requirement was that the assistive devices should place a minimal cost-burden on the end user. I later termed this criterion, “The Best Buy Test”.
Discovering Universal Design
Early on, I learned about the principles of universal design (rooted in architecture) for planning physical environments. The key premise of universal design is that products, environments, (‘stuff’ in general) should be designed in a manner that benefits all users. There are numerous occurrences of design that accommodates users with disabilities, but are commonly used by the general populations. An example is the curb-cut in a sidewalk. This was conceived to provide access to wheelchair users, but is also beneficial to bicyclists and parents pushing stroller and many other users.
UDL
I had just started pondering the universal design framework for delivery of content when I became acquainted with the Center for Applied Special Technology (CAST), a Boston-area research organization that had developed an educational framework known as the Universal Design for Learning (UDL).
CAST’s neurological research has shown that learning occurs in three primary networks in the brain:
Furthermore, CAST saw that traditional educational practices placed a heavy burden on the learners to adapt to the content.
Thus, in the spirit of the universal design, CAST developed the Universal Design for Learning framework. CAST’s findings were that in order for content to benefit the greatest number of learners, then learning materials should adhere to three primary principles :
That’s Nice But Why Are You Telling Me This?
If these learning principles above don’t immediately seem relevant to your organization, then swap the word “learners” with a term (employees, constituents, customers…) that is more appropriate to your context.
Now. you have the beginning of a universally designed content strategy. Is your content universally designed?
Is your content available in multiple formats?
Are there multiple means by which your users can act on the content?
Are you engaging your customers?
Going Forward
If you can honestly say that your content strategy includes “the multiple means” (of representation, expression and engagement) then congratulations, go have a long lunch and enjoy the waning moments of this summer weather!
When you return from this glorious lunch, then get to thee to a whiteboard and think about how you can reach more users and how you can do so more effectively:
If your content strategy does not include “the multiple means,” then you also need to post up in front of a white board, digital collaborative space, etc. and start thinking about the goals for your organization’s (or clients’) content.
Please see my SharePoint article on The Content Wrangler site.
About two weeks ago, I joined a project that is already fairly close to its go-live date. When I start a project at a client’s office, I ask these questions:
It turns out that, yes, their thing was being backed up. Their particular thing is a forthcoming re-lease of their public Web site. Good thing, too; let’s just say I have a history.
I remember what happened on previous projects when I didn’t ask all those questions. Like the time I located the coffee, but found myself lost in an unfamiliar building, seemingly miles from a bathroom.
Or the time I deleted a client’s SharePoint portal (forever) within 1/2 hour of joining the project.
About a year ago, I learned something intriguing about SharePoint. You can delete a site collection from WITHIN that site collection. I know this, because I accidentally did this upon starting the project.
My client had asked about a styling problem. He asked that I not touch the current style sheet because people were going to be reviewing the site that day. So to work beneath their radar, I created a sub site–three levels down in the hieararchy–to do some testing.
I soon learned that the problem was actually with a mal-formed custom layout template and took the following steps:
Actually……I deleted the top-level site–the site collection–and subsequently EVERYTHING that lay beneath. Buh-Bye, sub-sites, document libraries, calendars…..
I asked my client who was taking care of the SharePoint backups and was given some phone numbers of DBAs and system administrators. The answers to my question about backups were reminiscent of that recurring Family Circus theme when the parents asked “Who did this?” and received one of these answers from the children:
No backup. All the content that had been there at 8:00 am that day was gone by 8:25. My fingerprints were all over the mouse button that clicked the “OK” button in the dialogue box to authorize the deletion.
My colleague, who had been with the project for a few weeks, was able to recreate the few changes he had made to the cascading style sheet and layout templates fairly quickly. A bigger problem was ressurecting the SharePoint libraries and lists.
My client recognized that it wasn’t my fault that the sites were not being backed up. Still, I felt like a dolt, not just because I whacked the site collection (could happen to anybody) but because I didn’t ask about backups. Bad business analyst! BAD!
I’ve since taken the won’t-get-fooled again approach. In subsequent projects, I recognized that I need to enquire about backups BEFORE touching the site (and after ensuring continuity of caffeination).