Internet and Intranet Web Standards

Transcription

1 FLORIDA DEPARTMENT OF AGRICULTURE AND CONSUMER SERVICES Internet and Intranet Web Standards Revised: May 13, 2015 The standards in this document and the Web Writing and Style Guide encompass the Department of Agriculture and Consumer Services department websites. This includes department-affiliated websites and web applications, which shall also adhere to the Application Development Standards.

2 Table of Contents SECTION 1: SECTION 508, ACCESSIBILITY... 5 Standard 1.1.1: Accessibility (Internet and Intranet)... 5 SECTION 2: INFORMATION ARCHITECTURE... 7 Standard 2.1.1: Contact Information (Internet)... 7 Standard 2.1.2: Contact Information (Intranet)... 7 Web applications shall incorporate a link to contact information within the footer of the application which provides who to contact for assistance with application troubleshooting or questions Standard 2.2.1: Navigation (Internet)... 7 Standard 2.2.2: Navigation (Intranet)... 7 Standard 2.3.1: Department, Commissioner, and Director Names (Internet)... 8 Standard 2.3.2: Division and Director's Name (Intranet)... 8 Standard 2.4.1: Page Footer (Internet)... 8 Standard 2.4.2: Page Footer (Intranet)... 8 SECTION 3: GRAPHICS, MULTIMEDIA, SCRIPTS, AND PLUG-INS... 9 Standard 3.1.1: Copyrights (Internet and Intranet)... 9 Standard 3.2.1: Logos Department Seal (Internet)... 9 Standard 3.2.2: Logos Department Seal (Intranet)... 9 Standard 3.2.3: Logos Divisions (Intranet)... 9 Standard 3.3.1: Animation (Internet and Intranet)... 9 Standard 3.3.2: Animation Multimedia (Internet and Intranet)... 9 Standard 3.4.1: Graphics ALT,TITLE Attributes (Internet and Intranet) Standard 3.4.2: Graphics Static Image Maps (Internet and Intranet) Standard 3.4.3: Graphics Image Size (Internet and Intranet) Standard 3.5.1: JavaScript (Internet and Intranet) SECTION 4: INFORMATION PRESENTATION Standard 4.1.1: Web Writing and Style Guide (Internet and Intranet) Standard 4.2.1: Cascading Style Sheets (CSS) (Internet) Standard 4.2.2: Cascading Style Sheets (CSS) and Server Side Includes (SSI) (Intranet) Standard 4.3.1: Fonts (Internet and Intranet) Standard 4.4.1: Color Scheme (Internet and Intranet) Standard 4.5.1: Department-Affiliated Websites (Internet) Standard 4.5.2: Department Affiliated Websites (Intranet) Standard 4.6.1: Forms (Intranet and Internet) Standard 4.7.1: Browsers (Internet and Intranet) Standard 4.8.1: Web Page Width (Internet and Intranet) Standard 4.9.1: Frames and iframes (Internet and Intranet) Standard : Hyperlinks (Internet and Intranet) Standard : Hyperlinks Downloadable Files (Internet and Intranet) Standard : File Naming Conventions (Internet and Intranet) Page 2 of 22

3 Standard : Page Titles (Internet and Intranet) Standard : Cookies (Internet and Intranet) Standard : Tables Layout Tables (Internet and Intranet) Standard : Tables Data Tables (Internet and Intranet) Standard : Spelling and Grammar (Internet and Intranet) SECTION 5: EXAMPLES Page Titles (Intranet) SECTION 6: DEFINITIONS Active Server Pages (ASP) ASP.NET Cascading Style Sheets (CSS) Extension Folder Information Architecture Hypertext Markup Language (HTML) Internet Intranet Java Applet JavaScript Web Application Web Page Website World Wide Web World Wide Web Consortium (W3C) SECTION 7: SECTION 508, TERMS AND DEFINITIONS Accessible Applet Assistive Technology Data Tables Documents Equivalent Alternatives Field Element Flicker Functional Text Hertz (Hz) Multimedia Presentation Non-Text Element Plug-in Redundant Text Link Repetitive Navigation Links Scripting Language Style Sheet Synchronized Page 3 of 22

