Skip Navigation
 
     

Web Services > Accessibility > AccVerify > Repairing without the wizard

Common Errors and how to make them compliant:
Alternate Text Frames Blink or Marquee Scripts

Alternate text: 508 Standards, Section 1194.22(a)

Points to remember when creating alternate text

Images
Form inputs
Applets
IFrames
Image maps and area elements
Embed and objects

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.

Insert ALT tag text

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.

To top of page

Correcting alternate text tags for input elements

Alternate text for input fields associated with forms allows users of assistive technology to clearly identify what type of information is requested for each field. While this may seem obvious visually, remove the visual cues and sometimes forms can seem vague and confusing. Alternate text makes it easier to understand.

Add ALT tag for text

By adding the ' alt="Firstname" ' the input element meets the standards. Remember, the alternate text should be meaningful and represent the data requested by the form field.

To top of page

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 applet function

Add the alternate text within the <applet> tag and the Element content between the <applet> and </applet> tags.

To top of page

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 inline frame text

Add the Element content between the <iframe> and </iframe> tags.

To top of page

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 ALT text for image map

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.

To top of page

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.

Noembed text for multimedia file

Place the description between the <noembed> and </noembed> tags.

To top of page

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.

Add frame description

Insert the <noframes> and </noframes> tags along with the message after the first <noframeset> tag. Add the 'title' element to each </frame> tag.

Top of Page


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 <blink> tag or a <marquee> tag must have the tag removed.

The blink or marquee tag must be removed from the code by hand.

Remove blinking or marquee text

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.

Insert noscript text

Place the information between the <noscript> and </noscript> tags.

To top of page

Visual Checklist for Section 508 compliance


Return to Top