Skip Navigation Links
 Previous Screen  Go to "Page Samples"  Go to "Program Features"

Web Accessibility

CONTENTS
Introduction
Basic Design Checks
Language
Navigation
Images
Tables
Frames
Inline Frames
Forms
Scripting
US Government's Section 508
W3C's WCAG 1.0
Web Page Testing
Language Codes

In the interest of promoting Web Accessibility for all, the full content of Able Web Editor's Page Sample on the subject is included here.

Accessibility is the word used to describe how to make Web Pages accessible to people with disabilities. In some cases the law requires Web Pages to be Accessible, see Section 508. But the guidelines for Accessibility also provide an excellent way of evaluating the overall design of Web Pages and Web Sites.

AbleWebEditor.com's Other Resources includes Links to relevant Web Sites on the Internet including Web Page testing and Validation for Accessibility.

See also the description of how this Web Site and Able Web Editor are designed to comply with the needs of Web Accessibility.


page 2    Return to Previous Screen  Go to "Basic Design Checks"

Introduction

The variety of disablities ranges from people who cannot use a Mouse, to people with learning disabilites, to people who require the use of assistive technologies such as screen readers, text-to-speech Browsers, or head wands. It is estimated that 1 out of 5 people using the Internet have some form of disability including the ones shown below.

But the guidelines for Web Accessibilty actually provide the best approach for creating Web Pages for all Visitors, including those using new technologies such as automatic language translation or hand held devices with small screens.

This Web Page describes specific examples of how to make Web Pages Accessible. It also includes the US Government's Section 508 which requires government agencies and businesses providing services to the US Government to make their Web Sites Accessible. This Web Page concludes with an introduction to the W3C's Web Content Accessibilty Guidelines.

Return to Top


page 3    Return to Previous Screen  Go to "Language"

Basic Design Checks

The design checks for optimum Accessibility are also good guidelines for the design of Web Pages in general. Primarily Web Pages should be comprehensible as text only. People with impared vision can not scan a Web Page for relevant information. It must be read to them or enlarged in small sections. Also, not all Visitors can interact with Web Pages using a Mouse. Any interaction that requires a Mouse should have an alternate keyboard input. If a Visitor can not use a Mouse or the keyboard, assistive technologies can replicate keystrokes using techniques such as voice control.

Make content understandable.
Use the clearest and simplest language.
Start paragraphs with the main topic.
Use consistent page layouts.
Supplement text with graphics when they will aid comprehension.
( Reference: WCAG 1.0, Guideline 14 - Priority 1 )
Separate Structure from Presentation.
Use markup to indicate structure. For example, Headings should outline the content of the Web Page.
Use Style Sheets to indicate presentation ( appearance ). Content should be understandable when the Style Sheet is not used.
Use relative rather than absolute units of measurement.
( Reference: Section 508 §1194.22( d )
WCAG 1.0, Guidelines 3 and 6 - Priority 1 )
Do not rely on color alone.
Information conveyed with color should also be available without.
Ensure there is sufficient contrast between foreground and background colors.
If a foreground color is specified, provide a background color.
Content should be visable on a black and white screen.
Use numbers not names for colors.
( Reference: Section 508 §1194.22( c )
WCAG 1.0, Guideline 2 - Priority 1 )
Do not rely on specific hardware.
Do not depend on a Mouse.
Content should be visable on a small or low resolution screen.
Content should be clear as text only.
( Reference: WCAG 1.0, Guideline 9 - Priority 2 )
Do not use blinking, scrolling, or auto-updating of pages.
Do not use Images that flicker.
Do not use automatic text or Image scrolling.
Do not automatically refresh pages.
Do not redirect pages.
Do not change windows without informing the Visitor.
( Reference: Section 508 §1194.22( j )
WCAG 1.0, Guideline 7 - Priority 1 )
Avoid proprietary elements that require plugins.
( Reference: WCAG 1.0, Guideline 11 - Priority 2 )

Return to Top


page 4    Return to Previous Screen  Go to "Navigation"

Language

Text-to-Speech Browsers that speak multiple languages need to be informed of the language being used. This includes identifying the primary language of the Web Page in the <html> Tag and any changes of language using Inline Text Tags such as the <span> Tag. Languages are identified by a two letter code. For a list of available codes, see Language Codes.