4 Text Equivalent Page 4 of 22

5 SECTION 1: Section 508, Accessibility Standard 1.1.1: Accessibility (Internet and Intranet) All department websites, including web-based applications, and downloadable documents (pdf, doc, xls, etc.) shall adhere to Section 508, subsection , of the Rehabilitation Act and shall follow Administrative Policies and Procedures The standards provided in this section are for your reference and information only. Any changes to Section 508 supersede this section. The department uses an enterprise software system to verify compliance with these requirements. All department websites, including web applications, shall meet or exceed these requirements before being placed in a production environment. A. A text equivalent for every non-text element shall be provided (e.g., via alt, longdesc, or in element content). Refer to standard B. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Refer to section3, standard C. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Refer to section 4, standard D. Documents shall be organized so they are readable without requiring an associated style sheet. To test, disable CSS Styles in your browser and review the site. E. Redundant text links shall be provided for each active region of a server-side image map. F. Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. G. Row and column headers shall be identified for data tables. Refer to section 4, standard H. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Refer to section 4, standard Page 5 of 22

6 I. Frames shall be titled with text that facilitates frame identification and navigation. Refer to section 4, standards J. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55Hz. Refer to section 3, standard K. A text-only page, with equivalent information or functionality, shall be provided to make a website comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. L. When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. To test within Internet Explorer: select Tools > Internet Options. Select the Security tab, click the Internet icon, then click the Custom Level button. Scroll down to the Scripting section and disable active scripting. Remember to enable the feature when you are done testing. M. When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page shall provide a link to a plug-in or applet that complies with (a) through (l). Refer to section 4, standard N. When electronic forms are designed to be completed online, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. Refer to section 4, standard O. A method shall be provided that permits users to skip repetitive navigation links. Set up a method that allows keyboard and visually impaired users the option to skip navigation. Additional possible solutions are suggested by the Utah State University s Center for Persons with Disabilities, found at P. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. Page 6 of 22

7 SECTION 2: Information Architecture Standard 2.1.1: Contact Information (Internet) Every internet web page, including web-based applications, shall include a link to contact information: A. The department s internet website shall prominently link to the FDACS contact us page. B. The FDACS contact page shall incorporate a link to the department s Customer Service Feedback form. C. Web applications shall incorporate a link to contact information within the footer of the application which provides who to contact for assistance with application troubleshooting or questions. Standard 2.1.2: Contact Information (Intranet) Every Intranet web page, including web-based applications, shall include a link to contact information. A. Division web pages shall incorporate a link to contact information within the navigation menu. The link shall be specific to the division and should include division contacts (name and title), links and phone numbers (including the main office number for the division), if applicable. Web applications shall incorporate a link to contact information within the footer of the application which provides who to contact for assistance with application troubleshooting or questions. Standard 2.2.1: Navigation (Internet) Site navigation shall appear on every internet web page. A. Top-level navigation (global links) and section navigation shall be available on every web page so that visitors can navigate with ease. Standard 2.2.2: Navigation (Intranet) Site navigation shall appear on every static intranet web page. A. Top-level navigation (global links) and section navigation shall be available on every static web page so that visitors can navigate with ease. B. Each static web page shall have a prominent link back to the department s intranet home page labeled FDACS Intranet and shall appear as the last item on the navigation menu. C. Web-based applications are not required to have full site navigation, but shall have a link to the department's intranet home page, labeled FDACS Intranet, and division's intranet home page provided within the navigation menu. D. Navigational elements shall be consistent on every web page within the website. Page 7 of 22

8 Standard 2.3.1: Department, Commissioner, and Director Names (Internet) The department s name, commissioner s name (as specified by the Office of Communications) and official seal shall appear within the page header of every internet web page. Standard 2.3.2: Division and Director's Name (Intranet) The division's name and the division director's name shall appear within the page header of every division's intranet web page. Standard 2.4.1: Page Footer (Internet) Links determined by the Web Office including a copyright statement are required on the footer of every web page. Standard 2.4.2: Page Footer (Intranet) Global footer links are required on the footer of every static web page. A. A link to the Administrative Policies and Procedures, OATS Help Desk, Employee Contact Search, and Forms Search shall be included in the footer of each intranet web page. Page 8 of 22

