Alternate text: 508 Standards, Section 1194.22(a)
Correcting alternate text tags for images
The purpose of alternate text: When an image can not be displayed in a web page, or to a person who has impaired vision alternate text provides information explaining the picture.
By adding the ' alt="description of image here" ' you make this image comply with the rules. AccRepair makes this task easy by building a library that will remember the text you associate with an image and use that text automatically each time that image is used, potentially saving you hours of work.
Correcting alternate text tags and content element for applets
Applets can be run when a user presses a button or a link. To a user of assistive technology the function of such an applet is not always readily discernable. By including both alternate text and content element notation it informs the user that an applet is going to be invoked and what the function does.
Add the alternate text within the <applet> tag and the Element content between the <applet> and </applet> tags.
Correcting content element for inline frames (iframe)
Inline frames are essentially a web page within a web page. Visually this is fairly easy to discern, but without the visual cues a user may feel as if they have stumbled upon a whole new webpage by accident. Giving the user Content Elements allows them to make the distinction that is so readily available visually.
Add the Element content between the <iframe> and </iframe> tags.
Correcting alternate text tags for image map elements
Image maps are especially useful in allowing users to make a selection based upon some sort of picture. While novel in its approach it can pose some serious difficulties for users of assistive technology without the proper alternate text tags.
Add the alternate text for each image as shown. For links, make the alternative text descriptive as to what web page the user is going to.
Correcting embed and noembed tags
Not all users allow embeded mutlimedia files to play. It is important to inform the users that such an item exists within the webpage. You do so by including the <noembed> and </noembed> tags.
Frames: 508 Standards, Section 1194.22(i):
Correcting errors in pages with frames
Purpose of <frames> tag: Frames are used to break a page up into logical units. Many people use frames to provide a navigation area that never changes and a main display area. Use of the <noframes> tag allows people that do not have frames enabled to see that the site is not empty. You can also use this area to provide a link to a noframe version of your site. Proper use of the title attribute allows users of assistive technology to navigate the site easier by identifying which frame they are in.
Frames are a poor way of organizing a page and present a myriad of accessibility issues. If you have a page that utilizes frames it should be recoded using CSS (Cascading Style Sheets).
Blinking or scrolling text: 508 Standards, Section 1194.22(j):
Blinking or marquee text is not allowed
Text that blinks or scrolls across the screen can cause seizures and is not allowed. Any text placed within a tag or atag must have the tag removed.The blink or marquee tag must be removed from the code by hand.
Scripts: 508 Standards, Section 1194.22(l):
Correcting the noscript error
Purpose of <script> and <noscript> tag: Scripts allow small program-like functions to operate on a webpage. They can add flare or functionality to a website. If someone does not have scripts enabled they will miss out on any information that may be provided through a script without ever knowing. By providing the <noscript> tag you inform the user that there is something they are not receiving. Correction: Merely informing users that they are missing out on information is not complying with ADA Section 508 guidelines. Noscript elements should direct users to alternative methods of receiving the same information or utility. Menu systems that utilize scripting elements should have redundant links in the NOSCRIPT section so that all users will have access.