Use the title Attribute to expand <abbr> and <acronym> Tags.

These techniques allow search engines to find key words and documents in a specified language.

Primary Language:   <html lang="en-us">
Language Changes:   <span lang="fr">
Abbreviations:   <abbr title=" Description ">
Acronym:   <acronym title=" Description ">

Reference: WCAG 1.0, Guideline 4 ( Priority 1 )

Return to Top


pages 5 to 6    Return to Previous Screen  Go to "Images"

Navigation

For Text-to-Speech Browsers, repetitive Navigation Links should be grouped and provided with a means for being bypassed. For people with physical limitations, Links should be provided with a keyboard alternative using the accesskey Attribute. The table below lists additional considerations.

Link Text should indicate purpose of the Link.
Use clear and concise language.
Do not use "Click Here" as Link Text.
Text-to-Speech Browsers preface Links by saying "Link."
Use Alt Text in Images used for Links.
Alt Text should indicate purpose of the Link.
When Images and text are both used for a Link, use null Alt Text in the Image, <img src="..." alt="" >.
Group repetitive Links.
Provide a logical Tab order through Links.
Separate grouped Links with spaces and a printable character.
Provide keyboard shortcuts using the accesskey Attribute.
Provide a Link to skip repetitive Links.
  1. Use a visible Text Link or
  2. Use an Image that is not visible or
  3. Use Link Text that is the same color as the background.
Links in Image Maps.
Do not use Server-Side Image Maps.
Provide redundant text Links for Client-Side Image Maps. 1
( Reference: Section 508 §1194.22( f )
WCAG 1.0, Guideline 9 - Priority 1 )

Reference: Section 508 §1194.22( o ) and
    WCAG 1.0, Guidelines 9 and 13 ( Priority 2 ).
    1 WCAG 1.0, Guideline 1.5 ( Priority 3 ).

Example

Shown below is the Source Listing for the Links at the top of this Web Page. "Skip.gif" is an invisible Image used at the beginning of the Links to allow Text-to-Speech Browser to skip to the page heading. Each Link has an Access Key assigned to it and the Links are separated by spaces and vertical bars.

 Skip Navigation Links HTML  |  CSS  |  Scripts  |  Apps  |  Glossary

Return to Top


page 7    Return to Previous Screen  Go to "Tables"

Images

Images and Image Maps need to have a text equivalent for Text-to-Speech Browsers. The text should describe the Image and its function when it is used as a Link such as, "Return to previous screen." This Image description is used by search robots to index pages on the Internet.

When the Image is easy to describe, the alt Attribute can be used. The text in this Attribute should be kept short, less than 150 characters or 10 to 12 words. If the Image is being used as a Link, the alt Attribute should be used to indicate the Link Destination. When an Image is used to add spacing on a Web Page, use a null value ( alt="" ). When an Image is used as a bullet or decorative Images, use an asterisk ( alt="*" ).

When the Image requires a more comprehensive description, both the alt and longdesc Attributes should be included. The longdesc Attribute is a Link to a text only Web Page that contains the long description of the Image. A D-Link should be included to duplicate this Link for Browsers that do not recognize the longdesc Attribute.

Alt Description:  <img alt=" Description ">
or:  <area alt=" Description ">
Long Description Link:  <img longdec="Address">
D-Link:  <a href="Address">D</a>
Image as Bullet:  <img src="Bullet.gif" alt=" * ">
Image as Spacer:  <img src="Spacer.gif" alt=" ">

Reference: Section 508 §1194.22( a ) and
    WCAG 1.0, Guideline 1.1 ( Priority 1 )

Example

Shown below is a Source Listing for an Image that has alt and longdesc Attributes and a D-Link.

<img src="Sales.gif"
    alt=" Chart illustrating sales figures for 2004 "
    longdesc="Sales-2004.html"
>
<a href="Sales-2004.html">D</a>

Return to Top


pages 8 to 11    Return to Previous Screen  Go to "Frames"

Tables

Tables can be used either for layout, Layout Tables, or to present tabular information, Data Tables. Data Tables can be either simple Tables with a single row or column of <th> Tags or complex Tables with two or more rows and/or columns of <th> Tags.