9 Section 3: Graphics, Multimedia, Scripts, and Plug-ins Standard 3.1.1: Copyrights (Internet and Intranet) Never use text, graphics, multimedia files or scripts from another source unless the source explicitly states the material can be copied or written permission is obtained from the owner. A. Releases or permission documentation to publish copyrighted material shall be secured by the division s content liaison prior to publication on the web. Releases or permission documentation for publishing copyrighted material shall be maintained on file permanently by the division s web content liaison and be made available for review upon request. B. A Model Release form to publish a subject s photograph shall be secured prior to publication on the web. Photos may be published on websites with approval from the division director and written release from the subject(s) photographed by completing a Model Release Form (FDACS-01330). Copies of the subject s written release shall be maintained on file permanently by the division s web content liaison and be made available upon request. Standard 3.2.1: Logos Department Seal (Internet) An authorized FDACS seal is required on all department internet web pages. A. The seal shall link to the department s internet home page. Standard 3.2.2: Logos Department Seal (Intranet) The FDACS seal is not required on intranet web pages. Standard 3.2.3: Logos Divisions (Intranet) Divisions can place their authorized logo or an appropriate image(s) within the page header of intranet sites. A. The image(s) should reflect the identity of the division and shall be approved by the Office of Communications and the Web Office. B. The logo shall link to the division s intranet home page. Standard 3.3.1: Animation (Internet and Intranet) When animation is displayed, provide the user the option to pause the animation. A. The BLINK and MARQUEE elements shall not be used. B. Do not cause the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. Some individuals with photosensitive epilepsy can have a seizure triggered by displays that flicker or flash, particularly if the flash has a high intensity and is within certain frequency ranges. Standard 3.3.2: Animation Multimedia (Internet and Intranet) Provide equivalent alternatives for any multimedia presentation. A. Not all users can see or hear multimedia files. To make these files accessible to everyone, provide transcripts and/or descriptions to summarize the audio or video. B. Video, audio or other multimedia shall not start automatically without the request of the user. C. Provide the user the option to pause the audio or video. D. When closed captioning is provided, the text shall be synchronized with the presentation. Page 9 of 22

10 Standard 3.4.1: Graphics ALT,TITLE Attributes (Internet and Intranet) The ALT attribute shall be provided for all images and the TITLE attribute shall be provided for all text links which may be non-descriptive or function in a manner not expected by the user. A. The ALT attribute defines text that will be displayed when a user moves the mouse over an image. It should provide descriptive information to comply with ADA Section 508 guidelines. B. The TITLE attribute defines text that will be read by a screen reader and displayed when a user moves the mouse over the linked text. a. The TITLE attribute should increase the meaning of the text. i. For example: <a href= title= Website of the Florida Department of Agriculture and Consumer Services >FDACS</a> b. The TITLE attribute should describe any function not expected by the user, such as opening a new window/tab or running a JavaScript. i. For example: <a href= target= _blank title= Website of the Florida Department of Agriculture and Consumer Services opens in a new window >FDACS</a> Standard 3.4.2: Graphics Static Image Maps (Internet and Intranet) Server-side image maps are discouraged. A. Provide an alternate text-based method of selecting options when static image maps are used. B. To make client-side static image maps accessible, always assign an ALT description to each area of the image map. These descriptions can be read by a screen reader or other assistive technology device. C. For each active region of a client-side static image map, provide redundant text above or below the image. These links will also provide an alternative for those who do not know they can click the image map. If server-side image maps are used, send coordinates 0, 0 to the server for agents that do not provide the user a means to select specific coordinates. Page 10 of 22

