WF Contribute Role and Key Configuration

 

 

WF Contribute Roles and Keys

Role	Folders They May Edit	Home Page	New Page Restrictions	Editing Restrictions	Mac SMB Key	Windows Key
WF Admin	Any	/index.html	none		WF Admin Mac	WF Admin WIn
WF Frontpage	/frontpage	/frontpage/index.html	none		WF Frontpage Mac	WF Frontpage Win
WF Dreamweaver	/dreamweaver	/dreamweaver/index.html	none		WF Dreamweaver Mac	WF Dreamweaver Win
WF Coordinator	Any	/index.html	only use dreamweaver template		WF Coordinator Mac	WF Coordinator Win
WF Copy Editor	Any	/index.html	can't create new pages	don't allow use of external editors	WF Copy Editor Mac	WF Copy Editor Win
WF Multi Folder Author	Any, (restricted by file system permissions)	/index.html	none		WF Multi Folder Author	WF Multi Folder Author Win

 

Editing restrictions are the same for all roles with the exceptions noted in editing restrictions column above. These are:

• protect scripts and forms
• allow users to edit page in external application
• require alt tags for images
• use <strong> and <em> instead of <b> and <i>
• allow users to apply styles
• don't allow users to apply fonts and sizes
• allow users to apply bod italic, underline, strikethrough, and fixed width styles

Restricting the user to the use of a certain set of templates and taking away the font tagonly helps so much in making accessibile web pages. Consider the following other steps:

• User training. A good article to give to users is Accessibility and Macromedia Contribute for content contributors.
• Using othe tools to clean up Office Documents. Importing Office documents with Contribute doesn't give you the most accessible web page either, especially when tables and images are involved. Try using a converter such as The Accessible Web Publishing Wizard for Microsoft Office at http://cita.rehab.uiuc.edu/software/office/index.html. Available free to UIUC via CITES Webstore.
• Creating Dreamweaver Assets and Library items for commonly used items that need more developer control to make them accessible.