Tables present a special problem for Text-to-Speech Browsers because these Browsers read from left-to-right then top-to-bottom. Also Text-to-Speech Browsers can be used to move forward and back from one Cell to another. The problem becomes to identify which Heading Cell(s), <th>, apply to individual Data Cells, <td>. To resolve this problem, the HTML Standard added the headers and scope Attributes to relate Data Cells to specific Heading Cells. In addition, the summary, abbr, and axis Attributes have been added for descriptive text.

Return to Top

Layout Tables

Tables are useful for establishing the visual relationship between text and Images on a Web Page. For the most part, Browsers display these tables the same. Text-to-Speech Browsers read these tables from left-to-right and top-to-bottom. This is referred to as "Linearization." All of the information in one Cell is read before the Browser proceeds to the next Cell. The only guidelines to follow for Accessibility of Layout Tables is to verify that they are understandable when Linearized and do not use <th> Tags to create Cells.

Layout Tables
Verify the information is clear when it is Linearized.
Use only <td> to create Cells in Layout Tables.
Do not use <th> in Layout Tables.

Reference: WCAG 1.0, Guideline 5 ( Priority 2 )

Return to Top

Simple Data Tables

Simple Data Tables use a single row and/or column of <th> Tags for the Heading Cells. Within each <th> Tag, use the scope Attribute to specify whether the Heading Cell refers to rows or columns of Data Cells, <td>.

Tag   Relates To
<th scope="col">   <td> Cells in current Column
<th scope="row">   <td> Cells in current Row
<th scope="colgroup">   <td> Cells defined by <colgroup>
<th scope="rowgroup">   <td> Cells in <tbody>

Reference: Section 508 §1194.22( h ) and
    WCAG 1.0, Guideline 5 ( Priority 1 )

Example

The Table below is a Simple Table with two rows and two columns. The <th> Tags are the first Cell in each row and therefore create a column of Headings. They define the <td> Tags that follow in each row. Therefore, the scope Attributes use the value "row." Because this Table reads across the page, it Linearizes very well.

 Show Test Frame <table border="5" cellpadding="6"><tr>
    <th scope="row" align="right"> Keyboard: </th>
    <td> Ctrl+N </td>
</tr><tr>
    <th scope="row" align="right"> Menu Option: </th>
    <td> Source >> New </td>
</tr></table>
Keyboard: Ctrl+N
Menu Option: Source >> New

Linearized Table

Keyboard: Ctrl+N
Menu Option: Source >> New

Return to Top

Complex Data Tables

Complex Data Tables have Data Cells that are defined by two or more rows or columns of Heading Cells. To specify the relationship, each <th> Tag includes an unique name in the id Attribute. Each <td> Tag includes a headers Attribute that indicates the Heading Cells that apply to that particular Data Cell. The headers Attribute may specify mulitple names from the id Attributes with each name separated by a space.

Tag   Relates To
<td headers="th_id">   <th id="th_id">

Reference: Section 508 §1194.22( h ) and
    WCAG 1.0, Guideline 5 ( Priority 1 )

Example

The example below is not a complex Data Table because there is only one row and one column of Header Cells. However, it illustrates how to relate multiple Header Cells to Data Cells using the id and headers Attributes.

 Show Test Frame <table border="5" cellpadding="6"><tr>
    <th scope="col"> Function</th>
    <th id="col-1"> Filename</th>
    <th id="col-2"> Folder</th>
    <th id="col-3"> Subfolder</th>
</tr><tr>
    <th id="row-1" align="right"> Default Buttons: </th>
    <td headers="col-1 row-1 "> Button.but </td>
    <td headers="col-2 row-1 "> Program Folder </td>
    <td headers="col-3 row-1 "> Reference </td>
</tr><tr>
    <th id="row-2" align="right"> Optional Lists: </th>
    <td headers="col-1 row-2 "> *.but </td>
    <td headers="col-2 row-2 "> Program Folder </td>
    <td headers="col-3 row-2 "> Reference </td>
</tr></table>
Function Filename Folder Subfolder
Default Buttons: Button.but Program Folder Reference
Optional Lists: *.but Program Folder Reference

Return to Top

Descriptive Attributes

Attributes have added to the HTML standard to describe the content of Table Cells. However, Browsers and assistive technologies have not yet made use of these Attributes.

