IT Leadership Banner and Tagline 

Web Accessibility Guidelines 

All state agency and institution of higher learning websites must meet the web accessibility standards as defined in 1 TAC 206. These standards map to Section 508 of the Rehabilitation Act of 1973, which serve as the foundation for 1 TAC 206.

The following guidelines offer some basic information on the standards. They can be used for reference, but they do not replace the 1 TAC 206 standards. 

For additional information, refer to 1 TAC 206 and/or Section 508.

Applets and Plug-Ins – If your page requires an applet, plug-in or other application on the client system, provide a link to a Section 508-compliant version of the software.

Color – If your page uses color to convey information such as numeric value (such as red to indicate a negative monetary value), hyperlinked text, importance (such as an alert or warning), or special value/meaning (such as red text to show a required field on a form), make sure that the information is equally understandable without color.

Electronic Forms – If your page includes an electronic form that needs to be completed online, design the form so that people using assistive technology are able to complete and submit the form.

Flickering – If your page includes images that flicker or flash repeatedly, or uses a strobe effect, make sure that the flicker rate is greater than 2 Hertz or less than 55 Hertz.

Frames – If your page uses frames, include text and tags that will help users understand the frame’s purpose and function.

Image Maps, Client-Side – If your page includes a client-side image map, provide alternative links and alt attributes.

Image Maps, Server-Side – If your page includes a server-side image map, provide a descriptive redundant text link for each active area.

Multimedia Synchronization – If your page includes an audio and/or video presentation, it should also include an equivalent alternative that accommodates users with visual or auditory disabilities.

Navigation – If your page contains repetitive navigational elements, allow users of assistive technology to skip over navigational links or filter mechanisms and go directly to content.

Non-Text Elements: Images, Multimedia, Buttons, Animations, Applets and Scripts – If your page includes non-text elements (such as graphics, images, or input buttons), provide a text equivalent or description of each element.

Scripting Languages – If your page uses client-side scripting languages to display content or create interface elements, include functional text that can be read by assistive technology.

Style Sheets – Organize your web page so that it is still readable and understandable if the style sheet is removed.

Tables, Simple – If your page uses tables to display information, use tags to clearly identify row and column headers.

Tables, Complex – If your page uses complex tables (i.e., two or more levels of row or column headers), use id and header attributes to clearly identify information.

Testing – Plan for regular accessibility testing of your site.

Text-Only Pages – If your page cannot comply with accessibility guidelines in any other way, provide a text-only page with equivalent information or functionality.

Timed Responses – If your page requires a timed response (for a timed test or a secure web application), alert the user and provide them with a way to request more time.