11 Standard 3.4.3: Graphics Image Size (Internet and Intranet) All graphics used shall be meaningful and relevant to the content on the web page and should be resized appropriately for the web. A. Use the attributes WIDTH and HEIGHT to improve page loading. B. Reduce the number of colors and quality of the image used to the minimum needed that support a quality graphic. C. If a large image is being considered, put it on a separate web page and link to the image through a small thumbnail representation. D. Warn users if a link leads to a large graphic and include the estimated number of bytes they will be downloading. Correctly size an image (using graphics software) to the finished presentation size. Never use HTML to change the pixel width and height to something different than the actual size of the image. Standard 3.5.1: JavaScript (Internet and Intranet) A web page with JavaScript shall be able to function properly when the JavaScript is disabled. A. Web pages should never rely solely on JavaScript. B. JavaScript used repeatedly should be placed in an external file. Standard Plug-ins (Internet and Intranet) Navigation and all other critical website functionality must be usable without flash or other special plug-ins. Page 11 of 22

12 Section 4: Information Presentation Standard 4.1.1: Web Writing and Style Guide (Internet and Intranet) All websites shall adhere to the FDACS Web Writing and Style Guide maintained by the Web Office and Office of Communications. Standard 4.2.1: Cascading Style Sheets (CSS) (Internet) Internet web pages shall be developed to utilize Cascading Style Sheets to provide consistent layout and presentation. All web pages shall be printable or have a printable alternative. A. Department web pages are required to use layouts approved by the web office unless an alternative is specifically approved for a special event or program by the Web Office and the Office of Communications. B. Web pages shall be organized so they can be read when CSS is turned off. C. Refer to section 1, standard (D) Avoid splitting a topic across multiple web pages as this makes it difficult for users to print all information on the topic. Keep related information within a single page and use headers to break up the content into manageable chunks. See the department s Web Writing and Style Guide for additional information. Standard 4.2.2: Cascading Style Sheets (CSS) and Server Side Includes (SSI) (Intranet) Intranet web pages shall be developed from a CSS to provide consistent layout and presentation throughout division level pages. All web pages shall be printable or have a printable alternative. A. Division web pages shall have a consistent layout and shall appear different from the internet page layout. B. SSI files shall be utilized for global changes to be reflected immediately. C. Web pages shall be organized so they can be read when CSS is turned off. D. Refer to section 1, standard (D) Avoid inline CSS styles by using an external CSS file instead. Page 12 of 22

