Re: Training topics: Suggestion for CMS/"Writing Accessible Web Content" example

Hi Alan & Suzette,

Thanks for the suggestions [1] and additional thoughts [2]. Maybe we can 
discuss further in the WAI-AGE TF next week or in EOWG.

Andrew
[1] http://lists.w3.org/Archives/Public/public-wai-age/2010JanMar/0012.html
[2] http://lists.w3.org/Archives/Public/public-wai-age/2010JanMar/0014.html

Suzette Keith wrote:
> Hi,
> This example taking into account authors/journalists using CMS systems is very useful. 
> In our case here at Middlesex University - we have recently moved to a  new CMS system which has been created with accessibility in mind, but our development team are concerned that our many hundred authors/academics and admin staff  will not take on board the accessibility issues. I am guessing this scenario would apply to many large businesses where multiple authors are encouraged to look after their own section.
> Our development team need to offer a short course (half day/whole day) that would give guidance on our in-house requirements, including delivering the accessibility element as though it was just a part of good overall practice.
> This would share most of the characteristics of Alan's proposal except our training could start from a position of knowing the functionality of our CMS system, pre-defined templates and in-house requirements.
> Regards
> Suzette
> 
> -----Original Message-----
> From: public-wai-age-request@w3.org [mailto:public-wai-age-request@w3.org] On Behalf Of Alan Chuter
> Sent: 17 February 2010 16:46
> To: WAI-AGE Taskforce; WAI-EO
> Subject: Training topics: Suggestion for CMS/"Writing Accessible Web Content" example
> 
> I think that this is a very important subject as so much of the content 
> on the Web is created using a Content Management System of some kind. 
> The design of the CMS can force people to create inaccessible content or 
> can do the opposite. Here's a first pass at it:
> 
> 
> =Goal=
> To enable authors to create accessible text effectively using their 
> specific CMS and to understand the issues common to all such systems.
> 
> =Audience=
> Content authors whose main background is in journalism. Assume 
> familiarity with word processors but no prior knowledge of HTML or 
> accessibility (other than that of the general public). Assume some 
> knowledge of the specific CMS they use.
> 
> =Description=
> This topic will introduce different types of content (text, images, etc) 
> and how documents are structured in relation to how this is done in a 
> word processor. it should cover general aspects of Web accessibility but 
> should also be tailored to the specific CMS used by the audience.
> 
> =What the audience will learn=
> * How a CMS differs from word processors.
> * The role of templates and authoring components.
> * How electronic media is different from print.
> * An overview of accessibility.
> * How a CMS can help or hinder accessible authoring.
> * Knowing how the template affects the accessibility of your copy.
> * Encouraging developers to create accessible templates.
> * Comparison of WISYWIG and source code editing.
> * The restrictions imposed by your CMS. How to complain or find 
> alternatives or plugins to overcome limitations.
> * How to compare the accessibility features of different CMS systems. ATAG.
> 
> =Notes for speaker=
> 
> * Must know in advance what CMS the audience works with and its 
> accessibility features.
> 
> =Key points=
> 
> * Thh roles of template developer and content author.
> * The role of the template.
> * How electronic media is different from print.
> * An overview of accessibility.
> * How a CMS can help or hinder accessible authoring
> * Comparison of WISYWIG and source code editing
> * How to compare the accessibility features of different CMS systems. ATAG.
> 
> =Optional demonstrations=
> 
> * Adding alternative text to an image
> * Creating section headers, lists, blockquotes
> 
> =Questions to engage the audience=
> 
> * How do you prepare your copy? In a word processor or directly in the 
> CMS edit control?
> 
> =Handouts=
> 
> * Accessibility dataheet for the specific CMS used by audience.
> * VPAT for the CMS.
> 
> 
> 
> 
>

Received on Thursday, 18 February 2010 11:13:03 UTC