Publishers

Those who know HOW to say it and DELIVER with technical know-how.

The approver/publisher determines if the content of their department communications being readied for delivery to the public via the World Wide Web is acceptable. They manage the design, processing and delivery of web-based communication on the website – and are usually a webmaster. The Approver/Publisher has web production and project management expertise, and  is typically an administrator in the CMS, with an extensive knowledge of its use.

Responsibilities:

  • Attend CMS training annually to keep up to date on industry initiatives, including accessibility.
  • Check if content is appropriate for web applications and make sure it’s concise, meaningful and meant for our external site.
  • Check style and presentation—is it easy to read?
  • Check to make sure the wheel is not being re-created; if you know content is present on another part of the site or within an external site, suggest that the content provider establish links.
  • If links are used, make sure they are meaningful; they should not read “click here” or “read more” but instead indicate what information the site visitor is being directed to.
  • Check spelling, grammar and presentation of information, to include placement and proportion of pictures, use of headings and tables, etc.
  • Check links to ensure they are directed properly.
  • Check link language, ensuring “click here” or “read more” is not utilized as link text; if not, notify content provider and provide explanation.
  • Double-check representation of any images or tables. Check that tables are designed and labeled properly with headers; if not, notify content provider and provide explanation.
  • Ensure that PDFs and flip-books are not in use, unless exception has been granted; if not, notify content provider and provide explanation. If replacement of PDFs or flip-books is cost- or time-prohibitive, aid content provider in securing exception request form.
  • Ensure that any videos contain closed captioning or “request transcript” link; if not, notify content provider and provide explanation.
  • Publish or reject based on the above criteria; if rejected, send an email directly to the content provider explaining in detail the reason for sending it back; do not rely on the automated messaging within the CMS.
  • Educate component CMS users regarding accessibility initiatives.

Additionally, when working to design pages or sites:

  • Validate HTML and CSS
  • Design with accessibility in mind; use accessibility web development tools
  • Test your site’s accessibility with page-by-page or enterprise testing
  • Determine key public entry points of respective sites and perform routine accessibility checks
  • Periodically spot check pages within your site for usability and accessibility
  • Check code within workflows for the presence of “skip nav” and to remove extraneous code

Next: Cascade Pre-Workshop Evaluation