13 Standard 4.3.1: Fonts (Internet and Intranet) Do not use the deprecated Font tag; use Cascading Style Sheets (CSS) to control font presentation. A. Use the font properties in CSS instead of the HTML <font> tag to control font styles. B. Font color for text and links shall be determined by CSS. C. Font styles shall be determined by CSS. D. Do not use underline (<u></u>), as this is the standard format for links. E. Use heading elements to convey document structure and use them according to specification. a. Example: In HTML, H2 elements should follow H1 elements. H3 elements should follow H2 elements, etc. Header levels should not be skipped (e.g., H1 directly to H3). Use all-caps sparingly. In some cases, all-caps can make text hard to read. Standard 4.4.1: Color Scheme (Internet and Intranet) Color schemes shall be consistent throughout each website and be determined by the website s Cascading Style Sheet (CSS). As a quick test, print the page on a black and white printer to determine if the information can still be discerned. Use the WAVE accessibility evaluation tool ( for a more precise test. Determine that links are not distinguished by color alone. Do not use color to mark required fields in a form; use symbols instead. A combination of symbols and colors is allowed Standard 4.5.1: Department-Affiliated Websites (Internet) Web pages designed for department-affiliated programs shall be approved by the department Web Office and Office of Communications prior to being posted on the internet. A. All department-affiliated websites shall include the full name of the department, the Commissioner s name, and a link back to FreshFromFlorida.com. Standard 4.5.2: Department Affiliated Websites (Intranet) Web pages designed for department-affiliated programs shall not be kept on the intranet web servers. Standard 4.6.1: Forms (Intranet and Internet) Use appropriate HTML markup specifically intended to enhance accessibility of online forms. A. All internet department forms, accessible from the web, approved by the department forms committee shall reside within the department s internet forms directory. B. All intranet department forms, accessible from the web, approved by the department forms committee shall reside within the intranet forms directory. C. All links to department internet forms shall be linked to the department s internet forms directory. D. All links to department intranet forms shall be linked to the intranet forms directory. E. Use a simple single column layout. F. Text-boxes should be appropriately sized for the intended content. Page 13 of 22

14 G. Label form fields with clear and meaningful explanations and use the <LABEL> tag to associate field labels with their corresponding form element. H. If fields are required, label them as required fields by using an asterisk (*). I. Avoid the use of graphic buttons for submission. J. Selection lists and drop-down menus should be short and listed in alphabetical order. K. Drop-down menus providing links to the selected item shall be accompanied by a submit button to be fully accessible. L. Use tab stops. When fields are added to a form, it can affect the order in which the user accesses the fields when tabbing through the form. Tab stops should be set to access the form fields from top to bottom and left to right. M. Forms should be formatted to present requests for information in a cohesive display. The amount of time it requires for the user to enter the data should be evaluated against the amount of data to be entered. In other words, if a small amount of data is being requested, the format should not require the user to spend a lot of time completing the form. N. Submission of data from users over the internet shall comply with current department Administrative Policies and Procedures for access and security. Standard 4.7.1: Browsers (Internet and Intranet) Web pages shall display correctly when viewed with the current versions of popular browsers (Internet Explorer and other current industry standards). Web pages shall also display correctly when using a browser version that is two versions old. A. Do not change the appearance or function of the mouse (do not use trailing cursors or disable the right click). B. Do not interfere with the normal function of the keyboard. C. Do not change or interfere with the function of the browser by disabling the back button. For a list of current browsers, contact the Web Office. Use access keys carefully. Standard 4.8.1: Web Page Width (Internet and Intranet) A web page shall be designed so that a horizontal scrollbar does not appear to a visitor with a set resolution of 1024 x 768. Set the width to 1,000 pixels or use proportional design (i.e. max width is 100%). Web applications may show a horizontal scrollbar to display data if the space available is not sufficient to display all necessary fields/data. Standard 4.9.1: Frames and iframes (Internet and Intranet) Do not use frames. iframes may be used, but must be accessible. See the guidelines and recommendations provided by WebAIM on frames ( Page 14 of 22

15 Standard : Hyperlinks (Internet and Intranet) Identify the target of every hyperlink with descriptive text. A. Hyperlinks that open a new browser window shall be clearly marked indicating a new window will be opened through the use of the TITLE attribute. B. Hyperlinks located on intranet websites which take the user to an internet website shall be clearly marked through the use of the TITLE attribute. See Standard (B) for additional information. C. Do not link to non-descriptive phrases, such as Click here or More information. a. Undesirable Click here for our special events. b. Desirable View a list of our special events. D. Minimize the number of hyperlinks in a single line of text as this makes reading the links difficult. E. Use as few words as possible for the clickable text, while still supplying meaning, as too many words used in one link can be confusing. a. Undesirable The St. Joe Company is Florida s largest private landowner with approximately one million acres in northwest Florida. b. Desirable The St. Joe Company is Florida s largest private landowner with approximately one million acres in northwest Florida. F. Include the complete address to links for users who do not have an program configured. Example WebHelp@FreshFromFlorida.com. When possible, use root relative or relative links instead of absolute links. Inform the user that the link will open a new window. For example: a. <a href="new-page.htm" target="_blank" title= A Wonderful Page opens in a new window >A Wonderful Page</a> b. <a href="new-page.htm" target="_blank"><img src="my_image.gif" alt="my Image opens in a new window" width="200" height="300"></a> Page 15 of 22

16 Standard : Hyperlinks Downloadable Files (Internet and Intranet) Hyperlinks to downloadable files shall include a text description that contains the file type. If a plug-in is required, access to download the plug-in should be provided on the web page. A. For example, with a PDF document a button or text link to Get Adobe Reader shall be provided on all pages containing PDF downloads. The link shall point to the Adobe Reader download page. It is recommended that this code be kept in an SSI for intranet pages. Example #1: List of links on a web page ABC Report [PDF] 216 KB EFG Report [DOC] 500 KB HIJ Report [XLS] 2 MB Note: This functionality is part of our internet template: therefore, no further action is required by the developer to meet this standard. Size notification is not mandatory, but is recommended. If the web page contains a variety of downloadable files (PDF, XLS, PPS, DOC), place a text link on the web page with the text Document Reader Download Link. Standard : File Naming Conventions (Internet and Intranet) Naming conventions should ensure that the file can be interpreted across all platforms and browsers, including text-only browsers. A. Keep file names under 32 characters. B. Use lowercase naming conventions for files and folders names. C. Do not use spaces in file names. D. Internet CMS: The name given to an object should be the exact name of the file. a. For example: A file with the name meeting_agenda.pdf should have the name of meeting_agenda.pdf. If the file name will contain more than one word, use the "_" (underscore) or "-" (hyphen) character to separate each word. Standard : Page Titles (Internet and Intranet) Each web page on a site shall have a unique, descriptive name. Examples for the intranet are available in Section 5. Internet page titles are handled directly by our web Content Management System. Keep titles short: Five to seven words, 65 characters or less. Browsers will accept more, but only the first 65 characters are shown in the favorites/bookmarks list. Make headings clear and unambiguous. Avoid abbreviations and acronyms (unless they are typical terms the target audiences expect). Page 16 of 22

17 Standard : Cookies (Internet and Intranet) Do not use cookies to collect a user s personal information. Standard : Tables Layout Tables (Internet and Intranet) Table-less design practices shall be used in place of layout tables to control site presentation and layout. Standard : Tables Data Tables (Internet and Intranet) A. Tables shall be used for tabular data only. Identify row and column headers by using the table header tag <th>. B. Ensure that the contents of the table make sense when removed from the table. C. Associate data cells with the appropriate headers by using the ID and HEADERS attributes. D. Do not nest data tables. E. Provide names or titles for data tables using the <caption> tag. F. Provide summaries using the SUMMARY attribute. Use the simplest table configuration possible. For more information on making tables accessible, review the resources available from WebAim ( Standard : Spelling and Grammar (Internet and Intranet) Web pages shall be checked for spelling and grammatical errors. Page 17 of 22

18 Section 5: Examples Page Titles (Intranet) Option 1 Home Page: Division of ABC FDACS Intranet Option 2 Home Page: Division of ABC Florida Department of Agriculture and Consumer Services Intranet Option 1 Sub Pages: Division of ABC, Page Title FDACS Intranet Option 2 Sub Pages: Page Title, Division of ABC FDACS Intranet Whichever option is chosen, make sure it is consistent throughout the site. Page 18 of 22

19 Section 6: Definitions Active Server Pages (ASP) A server-side scripting environment developed by Microsoft, that can combine such technologies as, HTML, scripts and ActiveX components to create dynamic web-based applications. Application Introductory Page A page used for web applications which may provide the purpose of the application, instructions on how to use the application, and who to contact with questions. ASP.NET A server-side web technology used to create web pages and web services which was developed my Microsoft. Pages load much faster than classic ASP pages because embedded VBScript or Jscript have to be continuously interpreted and cached. Cascading Style Sheets (CSS) Feature of HTML that allows developers to create style sheets in order to define how different elements of the page, such as headings, paragraphs, and links, will display. Extension A filename extension usually follows a period and indicates the type of information that is stored in the file. For example, Microsoft Word documents end in.doc, Adobe Acrobat files with.pdf ; Cascading Style Sheets are.css, etc. Folder A folder is an object that can hold multiple documents or a collection of related files. Folders may also be referred to as "directories." Information Architecture Information Architecture is a term that has recently become associated with website management. In the early days of the internet, a website with a handful of pages was easy to organize. However, sites quickly grew and many found themselves wrestling with a huge monster how can you provide a concise, organized and uniform presentation for thousands of pages? The concept of approaching the design of information in a manner similar to the approach an architect might take with the design of a building has rapidly become an accepted technique. For instance, the steps an architect might follow when constructing a new building: Gather information about who will use the building and how they need to use it, Organize the needs into a pattern that clarifies their nature and interactions, and Design a building that will--by means of its rooms, fixtures, and layout--meet those needs By the same token, an information architect might follow these steps when redesigning a website: Clarify the site s mission and vision to balance the needs of its owners and visitors. Determine the content and functionality required. Specify how users will find information in the site by defining its organization, navigation, labeling, and searching systems. Outline how the site will accommodate change and growth over time. Page 19 of 22

20 So, how do you provide a concise, organized and uniform presentation for thousands of pages? You apply the evolving principles of information architecture as they apply to web design. Hypertext Markup Language (HTML) A combination of markup symbols that instruct a web browser how to render the contents of a web page. Internet A public network of millions of connected computers. The World Wide Web, and file transfer protocol are all a portion of the internet. Intranet A version of the internet confined to an organization. Java Applet A small program (mini-application) that can be sent along with a web page to perform animations, calculations, or other simple tasks. JavaScript A scripting language developed by Netscape to enable web authors to design interactive sites. Javascript can interact with HTML source code, enabling web authors to spice up their sites with dynamic content. Web Application An application that is accessed via the web over a network such as the internet or an intranet. Web Page When used in this document, it refers to a page of information that resides on a web server and uses HTML coding to present the information. This includes.htm,.html,.asp and other file types. Website When used in this document, it refers to a collection of web pages maintained by a single state agency or state government organizational group. World Wide Web A portion of the internet that consists mainly of web pages built with hypertext. World Wide Web Consortium (W3C) An international organization that seeks to promote standards for the web to assist in furthering its evolution. Page 20 of 22

21 Section 7: Section 508, Terms and Definitions Accessible Content is accessible when it may be used by someone with a disability. Applet An applet is a program that is part of content, and that the user agent executes. Assistive Technology Software of hardware that has been specifically designed to assist people with disabilities in carrying out daily activities. Common software-based assistive technologies include screen readers, screen magnifiers, speech synthesizers, and voice input software which operate in conjunction with graphical desktop browsers. Hardware assistive technologies include alternative keyboards and pointing devices. Data Tables Tables used to represent tabular information. Documents Names, structured units of text, images, or other elements; web pages. Equivalent Alternatives Captioning provided for audio information, audio description of visual information, or other alternative presentations of information that fulfills the same function or purpose upon presentation to the user. Field Element A user interface element that appears within an electronic form field. Flicker An unintentional and undesirable cyclic variation in display of a screen image. Functional Text Text that when read conveys an accurate message as to what is being displayed by the script or that describes or what action the script will perform. Hertz (Hz) The international unit of frequency, equal to one cycle per second. Multimedia Presentation Presentations that include a combination of more than one type of media, such as text, audio and visual information. Non-Text Element Any element that is not presented in electronically readable text (e.g., an image, image of text, graphic, audio clip, or other element) and that conveys meaning that is required for comprehension of content or to facilitate navigation. Page 21 of 22

22 Plug-in An application that is used to extend the functionality of a web browser. Plug-ins can be downloaded and installed on the user's computer to make it possible for their web browsers to display or play the content of the files with proprietary formats when these files are included as a part of the web page. Redundant Text Link A link that points to the same location as the active image region, or to another location that is equivalent to that referenced by the active image region. Repetitive Navigation Links A set of routine navigation links that appear on the top or the side on a web page. Scripting Language A programming language that is used to manipulate, customize, and automate the facilities of an existing system. Note this provision only refers to the use of scripting languages for creating and displaying dynamic web content. Style Sheet A collection of formatting instructions stored in a file that determines how the layout of the documents to which it is attached is presented (e.g. displayed on screens, printed, or pronounced). Synchronized Having common timing and coordination of execution. Text Equivalent Words added as text to represent the purpose of a non-text element. Page 22 of 22