What is Accessibility?

The Web is fundamentally designed to work for all people, whatever their hardware, software, language, culture, location, or physical or mental ability. When the Web meets this goal, it is accessible to people with a diverse range of hearing, movement, sight and cognitive abilities.

Learn more about accessibility standards at W3C®

Section 508 Compliance

The Florida Tech Web Services Office shall actively and vigilantly seek full compliance with all technical and accessibility requirements set forth in section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) for all official university websites and Web-based information.

1194.22 Web-based Intranet and Internet information and applications.
  1. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc" or in element content).
  2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  3. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  4. Documents shall be organized so they are readable without requiring an associated style sheet.
  5. Redundant text links shall be provided for each active region of a server-side image map.
  6. 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.
  7. Row and column headers shall be identified for data tables.
  8. 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.
  9. Frames shall be titled with text that facilitates frame identification and navigation.
  10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
  11. 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.
  12. 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.
  13. 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 must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
  14. 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.
  15. A method shall be provided that permits users to skip repetitive navigation links.
  16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

See Detailed Description at:

Accessibility Recommendations

  1. Consult the latest W3C guidelines.
  2. Use high contrast text/background combinations with little or no pattern in background.
  3. Use semantic markup, like proper heading styles to structure a page


    , etc.

  4. Use CSS when possible.
  5. Use "ALT" attributes to describe images.
  6. Use relative font sizes.
  7. Make sure page is "backwards compatible" (that is, that it "fails gracefully").

Strongly Discouraged (all hinder accessibility for those with visual impairments)

  1. Use of red/green combinations.
  2. Designation of headings by using "Bold" formatting.
  3. Making navigation or other essential information depend solely on images.