Table Summary:   <table summary=" Table Content ">
Header Content:   <th abbr=" Cell Content ">
or:   <td abbr=" Cell Content ">
Cell Category:   <td axis=" Cell Category ">
or:   <th axis=" Cell Category ">

Reference: WCAG 1.0, Guideline 5 ( Priority 3 )

Return to Top


page 12    Return to Previous Screen  Go to "Inline Frames"

Frames

Accessibility guidelines specify that Frames shall have titles that facilitate frame identification and navigation. Some assistive technologies use the name Attribute of the <frame> Tag to serve this function and others use the <title> Tag of the Web Page in the Frame. The best approach is to use meaningful name and title Attributes in the <frame> Tag and a meaningful <title> Element in all the Web Pages.

The HTML standard has added the longdesc Attribute to the <frame> Tag but it is currently not supported by assistive technologies. The <noframes> Tag should always be used to specify alternate information.

Title:   <frame title=" Description "> 1
Name:   <frame name="FrameName">
Long Description:   <frame longdesc="Address"> 2
No Frames:   <noframes> Alternate Content </noframes>

Reference: Section 508 §1194.22( i ) and
    1 WCAG 1.0, Guideline 12.1 ( Priority 1 )
    2 WCAG 1.0, Guideline 12.2 ( Priority 2 )

Example

<frameset cols=" 125, * ">
    <frame src="Content.html"
        name="Contents"
        title=" Contents Page "
>
    <frame src="FirstPage.html"
        name="Documents"
        title=" Documents "
        longdesc="Library.html"
>
    <noframes>
        <a href="HomePage.html">
            Alternate Home Page</a>
    </noframes>
</frameset>

Return to Top


page 13    Return to Previous Screen  Go to "Forms"

Inline Frames

Web Pages with Inline Frames should include meaningful name and title Attributes and alternate content between the Opening and Closing <iframe> Tags.

The HTML standard has added the longdesc Attribute to the <iframe> Tag but it is currently not supported by assistive technologies.

Title:   <iframe title=" Description "> 1
Name:   <iframe name="FrameName">
Long Description:   <iframe longdesc="Address"> 2
Inline Frames:   <iframe> Alternate Content </iframe>

Reference: Section 508 §1194.22( i ) and
    1 WCAG 1.0, Guideline 12.1 ( Priority 1 )
    2 WCAG 1.0, Guideline 12.2 ( Priority 2 )

Example

This is the beginning of the primary Web Page.
<iframe src="FirstPage.html" width="415" height="250"
    name="Documents"
    title=" Documents "
    longdesc="Iframe.html"
>
    Alternate content.
</iframe>
<br>This is the end of the primary Web Page.

Return to Top


page 14    Return to Previous Screen  Go to "Scripting"

Forms

To complete a Form the Visitor must know what information is required for each Form Element. For Text-to-Speech Browsers this can be accomplished by following the guidelines below.

  • Use a logical sequence for access when the Tab key is pressed. If necessary, use the tabindex Attribute.
  • For Text Boxes and Menus, place Labels to the left.
  • For Checkboxes and Radio Buttons, place Labels to the right.
  • To associate a Label with a Form Element, use the <label> Tag.
  • For <input> Form Elements that do not have a visual Label, use the title Attribute. 1
  • For complex Forms, to group similar Form Elements use <fieldset> and <legend> Tags.
  • When appropriate, include the accesskey Attribute.

Reference: Section 508 §1194.22( n ) and
    WCAG 1.0, Guidelines 10 and 12 ( Priority 2 ).
1 This is not included in the WCAG 1.0 Standard but it is supported by assistive technologies.

WCAG 1.0 Guideline 10.4 states "Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas." This Guideline no longer applies to current assistive technologies.

Return to Top


page 15    Return to Previous Screen  Go to "US Government's Section 508"

Scripting

Web Pages that rely on Scripting may not be Accessible for text only or Text-to-Speech Browsers

Do not rely on Scripting.
Ensure pages are usable when scripting is disabled.
Use <noscript>.
Do not use Javascript in the href Attributes of Links.
Event Handlers should be independent of the input device.
Make dynamic content accessible from an alternative page.

Reference: Section 508 §1194.22( l ) and
    WCAG 1.0, Guideline 6 ( Priority 1 ).

Return to Top


pages 16 to 17    Return to Previous Screen  Go to "W3C's WCAG 1.0"

