Web Coordinator Cascade Page Approval Checklist

As a Web Coordinator, you will be responsible for reviewing and approving all webpages in Cascade for your clients. Please use the checklist below as a guide when reviewing pages. We should be checking and fixing all these elements before approving a page to go live. You can decide if it is a fix that can be done on your end or something you need to push back to the campus partner.

Images & Video

  • Alt text: Make sure all images have proper alt text. Don’t allow “lazy” alt text to occur, Use “Student in red Chapman University sweatshirt giving presentation in front of class” as opposed to “girl” – try to add Chapman relevance to the description for SEO.
  • Text on images: Images should be just photographs and not graphically designed images. Descriptive text is an absolute no on images. Occasionally, the use of a branded event logos can be used for visual consistency, but verify with your supervisor and make sure the text is written on the page somewhere as well.
  • Image size: Make sure all images are cropped for the right size per the widget used. Often times, the image will be stretched or squished if not properly cropped.
  • Image quality: Make sure images are not too low res or not really big, which slows down load time.
  • Avoid stock photos: We want to avoid photos that appear stock and generic and instead use more authentic Chapman photos.
  • Approved videos: If an embedded video is not from an approved Chapman account (Main Youtube/Vimeo), then do not approve on page  until the video has been reviewed and corrected (if needed) by the Digital Media Team. All videos should have closed captions and action information to request a video transcript.

Links

  • Broken links: Make sure all page links are functioning properly.
  • Internal vs. external: make sure individuals are using the correct link method. All chapman.edu links should be internal, except faculty bios.
  • No “Learn More” or “Click Here”: Hyperlink Text should be descriptive to the link destination and not just generic text like “learn More.” Good example: “Student Conduct Policy”
  • Title attribute: This feature is used to help the user understand the action behind the link. make sure it is used if the hyperlinked text is not descriptive enough. Otherwise don’t use or just repeat the hyperlink text.

Text

  • Spelling and grammar: no mistakes
  • Follow the Writing Style Guide. Things to definitely look out for:
    • Phone numbers
    • Degree and graduation year
    • Building and donor name consistency
    • Dates and times
    • Remove unnecessary spacing
    • Remove double space after periods; some on-campus partners have a habit of doing double or triple space
  • Writing for the web. Many clients do not know web writing best practices. Make sure the page is optimized for web. This includes
  • Meta information: Make sure the meta description is being uses.
  • Outdated information: Often times there is outdated event dates or deadlines listed on the pages. These should be flagged.
  • Table: In content, to design table with fixed width in pixel (px), it’s obsolete method and also not responsive to mobile devices’ screens. The result is the request will be denied in approval process for the webpage go live. While we’re waiting for a solid solution to create a table or a list… by widget, this widget should generates a table on front-end for users to input information in same as html table, but on back-end it generates tableless design (div tag, which automatically scales to fit in mobile devices’ screens).
    • Temporary solution is when you create a table, you should change the width into percentage (i.e. 50%, 80%…) in html codes or change it on the small pop up window.

Widgets and Templates

  • Remove unused widgets in Cascade: as part of the cleanup process, please remoe any  unused widgets in Cascade. We often see this with the news/stories/featured widget in the left column.
  • Misused widgets: Make sure clients are using the widgets appropriately. A good example would be people using the buttons. Instead of using multiple widgets for single buttons, they should use one widget with multiple buttons.
  • Template misuse: Make sure client are using the right template for the page content. If they don’t have right column content, don’t use the the three column template.
  • Widget content: Make sure content is appropriately used in the different widgets. An example would be putting in captions text into a title area of a masthead.

Back to Web Team Internal Page