Program content should be tested by a content expert or educationalist for accuracy.
Test screen text (including titles, body text, captions and labels) for
As recommended in Apple Computer, Inc., (1994), Multimedia Demystified, p.223, proofing should be performed early in the development process when content is in an easily checkable form. Transferring content to screen, though, is often a slow and tedious process and errors can creep in. Equally, giving assets file names in production and integrating the assets in programming can cause errors to appear. Content should again be checked at the end of the production process before mastering to trap for these errors.
Test illustrative and sound assets to ensure that
- stylistic consistency (in capitalisation and punctuation, say)
- content accuracy.
- they match labels and captions
- they are accurate
- proper names
- job titles
- any telephone and other contact numbers mentioned
- copyright notices
- copyright acknowledgements
- other acknowledgements and information, such as developing team-member names, to appear on title screens, say.