Accessible Web Design Examples

These examples have been created to help directly identify common 508 issues. Code is provided for advanced users

Try the WebXact to check http://www.siu.edu/~dss/Grant/508%20examples.htm for errors.

Images - Synchronized Multimedia - Color - Style Sheets - Server-Side Image Maps - Client-Side Image Maps - Table Headers - Complex Tables - Frames - Flicker - Text Only Last Resort - Scripting - Applets and Plug-ins - Forms - Navigation Skipping - Timed Responses


Images

1194.22 (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

Rationale: Individuals who are blind cannot perceive information presented in images; screen reading software reads alternate text instead.

Accessible Image "Alt" Text Example

SIU Logo

<IMG SRC="Images/SIU.gif" ALT="SIUC Logo" WIDTH="208" HEIGHT="117" BORDER="0">

Result: When a screen reader encounters this image, it will read "SIUC logo."


Non-Accessible Image "Alt" Text Example


<IMG SRC="Images/SIU.gif" WIDTH="208" HEIGHT="117" BORDER="0">

Result: When a screen reader / text only browser encounters this image, it will read "image" instead of SIUC logo.


Accessible Image "longdesc" Example

DSS Organizational ChartD

<SRC="Images/org.gif" WIDTH="220" HEIGHT="104" ALT="DSS Organizational Chart"><A HREF="Long.htm">D</A>

Result: When a screen reader / text only browser encounters this image, it will read a short description of the image that should be suitable for the user to decide whether he or she wants to follow the "D" link to the long description.


Non-Accessible Image "longdesc" Example

<SRC="Images/org.gif" WIDTH="220" HEIGHT="104">

Result: When a screen reader / text only browser encounters this image, it will only read "image."

Automatic vs Manual: When using an accessibility program, an image will automatically fail if it does not have an "alt" tag. If an image needs a long description but does not have one, user input through a manual check will be required prior to passing or failing.


Synchronized Multimedia

1194.22 (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Rationale: Individuals who are deaf or hard of hearing may require captions to access the audio information in multimedia.

Accessible Captioned Multimedia

Captioned with Magpi program

Magpi timecodes and captions for Wendler video link

Result: Audio information is presented visually using a program

Automatic vs Manual: You will always be prompted when your pages contain multimedia.

Further Resources: http://cita.rehab.uiuc.edu/new/multimedia/index.html


Color

1194.22 (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Rationale: Those who are unable to process a full spectrum of colors such as users with color-blindness or limited vision may miss information presented with color.

Non-Accessible Color Link

Improper use of color example

<A HREF="http://www.Image_Used_As_Link.com"><IMG SRC="Images/ColorButton.gif" ALT="Improper use of color example" WIDTH="300" HEIGHT="40" BORDER="0"></A>

Result: A person who has trouble with yellows / greens might not see the text in this link.

Accessible Color Link

Contrasting use of color example

<A HREF="http://www.Image_Used_As_Link.com"><IMG SRC="Images/ContrastColorButton.gif" ALT="Contrasting use of color example" WIDTH="300" HEIGHT="40" BORDER="0"></A>

Result: Dark colors on light backgrounds or vice versa provide necessary contrast.

Non-Accessible Color Indicators

Note: This form denotes required fields with blue.

<LABEL FOR="name"><SPAN CLASS="LightBlue">Name:</SPAN> <INPUT TYPE="TEXT" ID="name"></LABEL>.....

Result: A person who is blind or has trouble with blues might not see the required fields.

Accessible Color Indicators

Note: This form denotes required fields with blue and asterisks.

<LABEL FOR="name"><SPAN CLASS="LightBlue">Name:</SPAN> <INPUT TYPE="TEXT" ID="name" VALUE="******"></LABEL>.....

Result: A person who is blind or has trouble with blues will see the required fields denoted with asterisks.

Automatic vs Manual: When using an accessibility program, the program might pick up that color is being used but it will not know the intent of the use. Consequently, a manual check on how the color is being used will need to be performed prior to passing or failing.


Style Sheets

1194.22 (d) Documents shall be organized so they are readable without requiring an associated style sheet.

Rationale: Style Sheets are a means to separate the presentation from the structural markup of a web site and screen readers read through the elements on a web page in the order in which they appear in the page code, regardless of how they are positioned using style sheets.

Accessible Style Sheet Layout

The left location of this information is being controlled by the style sheet. Visually, it will be read read first and will also be read first by a screen reader because it comes first in the HTML. Not because the style sheet places it on the left.

The right location of this information is being controlled by the style sheet. Visually, it will be read second and will also be read second by a screen reader because it comes second in the HTML. Not because the style sheet places it on the right.


HTML Code

<DIV ID="Left">
	<P>The right location of this information is being
	controlled by the style sheet. Visually, it will be
	read second and will also be read second by a screen
	reader because it comes second in the HTML. Not because
	the style sheet places it on the right.</P>
</DIV>
<DIV CLASS="right">
	<P>The right location of this information is being
	controlled by the style sheet. Visually, it will be
	read second and will also be read second by a screen
	reader because it comes second in the HTML. Not because
	the style sheet places it on the right.</P>
</DIV>

CSS Code

#Left {
	FLOAT: left;
	WIDTH: 40%;
	BORDER: 1px groove black;
	BACKGROUND-COLOR: #FFDDAA;
	PADDING: 5px; 
	}

.right {
	BORDER: 1px groove black;  
	BACKGROUND-COLOR: #D9C4AA;
	PADDING: 5px; 
	}

Result: A screen reader will read the left box first then the right because of the HTML code order.

Non-Accessible Style Sheet

Previously on the right in the accessible style sheet example, this information is now being told to be on the left by the style sheet. Visually, it will be read first but with a screen reader or style sheets turned off, will be read out of order (second) because it comes second in the HTML.


HTML Code

<DIV ID="Right">
	<P>Previously on the left in the accessible style sheet 
	example, this information is now told to be on the
	right by the style sheet. Visually, it will be read
	second but with a screen reader or style sheets turned
	off, will be read out of order (first) because it comes
	first in the HTML.</P>
</DIV>
<DIV CLASS="left">
	<P>Previously on the right in the accessible style sheet
	example, this information is now told to be on the
	left by the style sheet. Visually, it will be read
	first but with a screen reader or style sheets turned
	off, will be read out of order (second) because it comes
	second in the HTML.</P>
</DIV>

CSS Code

#Right {
	FLOAT: right;
	WIDTH: 40%;
	BORDER: 1px groove black;
	BACKGROUND-COLOR: #FFDDAA;
	PADDING: 5px; 
	}

.left {
	BORDER: 1px groove black;  
	BACKGROUND-COLOR: #D9C4AA;
	PADDING: 5px; 
	}

Result:

Automatic vs Manual: When using an accessibility program, external style sheets are typically ignored. However, user input on proper style sheet use through a manual check will be required prior to passing or failing. W3C's css-validator does provide assistance with checking properly coded style sheets.


Server-Side Image Maps

1194.22 (e) Redundant text links shall be provided for each active region of a server-side image map.

Rationale: Image maps provide different links for different areas of a map and server-side maps store link information in a location that is not accessible to adaptive technologies.

Accessible Server Side Site Map Example

Site map with alternative links provided

SIUC Home - About SIUC - Search SIUC - SIUC Facts - Public Events Calender

<A HREF=" ../imagemaps/SIUCheader_maroon.map"> ALT="Site map with alternative links provided"< IMG SRC=" ../images/SIUCheader_maroon.jpg" WIDTH="483" HEIGHT="110" BORDER="0" ISMAP="ISMAP">
< /A>

Result: Screen readers can not read server side links and areas of the map are not readily accessible without a mouse.

Automatic vs Manual: When using an accessibility program, the program is unable to determine if the text links are redundant copies of the server-side links. User input is required to ensure consistency.


Client-Side Image Maps

1194.22 (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Rationale: Just as images must have alternate text, each area of an image map must also have appropriate alternate text for use when the image is not displayed.

Accessible Client Side Site Map Example

Site map with regions alt tagged Public Events calanderSIUC FactsSearch SIUCAbout SIUCSIUC Link

<IMG SRC="Images/SIUCheader.bmp" ALIGN="TOP" ALT="Site map with regions alt tagged" < AREA SHAPE="RECT" COORDS="0,32,73,43" HREF="http://www.siuc.edu/aboutsiuc/" ALT="About SIUC" > BORDER="0" WIDTH="315" HEIGHT="70">:

Result: The site map has an alt text for identification, the areas have alt text for screen readers. Redundant links should be provided for text only browsing but are not required.




Automatic vs Manual: When using an accessibility program, detection of client-side image maps should be automatic. Ensure that the alt text used in the map is equivalet to the link information on the image.


Table Headers

1194.22 (g) Row and column headers shall be identified for data tables.

Rationale: A screen reader can use table headers to provide row and column information while a user accesses the data cells within a table.

  • Use TD elements for data cells
  • For simple tables use TH or THEAD elements to indicate headers
  • Use SCOPE and HEADER attributes to indicate relationships between headers and data cells
  • Define the CAPTION element to title the table
  • Use the SUMMARY attribute of the TABLE element to provide additional information on the purpose of the table in the document
  • Use AXIS attribute of TD and TH to indicate conceptual categories

Accessible Table using "Scope"

"Scope" must have one of the following values: "row", "col", "rowgroup", or "colgroup." Scope specifies the set of data cells to be associated with the current header cell. This method is particularly useful for simple tables. It should be noted that the spoken rendering of this table would be identical to that of the previous example. A choice between the "headers" and "scope" attributes is dependent on the complexity of the table. It does not affect the output so long as the relationships between header and data cells are made clear in the markup.

Student GPA Data
Year 4.0 3.9 - 3.0 2.9 - 2.0 1.9 - 1.0 0.9 - 0.0
Freshmen 26% 23% 31% 12% 8%
Sophmore 30% 25% 35% 7% 3%
Junior 33% 28% 34% 3% 2%
Senion 32% 33% 32% 2% 1%

<TABLE border="2"
  summary="This table charts student GPA data.">
  < CAPTION>Student GPA Data</CAPTION>
  < TR>
     <TH SCOPE="col">Year</TH>
     <TH SCOPE="col"> 4.0 </TH>
     <TH SCOPE="col"> 3.9 - 3.0 </TH>
     <TH SCOPE="col"> 2.9 - 2.0 </TH>
     <TH SCOPE="col"> 1.9 - 1.0 </TH>
     <TH SCOPE="col"> 0.9 - 0.0</TH>
  < /TR>
  < TR>
     <TH SCOPE="row">Freshmen>
    < TD>26%</TD>
    < TD>23%</TD>
    < TD>31%</TD>
    < TD>12%</TD>
    < TD>8%</TD>
  < /TR>....
< /TABLE>

Result: A speech synthesizer might render it by speaking the following:

Caption - Student GPA Data

Summary - This table charts student GPA data.

Year: Freshmen, 4.0: 26%, 3.9 - 3.0: 23%, 2.9 - 2.0: 31%, 1.9 - 1.0: 12%, 0.9 - 0.0: 8%

Year: Sophmore, 4.0: 30%, 3.9 - 3.0: 25%, 2.9 - 2.0: 35%, 1.9 - 1.0: 7%, 0.9 - 0.0: 3%

Year: Junior, 4.0: 33%, 3.9 - 3.0: 28%, 2.9 - 2.0: 34%, 1.9 - 1.0: 3%, 0.9 - 0.0: 2%

Year: Senior, 4.0: 32%, 3.9 - 3.0: 33%, 2.9 - 2.0: 32%, 1.9 - 1.0: 2%, 0.9 - 0.0: 1%

Accessible Table using "Headers"

The next example associates the same header (TH) and data (TD) cells as before, but this time uses the "headers" attribute rather than "scope". This example shows how to associate data cells (created with TD) with their corresponding headers by means of the "headers" attribute. The "headers" attribute specifies a list of header cells (row and column labels) associated with the current data cell. This requires each header cell to have an "id" attribute.

Student Data
Last Name GPA Major Full Time
Baggins 3.5 Chemistry No
Friday 2.5 Aviation Yes
Stocking 4.0 Undecided Yes

<TABLE border="2"
  summary="This table charts student data.">
  < CAPTION>Student Data</CAPTION>
  < TR>
     <TH ID="Last_Name"> Last Name </TH>
     <TH ID="GPA"> GPA </TH>
     <TH ID="Major"> Major </TH>
     <TH ID="Full_Time"> Full Time </TH>
  < /TR>
  < TR>
    < TD HEADERS="Last_Name">B. Baggins</TD>
    < TD HEADERS="GPA">3.5</TD>
    < TD HEADERS="Major">Chemistry</TD>
    < TD HEADERS="Full_Time">No</TD>
  < /TR>....
< /TABLE>

Result: A speech synthesizer might render it by speaking the following:

Caption - Student Data

Summary - This table charts student data.

Name - Baggins, GPA 3.5, Major Chemistry, Full time No

Name - Friday, GPA 2.5, Major Aviation, Full time Yes

Name - Stocking, GPA 4.0, Major Undecided, Full time Yes

Non-Accessible Table

Student Data
Last Name GPA Major Full Time
Baggins 3.5 Chemistry No
Friday 2.5 Aviation Yes
Stocking 4.0 Undecided Yes

<TABLE border="2"
  summary="This table charts student data.">
  < CAPTION>Student Data</CAPTION>
  < TR>
     <TD> Name </TD>
     <TD> GPA </TD>
     <TD> Major </TD>
     <TD> Full Time </TD>
  < /TR>
  < TR>
    < TD>B. Baggins</TD>
    < TD>3.5</TD>
    < TD>Chemistry</TD>
    < TD>No</TD>
  < /TR>....
< /TABLE>

Other resources: W3C Accessible Table Techniques

Automatic vs Manual: When using an accessibility program, associations between information will require a suer check becuase software is unable to determine if cells are truly header information or if relationships are correct.


Complex Tables

1194.22 (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Rationale: Without proper markup, complex data tables can be difficult to navigate and understand using a screen reader.

This is important to the computer's ability to speak the contents of a table using a speech synthesizer. Browsers and assistive technologies rely on structural markup such as headers to customize presentation to meet a user's needs. If there is more than one row or column of headers, a more extensive description of the relationship between cells helps the user understand the structure better (http://bobby.watchfire.com/bobby/html/en/gls/g250.html).

Accessible Complex Table Using "axis" Attribute

Funds Raised
Sales Charity Total
Fall - - -
Freshman 31.25 87.00 118.25
Sophmore 22.43 52.00 74.43
Spring - - -
Freshman 21.25 32.00 53.25
Sophmore 35.70 64.00 99.70
Totals 110.63 235.00 345.63

Result: A speech synthesizer might render it by speaking the following:

Funds Raised

Fall

Freshman - Sales: 31.25, Charity: 87.00, Total: 118.25

Sophmore - Sales: 22.43, Charity: 52.00, Total: 74.43

Alternatively, the user may be interested only in a particular column, and with the appropriate markup can instruct the speech synthesizer to read it as follows:

Charity - Fall - Freshman: 87.00 - Sophmore: 52.00

Charity - Spring - Freshman: 32.00 - Sophmore: 64.00

Complex Table HTML Code

<TABLE border="2" summary="complex table example">
  <CAPTION> Travel Expense Report </CAPTION>
  <TR>
    < TH></TH>
    <TH id="a2" axis="funds">Sales</TH>
    <TH id="a3" axis="funds">Charity</TH>
    <TH id="a4" axis="funds">Total</TH>
  </TR>
  <TR>
    < TH id="a6" axis="semester">Fall</TH>
    <TH></TH>
    <TH></TH>
    < TH></TH>
  </TR>
  < TR>
    < TD id="a7" axis="class">Freshman</TD>
    < TD headers="a6 a7 a2">31.25</TD>
    < TD headers="a6 a7 a3">87.00</TD>
    <TD headers="a6 a7 a4">118.25</TD>
  </TR>
  < TR>
    < TD id="a8" axis="class">Sophmore;/TD>
    <TD headers="a6 a8 a2">22.43</TD>
    <TD headers="a6 a8 a3">52.00</TD>
    < TD headers="a6 a8 a4">74.43</TD>
  < /TR>
  <TR>
    < TH id="a10" axis="semester">Spring</TH>
    < TH></TH>
    <TH></TH>
    <TH></TH>
  < /TR>
  <TR>
    <TD id="a11" axis="class">Freshman;/TD>
    <TD headers="a10 a11 a2">21.25</TD>
    < TD headers="a10 a11 a3">32.00</TD>
    <TD headers="a10 a11 a4">53.25</TD>
  </TR>
  <TR>
    <TD id="a12" axis="class">Sophmore</TD>
    <TD headers="a10 a12 a2">35.70</TD>
    <TD headers="a10 a12 a3">64.00</TD>
    <TD headers="a10 a12 a4">99.70</TD>
  </TR>
  <TR>
    <TH>Totals</TH>
    <TD>110.63</TD>
    <TD>235.00</TD>
    <TD>345.63</TD>
  </TR>
</TABLE>

Other resources: W3C Accessible Table Techniques

Automatic vs Manual: When using an accessibility program, associations between information will require a suer check becuase software is unable to determine if cells are truly header information or if relationships are correct.


Frames

1194.22 (i) Frames shall be titled with text that facilitates frame identification and navigation.

Rationale: Frames are typically used to display more than one web page and at times are used for layout. To navigate frames, adaptive technology users must know the intent of each frame.

Non-Accessible Frame

Frame Example with links in left frame and content in the right

HTML Code

<FRAMESET COLS="20%, 80%">
	<FRAME SRC="508Links.htm">***508Links Title Missing***
	<FRAME SRC="508Content.htm" TITLE="Content">
</FRAMESET> 

 

Result: In this example, a screen reader can not identify the purpose of the Link Frame located on the left.

Automatic vs Manual: When using an accessibility program, you will be prompted to title and label your frames with meaningful names. Be sure they convey the usage of the frames, like "navigation" and "content."


Flicker

1194.22 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Rationale: photosensitive epilepsy can be triggered by flickering content. Learning disabled or cognatively disabled users can be overly distracted or disrupted by blinking content.

This one is a judgement call. usually gif animation will cause flickering. Animated graphics, Flash, Java, <blink> tags, <marquee> tags, and other techniques are often used to create a variety of animated effects.

A flickering or flashing screen may cause seizures in users with photosensitive epilepsy and content developers should thus avoid causing the screen to flicker. Seizures can be triggered by flickering or flashing in the 4 to 59 flashes per second (Hertz) range with a peak sensitivity at 20 flashes per second as well as quick changes from dark to light (like strobe lights). (Quoted directly from W3C http://www.w3.org/TR/WAI-WEBCONTENT/wai-pageauth.html#gl-movement)

2 Flashes per second Flicker example100 Flashes per second Flicker example

Flashing elements are created with various programs and coding practices. From Flash, Java, <blink> tags, and <marquee> tags, to animated gifs and flashing banners. These practices and programs typically allow the creator to specify how many times the image will change or flash per second through duration / delay control in thousandths of a second increments.

flicker control example

To ensure that the object does not flash in a dangerous range, specify a duration of greater than 50 for each frame (50/100=.5 per sec, 1 sec / .5 per = 2 flashes per sec) or a value of 1 for each frame (1/100=.01 per sec, 1 sec / .01 = 100 flashes per sec). Any number between 1 and 50 can result in a dangerous range (2/100=.02, 1sec / .02 = 50 flashes per sec).

Result: Use of excessive flicker is not only distracing and generally shown to be ineffective, it can cause seizures in photosensitive epileptics.

Automatic vs Manual: When using an accessibility program, you will be asked about flicker whenever a gif is present.


Text Only Last Resort

1194.22 (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

Rationale: If text only is all that can be done to be accessible, then do it.

Given advances in accessibility techniques and assistive technologies, "text-only" sites are simply not necessary in most cases.

 

 

 

 

 

 

 

 

Automatic vs Manual: When using an accessibility program, you will always be given this option. It is generally not recommended.


Scripting

1194.22 (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

Rationale: Not all I/O devices can access elements contained in javaScript and not all browsers support javaScript.

Inaccessible Script

See a bad example of javaScript navigation menus here.

Accessible Alternative

 

Result: Screenreaders can not access elements that are contained in javaScript. Using a browser detection or using a <noscript> element can not be relied upon to solve the javaScript problem. Frequently disabled users layer assistive technology on top of common browsers such is Internet Explorer and have javascript enabled. Their assistive technology is simply unable to active the javascript behavior or follow links contained in the script.

Automatic vs Manual: Any script present on a web page will result in a user check warning. It is a good idea to include <noscript> tags, even though they can not be relied upon to solve all issues.


Applets and Plug-ins

1194.22 (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).

Rationale: Software that is required to access information must meet requirements of section 508 for sofware accessibility.

Plug-Ins

Section 508 covers much more that just web pages. Part 1194.22, which we are examining on this page, applies to web pages. 1194.21 applies to software. This rule simply means that if you have a link to a .PDF, a .DOC, a .XLS, a .PPT or any other file, the software that is used to manage the file must meet the specifications of 1194.21.

Additionally, be careful of using Java applets on pages. These are frequently very difficult if not impossible to make accessible for the same reasons that javaScript can be problematic.

Result: All the work in the world on web pages doesn't matter if all your content can't be read.

Automatic vs Manual: When using an accessibility program, your links to various file types will not always be flagged. Beware of linking to unusable file types or using inaccessible applets.

 


Forms

1194.22 (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Rationale: Forms can be difficult to understand and navigate easily with screen readers and keyboards.

Making Forms Accessible

Making forms as accessible as possible can involve a combination of the following. The need to undertake all these imporvments can be realtive to the type of form you are using.

Inaccessible:

First Name Last Name Email

Favorite Color
Red Yellow

Accessible:

Access keys

Personal Information



4. Favorite Color


Access Keys

P - Personal Information group
1 - first name
2 - last name
3 - email
4 - favorite color group
R - red
Y - yellow
B - blue

HTML Code

<FORM name="form2" method="post" action="someAction.cgi">
<FIELDSET accesskey="P">
<LEGEND><STRONG>P</STRONG>ersonal Information</LEGEND>

<P><LABEL for="label"><STRONG>1</STRONG>. First Name</LABEL>
<INPUT name="textfield2" type="text" id="label" accesskey="1" tabindex="10"
 value="Enter first name"><BR>

<LABEL for="label2"><STRONG>2</STRONG>. Last Name</LABEL>
<INPUT name="textfield3" type="text" id="label2" accesskey="2" tabindex="11"
 value="Enter last name"><BR>

<LABEL for="label3"><STRONG>3</STRONG>. Email</LABEL>
<INPUT name="textfield4" type="text" id="label3" accesskey="3" tabindex="13" 
value="Your email address"></P>

</FIELDSET>

<FIELDSET accesskey="4">
<LEGEND><STRONG>4</STRONG>. Favorite Color</LEGEND>

<P><INPUT type="radio" name="radiobutton" value="radiobutton" id="radiobutton" accesskey="R" tabindex="14">
<LABEL for="radiobutton"><STRONG>R</STRONG>ed</LABEL>

<INPUT type="radio" name="radiobutton" value="radiobutton" id="radio" accesskey="Y" tabindex="15">
<LABEL for="radio"><STRONG>Y</STRONG>ellow</LABEL>

<INPUT type="radio" name="radiobutton" value="radiobutton" id="radio2" accesskey="B" tabindex="16">
<LABEL for="radio2"><STRONG>B</STRONG>lue</LABEL></P>

<P><INPUT type="submit" name="Submit2" value="Submit" id="label4" tabindex="17"></P>
</FIELDSET>

</FORM>

Result: The use of all the points pertaining to forms help all users and make the form as accessible as possible and very well organized too.

Automatic vs Manual: When using an accessibility program, you will always be asked whether labels and form controls are placed properly. The software can not tell if the name label is next to the name box and so forth.


Skip Navigation

1194.22 (o) A method shall be provided that permits users to skip repetitive navigation links.

Rationale: Users with screen readers or who are keyboard bound will have to tab through or read through these links every time.

[skip navigation bar]

  Welcome | Support | Products | Services | About Us

The body of my page begins here.

Result: Users can skip past lengthy and essentially redundant information on all pages and get to the meat of a page.

Automatic vs Manual: When using an accessibility program, there will not always be a user check to see whether repetative naviagion links may be skipped. Be sure to check for this manually each time.


Timed Responses

1194.22 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Rationale: Users with mobility impairments may take much longer to complete tasks that able-bodied users.

Example: Online banking sessions are set to time out after a period of inactivity. This is to ensure the security of the customer, but could render it unusable to a disabled user if they were not able to click a simple button to extend the time.

Result: Users will have an equal opportunity to complete necessary tasks when given the opportunity to extend time.

Automatic vs Manual: When using an accessibility program, you will always be asked to check for a timed response.

 

 

 

 


Additional Contact Info:

Access Through Adaptive Computer
Technology And Website Design
IBHE-HECA Grant Project,
Access Through Adaptive Computer
Technology and Website Design
IBHE-HECA Grant Project
Woody Hall B-150
Carbondale, IL 62901
Mailcode 4705
DSSsiu@siu.edu
Ph:  (618) 453-5738
Fax: (618) 453-5700
TTY: (618) 453-2293
Updated: 7 November 2003
Crowell & Whitney
© 2003