US Government Section 508 §1194.22

The US Government has mandated that access to information technology is a civil right. The primary legislation addressing this issue for the Internet is Section 508 § 1194.22 The law prohibits federal agencies from developing, purchasing, using, or maintaining information technology that is inaccessible to persons with disabilities. States and other countries are adopting similar measures.

The 16 parts of Section 508 § 1194.22 are included below. Where appropriate, Links are included to the W3C's equivalent Guideline(s) and the topics that suggest how these issues may be addressed.

  1. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
    W3C.1  |  See: Images
  2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
    W3C.1  |  ( Multimedia )
  3. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
    W3C.2  |  See: Basic Design Checks
  4. Documents shall be organized so they are readable without requiring an associated style sheet.
    W3C.6  |  See: Basic Design Checks
  5. Redundant text links shall be provided for each active region of a server-side image map.
    W3C.1  |  ( Server-Side Check )
  6. 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.
    W3C.9  |  ( Server-Side Check )
  7. Row and column headers shall be identified for data tables.
    W3C.5  |  See: Tables
  8. 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.
    W3C.5  |  See: Tables
  9. Frames shall be titled with text that facilitates frame identification and navigation.
    W3C.12  |  See: Frames  |  Inline Frames
  10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
    W3C.7  |  See: Basic Design Checks
  11. 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.
    W3C.11
  12. 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.
    W3C.8  |  See: Scripting
  13. 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).
    W3C.8  |  ( Multimedia Check )
  14. 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.
    See: Forms
  15. A method shall be provided that permits users to skip repetitive navigation links.
    See: Navigation
  16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
    W3C.7  |  ( Server-Side Check )

Return to Top


pages 18 to 19    Return to Previous Screen  Go to "Web Page Testing"

W3C's Web Content Accessibility Guidelines 1.0

The organization responsible for creating standards for the Internet, the W3C, has created a Web Accessibility Initative ( WAI ) to address the issues of Accessibility. Their Web Content Accessibility Guidelines ( WCAG 1.0 ) specify three different Priorities. As the Checkpoints in each Priority are satisfied, the level of conformance increases from the lowest, Level "A," to the highest, Level "AAA." Logos are available to indicate the Level of conformance for each Web Page. The WCAG is not a law but rather series of Guidelines for Web Developers. For additional information including Links to the the full text of the Guidelines, see "Other Resources" at www.AbleWebEditor.com.

  1. A Web developer must satisfy this checkpoint ( Level "A" )
  2. A Web developer should satisfy this checkpoint ( Level "AA" )
  3. A Web developer may satisfy this checkpoint ( Level "AAA" )

Summary

Indicated below is a brief summary of the Guidelines. Each Guideline is divided into a series of Checkpoints. Each Checkpoint is assigned the appropriate Priority level. Fortunately there are Validation services that automate the verification process. Unfortunately some of the Guidleines are open to interpretation with each of the validation services offering a different interpretation. The summary below includes Links to the equivalent item in Section 508 and the topics that suggest how these issues may be addressed.

  1. Provide text equivalent content to auditory or visual content.
    508.a, 508.b, 508.e  |  See: Images
  2. Don't rely on color alone to convey information.
    508.c  |  See: Basic Design Checks
  3. Markup content so that Style Sheets may be used to control appearance. Including using relative units of measure where possible.
    See: Basic Design Checks
  4. Clarify language of Web Page.
    See: Basic Design Checks
  5. Create tables that can be translated by text-to-speech Browsers.
    508.g, 508.h  |  See: Tables
  6. Organize documents so they may be read without Style Sheets, Scripts turned off, and are not dependent on dynamic changes to content.
    508.d  |  See: Basic Design Checks
  7. Allow Visitor's to control time-sensitive changes. Do not use the Marquee Element.
    508.j, 508.p
  8. Make Elements such as Scripts and Applets accessible from assistive technologies.
    508.l, 508.m  |  See: Scripting
  9. Design for device-independence so that the Visitor does not have to rely solely on a mouse, keyboard, or pointing device.
    508.f  |  See: Basic Design Checks
  10. Use interim solutions for older Browsers and assitive technologies.
  11. Follow W3C guidelines and standards.
  12. Provide orientation and context information to explain complex pages and layouts.
    508.i
  13. Provide clear and consistent mechanisms for navigation.
    See: Navigation
  14. Ensure Web Pages are clear and simple.
    See: Basic Design Checks

