Section 508 Compliance

HTML Coding Tutorial

Using Applets and Plug-Ins

(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 must provide a link to a plug-in or applet that complies with �1194.21(a) through (l)
Explanation: While most web browsers can easily read HTML and display it to the user, several private companies have developed proprietary file formats for transmitting and displaying special content, such as multimedia or very precisely defined documents.
Importance: Because these file formats are proprietary, web browsers cannot ordinarily display them. To make it possible for these files to be viewed by web browsers, add-on programs or "plug-ins" can be downloaded and installed on the user's computer that will make it possible for their web browsers to display or play the content of the files.

Bad Example

1.  Not providing a link for proprietary files
No proprietary link If the user does not have the necessary program to use the file, downloading the file is pointless and the user might miss important information.

Good Example

1.  Include a link for proprietary files
Includes proprietary link The site provides a link to the PDF file, and a link to the Adobe Reader download page, to allow users who don't have the Adobe Reader program installed to view the document.

Do-It-Yourself Fixes

Again, complying with this section of accessibility is very easy. The main concept to remember is that whenever you include a link to a file, no matter what kind of media it is, include another link to a program that can uses the file so users who couldn't view the file now can. All it takes is another link directly after to linked propietary file to the program.