U.S. Department of Energy - Energy Efficiency and Renewable Energy
Communication Standards and Guidelines
Web Technical Guidelines
Top Five Standards Every EERE Web Developer Should Know
These are the top five technical standards that every EERE Web Developer should know and apply in their work on the EERE Web site.
-
Before a site goes live, it must meet the requirements on the Technical QA checklist. Checking your sites against the checklist while you code will assure that your site is 508 compliant and meets EERE's coding standards.
-
Know EERE's general coding standards, which contain information about EERE and 508 standards for html syntax, forms, data tables, links to native files, and scripting.
-
Most of EERE's sites are hosted in the RedDot CMS. Coders using RedDot should know how to make edits within RedDot and be aware of the workflow process.
-
PDFs are extremely common on EERE, and must be prepared so they are 508 compliant and optimized for search engines.
-
Applications have special requirements and standards. Developers producing Web applications should know the requirements for developing applications and obtaining approval before starting.
EERE's Web Technical Guidelines cover the more technical aspects of developing a Web site, including coding, graphics, and multimedia. Developers and designers should use these guidelines to ensure that their work follows EERE and federal guidelines for Web sites.
Also see the Web Project Management Guidelines and Web Content Guidelines. Technical work should be included and budgeted in project charters and maintenance plans. Both of these documents should be submitted to the EERE Web Manager for any Web site project.
The following topics are covered in the technical guidelines:
Covers general coding requirements for EERE sites, including Section 508 accessibility standards.
Links to the user guide and QA checklist for the RedDot Content Management System.
Covers policies for newsletters that are sent via an electronic mailing list.
Provides guidelines on preparing graphics for fast and accessible delivery on EERE sites.
Covers guidelines for multimedia, as well as the multimedia QA checklist and podcast standards.
Provides guidelines for naming files and setting up a directory structure for a Web site.
Provides PDF requirements as well as more in-depth resources for writers, PDF creators, and Web developers.
Ensures that all EERE standards are met before a site goes live.
Describes the types of redirects used when URLs change and the criteria for setting up a proxy.
Outlines the process and responsibilities for technical maintenance activities.
Provides explanations of graphics and code for the EERE template.
Describes the process and critical elements that must be included in Web applications and databases for EERE.
|