Return to Top


page 20    Return to Previous Screen  Go to "Language Codes"

Web Page Testing

Web Page testing is an important part of any Web Site development process. Many of the tests below can be accomplished following the Step-by-Step Instructions and using the Links and resources in the Other Resources section of www.AbleWebEditor.com.

  • Use an automated Accessibility validation tool.
  • Validate HTML syntax.
  • Validate style sheets.
  • Use a text-only Browser .
  • Use multiple browsers, with:
    Images not loaded,
    Style Sheets disabled,
    JavaScript disabled,
    Frames disabled.
  • Use a Text-to-Speech Browser.
  • Use a small display.
  • Use spell and grammar checkers.
  • Review the document for clarity and simplicity.
  • Invite people with disabilities to review documents.

Return to Top


page 21 to 24    Return to Previous Screen  Return to Top

Language Codes

The two letter Language Codes listed here are specified in ISO 639.2 which is maintained by the Library of Congress.

Return to Top

A to C

Abkhazian ab Bambarabm Catalanca
Afaraa Bashkirba Chamorroch
Afrikaansaf Basqueeu Chechen ce
Akanak Belarusianbe Chichewany
Albaniansq Bengalibn Chinesezh
Amharicam Biharibh Church Slaviccu
Arabic ar Bislamabi Chuvashcv
Aragonesean Bosnianbs Cornishkw
Armenianhy Bretonbr Corsicanco
Assameseas Bulgarianbg Creecr
Avaricav Burmesemy Croatian hr
Avestanae

Czech cs
Aymaraay



Azerbaijaniaz



Return to Top

D to G

Danish da Faroesefo Gaelicgd
Divehidv Fijianfj Gallegan gl
Dutchnl Finnishfi Gandalg
Dzongkhadz Flemishnl Georgian ka


Frenchfr Germande
Englishen Frisianfy Greekel
Esperantoeo Fulahff Greenlandickl
Estonianet

Guarani gn
Eweee

Gujarati gu

Return to Top

H to K

Haitianht Icelandicis Kalaallisutkl
Hausa ha Idoio Kannadakn
Hebrew he Igboig Kanurikr
Herero hz Indonesianid Kashmiriks
Hindi hi Interlingua ia Kazakhkk
Hiri Motu ho Interlingueie Khmerkm
Hungarian hu Inuktitutiu Kikuyuki


Inupiaqik Kinyarwandarw


Irish ga Kirghizky


Italianit Komikv




Kongokg


Japaneseja Koreanko


Javanesejv Kuanyamakj




Kurdishku

Return to Top

L to N

Laolo Macedonianmk Nauruna
Latinla Malagasymg Navajonv
Latvianlv Malayms Ndebele, Southnr
Limburganli Malayalamml Ndebele, Northnd
Lingalaln Maltesemt Ndongang
Lithuanianlt Manx gv Nepaline
Luba-Katangalu Maorimi Norwegian no
Luxembourgishlb Marathimr



Marshallesemh



Moldavianmo



Mongolianmn

Return to Top

O to T

Occitan oc Samise Tahitianty
Ojibwaoj Samoan sm Tamilta
Oriyaor Sangosg Tagalogtl
Oromoom Sanskritsa Tajiktg
Ossetianos Sardiniansc Tatar tt


Serbiansr Telugute
Panjabipa Shonasn Thaith
Palipi Sichuan Yiii Tibetanbo
Persianfa Sindhisd Tigrinyati
Polish pl Sinhalesesi Tonga to
Portuguese pt Slovaksk Tsongats
Pushtops Sloveniansl Tswanatn


Somaliso Turkishtr
Quechuaqu Sothost Turkmentk


Spanishes Twitw
Raeto-Romancerm Sundanese su

Romanianro Swahilisw

Rundirn Swatiss

Russianru Swedishsv

Return to Top

U to Z

Uighurug Venda ve Xhosaxh
Ukrainianuk Vietnamesevi

Urduur Volapükvo Yiddishyi
Uzbekuz

Yorubayo


Walloonwa



Welshcy Zhuangza


Wolofwo Zuluzu

Return to Top


Copyright © 2004 by Donald H. McCunn