SECTION V. Web Publications Conventions
G. Publishing elements other than HTML
1. Linking to non-Web files
STANDARDS:
When linking to non-Web pages, display the software extension and file size in brackets to the right of the link. If a graphic is used as an alternative, such as a .pdf logo, alternate text should be used with the graphic using brackets with the same content.
Examples:
course listings [pdf 110k]
budget report [xls 78k]
minutes of public hearing [doc 42k]
blueprints 203-212 [dgn 538k]
ALTERNATIVE:
Using an appropriate graphic next to a document which denotes its file type is acceptable, but the software extension and file size should be added as alternate text to the graphic. Examples would be an adobe image next to a .pdf file, or an MS Word image next to an MS Word document.
Explanation:
The extension lets the user know what software to employ in opening the file. From the file size, users can estimate the length of time that will be required for download. This is helpful information for all users but it is especially important for users of dial-up modems that run at slow speeds
2. JavaScript and Flash
STANDARDS:
a. If JavaScript or Flash is employed anywhere on the page as a link, there should be a text link substitute for these links on the page. See Section V, Navigation.
Explanation:
JavaScript and Flash links are not readable by most search spiders and robots or by the speech synthesizers used by the visually impaired. They also don’t work with some older browsers. If JavaScript is turned off, selection boxes, on the other hand, will not work. A server side script (such as Perl) must be used instead.
3. Cascading Style Sheets (CSS) Recommendations:
a. A institutional Web page should control presentation with CSS style sheets which have been approved by the campus Web Development Office.
Explanation:
Style sheets enhance accessibility by more precisely controlling layout and appearance, making Web pages easier to follow for users with various disabilities as well as for the general public.
b. Linking to external style sheets rather than using embedded ones is recommended for consistency.
Explanation:
Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g., fonts, colors, spacing) to Web documents. By attaching style sheets to structured documents on the Web (e.g., in HTML), authors and readers can influence the presentation of documents without sacrificing device-independence or adding new HTML tags. Only by referencing an external file (linking) will you get the maintenance benefits of being able to update the look of your entire site with a single change. You should still be able to read the HTML page if the cascading style sheets are turned off. Reference W3C Cascading Style Sheets [www.w3.org/Style/CSS/]
4. Common Gateway Interface (CGI) scripts
STANDARDS:
CGI scripts can be implemented on the UWRF Web servers. However, developers are required to have their forms approved by the Web Development Office before implementation.
Explanation:
PERL scripts must be reviewed for security issues and functionality before being posted to the server.
5. Form Mail
STANDARDS:
Institutional Web sites may feature pages that allow users to submit data to a campus email recipient. UWRF uses formmail.pl or PHP to deliver form mail based messages.
Recommendations:
Before creating each new form mail interface, campus Web developers must consult the Web Development Office. The Web Development Office provides assistance with properly setting up form mail Web pages.
6. PDF Files
STANDARDS:
PDF Should be used when
- When the original formatting of document must remain intact. (i.e. forms, complicated columnar layouts)
- When a printable form is desired that requires a signature
- When your audience is small or unique but the documentation is abundant (i.e. detailed government documents)
PDF should NOT be used:
- If the original of the document formatting is a single column document, thus it can easily be turned into an HTML page
- If the document is NOT intended to be printed
- Large PDF files containing many pages should be segmented into separate PDF documents to reduce download time. Long PDF downloads appear as a static white screen for the recipients. This can be mistaken for a broken link or faulty document.
PDF files should be “tagged” to make PDF files accessible to standard screen readers that support tagged PDF (like JAWS and Window Eyes).
Explanation:
A PDF is a digital hardcopy of a document. The originating document may be an MS Word Document or other format type.
Creating an HTML directory with descriptive links to the segments of the PDF document will make it simple for visitors to find only the content they want. This eliminates the need for a user to download a lengthy PDF document to review only two paragraphs of information, for example in a newsletter.
