Finally, let's discuss the least frequent checkpoints of Section 508. These typically occur less 
than 5 percent of the time. Again, it's important to know what the requirement are, but it 
is very unlikely that you will need to address these requirements when constructing 
your web page. Section 508 checkpoints E and F refer to image maps and making image maps 
accessible. An example of an image map is located at the url presented here. The interactive 
campus map at CSUCI is an image that has each of the buildings 
marked as a clickable area, which takes you to a separate page about that building. There 
are special steps that are required to make image maps accessible. But, fortunately, 
image maps occur very infrequently on web pages, and if you require assistance, 
please contact web services. Section 508 checkpoint I discusses requirements for pages 
that are laid out with frames. If you've never seen a page with frames, here's a good example. 
This is an old technique that is no longer used very much on the web where a page would be laid 
out in separate frames and each frame actually contains its own individual web page. These 
frames could be resized; and, over time, this technique proved to be difficult not only for web 
site designers to maintain but for visitors, especially persons with disabilities or users of 
assistive technology to navigate in an efficient way. So most pages are not laid out using 
frames. The CSUCI web site does not use frames. If you're not using frames in the design of 
your web page, there's nothing you need to do for this checkpoint. If your page happens 
to use frames, you need to make sure that your frames are titled using appropriate frame titles 
and that they're named in meaningful ways. Section 508 checkpoint L is really meant for 
web programmers. We're not going to discuss this checkpoint today in further detail. Suffice it to 
say that, if you create web applications or are a programmer, you'll need to take 
some extra steps to make sure that the scripts that you're incorporating in your web page 
meet with Section 508 requirements. This includes making sure that your scripts 
and applications are navigable without a mouse; that they work correctly using screen readers 
or other assistive technology; and when scripting languages are turned off, that all elements 
are still accessible and usable. If you're not a programmer, you can skip this checkpoint because 
it doesn't really apply to you. The final of the 16 checkpoints, checkpoint P, again really 
applies to programmers that are designing scripts or web applications that require people 
to complete tasks on the web within a certain period of time. If you're not using a timed exam 
or a timed script or application on your web page, this checkpoint doesn't apply to you. 
So that completes the less and least frequently used checkpoints of Section 508.