A text equivalent for every non-text element shall be provided (e.g., via
“alt”, “longdesc”, or in element content).
|
Supported
|
We have supported the non text content with alt, title attributes to make our
content more descriptive and easier to read using screen readers or screen magnifiers.
|
|
Equivalent alternatives for any multimedia presentation shall be synchronized with
the presentation.
|
Supported
|
We use multimedia only if it was needed to insure the purpose of the topic is
well described and synchronized with the content.
|
|
Web pages shall be designed so that all information conveyed with color is also
available without color, for example from context or markup.
|
Supported
|
Our Content is easy to read and the content is display with black letters on a white
background.
The content's font size can be easely increased or decreased if the
user needs to do so.
|
|
Documents shall be organized so they are readable without requiring an associated
style sheet.
|
Supported
|
The Content is readable with out CSS file. However, although the web page will
lose it's interface design, the content will remain 100% readable.
|
|
Redundant text links shall be provided for each active region of a server-side image
map.
|
N/A
|
-
|
|
Row and column headers shall be identified for data tables.
|
Supported
|
Each table has a Table Head and table body, that wraps the table rows and data.
|
|
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.
|
Supported
|
We have added scope attribute to support large tables for easier screen read.
|
|
Frames shall be titled with text that facilitates frame identification and navigation.
|
Supported
|
The only frame used in the website is titled and named.
|
|
Pages shall be designed to avoid causing the screen to flicker with a frequency
greater than 2 Hz and lower than 55 Hz.
|
Supported
|
The site has been designed to prevent screen flicker.
|
|
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.
|
Supported
|
We have supported any non-text with alt/title so it's more descriptive for
our users that uses screen readers.
|
|
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.
|
Supported
|
We have used safe and straight forward scripts that doesn't cause any confusion
or destruction to screen readers. We have also avoided nested scripts\inline
scripts in images.
|
|
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
|
Supported
|
We have added a reference link url to the required plug-ins in case the
plug-in is missing to ensure 100% deliverability.
|
|
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.
|
Supported
|
We have supported our onLine forms with AccessKey and TabIndex in all the required
fields to make it easy to use and to submit.
|
|
A method shall be provided that permits users to skip repetitive navigation links.
|
Supported
|
Users can in any time skip a task, Form, Content and move forward to get from
any page to any other page on the server. also the web server is organized
to give users an idea about where they are and where they are going.
|
|
When a timed response is required, the user shall be alerted and given sufficient
time to indicate more time is required.
|
N/A
|
-
|