Authoring Standards

1
Authoring Standards

• Spring 2006
• Publication Cycle Updates

2
Agenda

• Intranet changes
• Acrobat 7
• Technical requirements
• CHP spacing
• Audio/video notation
• Inaccessible content notation
• Media files CMS
• Commissioned images metadata

3
Intranet changes

• Breaking down large pages into chunks (e.g.,
  section standards)
• Adding Google search (mid-January)
• Minor updates for consistency (e.g., greater
  accuracy in style application)

4
Acrobat 7

• Updating to new version across the teams
• Getting updated settings in place - phase 1
• Updated settings from MIT accessibility teams -
  phase 2 (early December)

5
Technical Requirements

• Moving to a single tech requirements page
  (similar to trademarks)
• Make link from CHP section page to file type
  anchor link on tech requirements page (see
  http//ocw.mit.edu/OcwWeb/Global/OCWHelp/technical
  -faq.htm)

6
Technical RequirementsCHP Example

• Instead of
• RealOne? Player software is required to run the
  .rm files found in this course. MATLAB software
  is required to run the .m files found on a course
  site. Microsoft Excel software is recommended
  for viewing the .xls files found on a course
  site. Free Microsoft Excel viewer software can
  also be used to view the .xls files.
• Use
• Special software is required to use some of the
  files in this course .rm, .m, and .xls.
• Each file type is a link to the appropriate
  anchor on the tech req. page.

7
Technical RequirementsSection Example

• Instead of
• RealOne? Player software is required to run the
  .rm files found in this section.
• Use
• Special software is required to use some of the
  files in this section .rm.
• Each file type is a link to the appropriate
  anchor on the tech req. page.

8
CHP Spacing

• No ltpgt tags around description or highlights.
• No lt/ brgt within Technical Requirements subhead.
• Spacing between subheads and text more standard.
• CSS style takes care of spacing.

9
Audio/Video notation

• When creating a shell table for video/audio to be
  included by Prod later
• Use capital K for bit rate notation rather than
  lowercase k

10
Inaccessible Content Notation

• For accessibility we need to note to users when
  documents are known to be inaccessible.
• Scanned materials PDFs that couldnt be made
  accessible
• Add instructional text at the top of the section
  page and add pound sign next to each document
  w/issues in the section.

11
Inaccessible Content Notation Examples

• This section contains documents created from
  scanned original files, which are inaccessible to
  screen reader software. A symbol is used to
  denote such documents.
• How to boil an egg (PDF)

12
Inaccessible Content Notation Examples

• This section contains documents that could not be
  made accessible to screen reader software. A
  symbol is used to denote such documents.
• How to boil an egg (PDF)

13
Media Files CMS

• No more small .mov, .mp3 or other file types in
  CMS.
• Accessibility concerns.
• Will all be special sections.
• Please alert Prod if any such file types are
  submitted with a spec.

14
Commissioned Images Metadata

• Add minimal metadata into images in
  Illustrator/Photoshop
• Data will end up embedded in jpgs that are
  inserted into PDFs used on CHPs
• Best practice in the field at this point.

15
Commissioned Images Metadata
Course title.
MIT OpenCourseWare
Leave as is
http//ocw.mit.edu/OcwWeb/Global/terms-of-use.htm
http//ocw.mit.edu