|
|
| About site: Internet/Web Design and Development/Authoring/Online Tools/Checking and Debugging/Accessibility - Erigami Accessibility and Quality Validation Tool |
Return to Computers also Computers |
| About site: http://checkwebsite.erigami.com/accessibility.html |
Title: Internet/Web Design and Development/Authoring/Online Tools/Checking and Debugging/Accessibility - Erigami Accessibility and Quality Validation Tool Checks web page accessibility on compliance with WCAG and Section 508, including automatic color contrast validation of text elements. It shows issues on a web page screenshot, measures response and d |
| Alexa statistic for http://checkwebsite.erigami.com/accessibility.html |
Please visit: http://checkwebsite.erigami.com/accessibility.html
|
| Related sites for http://checkwebsite.erigami.com/accessibility.html |
| The_Mlvwm_+_Kfm_Site How to create a mac-like desktop in linux. | | MKS_Software Provider of Windows automation tools for system administration and development in a pure Windows or mixed UNIX/Linux and Windows environment. | | Digital_Imagination Specializing in Internet, CD-ROM and video production. | | Macintosh_User_Group_for_Seniors Sharing Macintosh information to members age 55 and better. | | Entomo Offers Web-based transaction, collaboration, data mining, analytics, and supplier performance management products to manufacturers, distributors, and their direct materials suppliers. | | Old_Stone Full service shop featuring 3D Lenticular imaging and printing, large format, and digital design and output. | | Quantum_Technologies Printer maintenance and printer service for office printers. | | Sofotex_com Download free top shareware and freeware. Many different categories to browse. | | Courses_for_free A database of direct links to free online training courses including programming, operating systems, office applications, graphics and internet. | | Perl/Tk_FAQ This compilation of Frequently Asked Questions and answers (FAQ) is intended to answer several of the first (and largely more basic) questions posted to the comp.lang.perl.tk newsgroup and the ptk mai | | Antenna_House_XSL_Formatter An XSL-FO processor for Windows [Commercial]. | | Home_Builders_Software Estimating and accounting software for todays homebuilders or remodelers. Simple to use and easy to learn. Interfaces with Quickbooks or Quickbooks Pro. | | AUTOS2000 Offers automotive software shop management software. Includes FAQ and product features. | | PeopleSoft-L_Technical_Discussion The PEOPLESOFT-L mail list is for the technical and functional discussion of PeopleSoft applications. | | Libero By iMatix Corp. Write top-level logic as readable state diagram and click. Libero generates: Assembler, C, C++, Java, VB, Unix shells, Perl, Awk, PL/SQL, PHP, and COBOL. Template-based code generator | | Open64 Suite of optimizing compiler development tools for Intel Itanium(TM) systems running Linux. The Open64 project is the continuation of the SGI Pro64(TM) compiler suite which was released under the GNU | | RFC_2542 Terminology and Goals for Internet Fax. L. Masinter. March 1999. | | 32_Studios Offers web design and development. Provides Flash design, graphic design, JavaScript, ASP, CGI, and HTML. | | Disk_Doctors_Windows_Data_Recovery_is Provides data recovery software for recovering data from deleted and formatted files, formatted and corrupted drives. | | Proxy-Pro_GateKeeper Complete Internet Sharing solution for business and corporate use, allows company's network to access the Internet using a single Internet account, while also providing a high level of security and co |
|
This is websites2007.org cache of m/ as retrieved on 2008.09.07 websites2007.org's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.
|
Truwex Online, Web Accessibility Testing Tool: WCAG, Section 508 compliance
fieldset
{
border: 0;
margin: 0;
padding: 0;
}
legend
{
position: absolute; width: 0; height: 0; font-size: 0; overflow: hidden;
}
JavaScript must be enabled to use Truwex website accessibility validation tool

Erigami Home
Accessibility Check
BITV Check
Google Analytics Check
Help
Contacts
Truwex manages website compliance with web accessibility, online privacy, and quality standards. Truwex is a web governance and testing solution, all in one product.
Web compliance managers can use Truwex to:
Define a uniform website standard.
Monitor compliance status and automatically generate reports for upper management.
Set action items for website owners and web developers.
Web developers can use Truwex to:
Automatically test new web pages against a required web standard.
Detect issues on a website and use detailed Truwex diagnostics to fix them.
Supported web standards and validations: US ADA Section 508, WCAG 1 for UK DDA and German BITV, web analytics validation, COPPA and PII, website visibility in search engines, any custom web standard including crawling AJAX web sites.
Web site accessibility check
Page URL:
* URL is missing * URL is incorrect
Accessibility
Accessibility
Section 508
WCAG 1.0, Level A
WCAG 1.0, Level AA
Report warnings
WCAG 1.0 Color contrast formula
WCAG 2.0 Color contrast formula
Accessibility issues from 508 (A) to 508 (F)
[508 (A)] [WCAG 1.1 (1)] Alt is missing
Error
Warning
[508 (A)] [WCAG 1.1 (1)] Object without alternative inner text
Error
Warning
[508 (A)] [WCAG 1.1 (1)] Clickable image without alt
Error
Warning
[508 (A)] [WCAG 1.1 (1)] Bad alt text
Error
Warning
[508 (A)] [WCAG 1.1 (1)] Alt exists, but empty
Error
Warning
[508 (B)] [WCAG 1.4 (1)] Multimedia presentation and its equivalent alternatives must be synchronized
Error
Warning
[508 (C)] [WCAG 2.1 (1)] The use of color must not be a single method for indicating important information on a web page
Error
Warning
[508 (D)] [WCAG 6.1 (1)] Documents must be organized so they are readable without requiring user agent support for style sheets
Error
Warning
[508 (E)] [WCAG 1.2 (1)] For server-side image map regions redundant text links must be provided
Error
Warning
[508 (F)] [WCAG 9.1 (1)] Server-side image map is found
Error
Warning
Accessibility issues from 508 (G) to 508 (N)
[508 (G),(H)] [WCAG 5.1,5.2 (1)] Data table without headers is found
Error
Warning
[508 (I)] [WCAG 12.1 (1)] Frame has no title
Error
Warning
[508 (I)] [WCAG 12.1 (1)] Frames with the same title are found
Error
Warning
[508 (J)] Flicker rate must be in the specified limits
Error
Warning
[508 (K)] [WCAG 11.4 (1)] Text-only web page shall only be provided as a last resort method
Error
Warning
[508 (L)] Clickable image with javascript link has no 'alt' or 'title'
Error
Warning
[508 (M)] Link to plug-in used by page must be provided
Error
Warning
[508 (N)] [WCAG 12.3 (2)] Long list of form controls without grouping is found
Error
Warning
[508 (N)] [WCAG 12.3 (2)] Long list of options without grouping is found
Error
Warning
[508 (N)] [WCAG 12.4 (2)] Form control without explicit label is found
Error
Warning
Accessibility issues from 508 (O) to WCAG 3.2
[508 (O)] [WCAG 13.6 (3)] Page without skip link
Error
Warning
[508 (P)] Page requiring timed response must allow user to get more time
Error
Warning
[WCAG 1.1,6.3 (1)] NOSCRIPT tag is required on a page
Error
Warning
[WCAG 1.3 (1)] Multimedia presentation requires auditory description
Error
Warning
[WCAG 2.2 (2)] Low-contrast text is found
Error
Warning
[WCAG 2.2 (2)] Images must have sufficient contrast
Error
Warning
[WCAG 3.1 (2)] Use markup instead of images where possible
Error
Warning
[WCAG 3.2 (2)] Doctype missing
Error
Warning
[WCAG 3.2 (2)] Document must be valid
Error
Warning
Accessibility issues from WCAG 3.3 to WCAG 4.3
[WCAG 3.3 (2)] Use style sheets to control layout and presentation
Error
Warning
[WCAG 3.3, 3.5 (2)] Do not use headers and other structural markup only for visual effects
Error
Warning
[WCAG 3.4 (2)] Fixed sizes are found
Error
Warning
[WCAG 3.4 (2)] Fixed fonts are found
Error
Warning
[WCAG 3.5, 12.3 (2)] Hardly reachable text for voice reader is found
Error
Warning
[WCAG 3.5 (2)] Use header elements to convey document structure
Error
Warning
[WCAG 3.6 (2)] Mark up lists
Error
Warning
[WCAG 3.7 (2)] Mark up quotations
Error
Warning
[WCAG 4.1 (1)] Changes in the natural language must be clearly identified
Error
Warning
[WCAG 4.3 (3)] Document language markup is missing
Error
Warning
Accessibility issues from WCAG 5.3 to WCAG 7.4
[WCAG 5.3 (2)] Do not use tables for layout if they can not be linearized properly
Error
Warning
[WCAG 5.4 (2)] Do not use data table markup for layout tables
Error
Warning
[WCAG 6.2 (1)] Equivalents for dynamic content must be updated when the dynamic content changes
Error
Warning
[WCAG 6.3 (1), 6.5 (2)] Script based link is found
Error
Warning
[WCAG 6.4, 9.3 (2)] Device-dependent event handler is found
Error
Warning
[WCAG 6.4 (2)] If objects use event handlers, they must be accessible without a mouse too
Error
Warning
[WCAG 6.5 (2)] Noframe for frameset required
Error
Warning
[WCAG 7.1 (1); 7.2, 7.3 (2)] Blink text is found
Error
Warning
[WCAG 7.1 (1), 7.2, 7.3 (2)] Avoid flickering, blinking and movement in pages
Error
Warning
[WCAG 7.4, 7.5 (2)] Refresh meta is found
Error
Warning
Accessibility issues from WCAG 8.1 to WCAG 12.2
[WCAG 8.1 (1)] Programmatic elements must be directly accessible
Error
Warning
[WCAG 9.2 (2)] Object interface must be accessible without a mouse too
Error
Warning
[WCAG 9.3 (2)] Inaccessible select menu
Error
Warning
[WCAG 10.1 (2)] New browser window is detected
Error
Warning
[WCAG 10.1 (2)] Popup dialog window is detected
Error
Warning
[WCAG 10.2 (2)] Implicit labels must be properly positioned
Error
Warning
[WCAG 11.1 (2)] Use the latest W3C technologies available whenever possible
Error
Warning
[WCAG 11.2 (2)] Avoid deprecated language features
Error
Warning
[WCAG 12.2 (2)] Provide additional information for framesets
Error
Warning
Accessibility issues from WCAG 13.1 to end
[WCAG 13.1 (2)] Link name/destination clash
Error
Warning
[WCAG 13.1 (2)] Non-meaningful link name is found
Error
Warning
[WCAG 13.2 (2)] Metadata are missing
Error
Warning
[WCAG 13.3,13.4 (2)] Provide clear and consistent navigation
Error
Warning
[WCAG 14.1 (1)] The clearest and simplest language must be used
Error
Warning
[WCAG 14.3 (3)] Inline styles are found
Error
Warning
[WCAG-2 1.4 (2)] Low luminosity contrast text is found
Error
Warning
Frame is detected
Error
Warning
Privacy issues
Privacy
General privacy issues
Privacy policy link is missing
Error
Warning
Web beacon with cookies is found
Error
Warning
Web beacon without cookies is found
Error
Warning
Third-party cookies are found
Error
Warning
Third party links are found
Error
Warning
Long-life persistent cookie is found
Error
Warning
Cookie restricted by IE is found
Error
Warning
Cookie blocked by IE is found
Error
Warning
Mailto link is used
Error
Warning
Form with method GET is used
Error
Warning
Privacy issues: P3P and PII (begin)
P3P policy reference file is missing
Error
Warning
P3P policyref must be in double quotes
Error
Warning
P3P compact policy must be in double quotes
Error
Warning
PII: Page collects PII
Error
Warning
PII: Page collects age data
Error
Warning
PII: Page collects age revealing information
Error
Warning
PII: Page collects PII and opt-in/opt-out inputs are missing
Error
Warning
PII: Page collects PII and has prechecked opt-in/opt-out inputs
Error
Warning
Privacy issues: PII (end)
PII: COPPA: Page collects PII and contains inputs collecting forbidden PII
Error
Warning
PII: COPPA: Page collects PII and does not ask parent email
Error
Warning
PII: COPPA: Page collects PII and has no kids privacy policy link
Error
Warning
PII: No COPPA: Page collects PII and age data
Error
Warning
PII: No COPPA: Page collects PII and age revealing information
Error
Warning
PII: No COPPA: Page collects PII and is oriented towards children
Error
Warning
PII: No COPPA: Page collects PII and contains disclaimers
Error
Warning
PII: No COPPA: Page collects PII and does not contain disclaimers
Error
Warning
Web site quality issues
Web site quality
Meta data issues
HTML title: missing
Error
Warning
HTML keywords: missing
Error
Warning
HTML keywords: default value
Error
Warning
HTML keywords: repetitive
Error
Warning
HTML description: missing
Error
Warning
HTML description: default value
Error
Warning
HTML character set: missing
Error
Warning
Broken links are found
Error
Warning
Other web site quality issues
Broken source URLs are found
Error
Warning
Broken anchors are found
Error
Warning
Page not found
Error
Warning
Page not accessible
Error
Warning
Old pages found
Error
Warning
Script error popup is detected
Error
Warning
Interactive behavior issues
Interactive behavior
New browser window is detected
Error
Warning
Popup dialog window is detected
Error
Warning
Check broken links
Essential steps for designing an accessible web site
This guide outlines some simple steps that will help make your website accessible to disabled users. Website accessibility is not rocket science. Most methods for designing an accessible website are already familiar to most developers. This guide is meant only as a brief outline. It is interesting to note that many accessibility techniques are very similar to search engine optimization methods. In recognition of this, Truwex links together web site accessibility and SEO where it works.
There is a fundamental difference between the way that blind users and sighted users browse the internet. A sighted user can look at any place on a page and move a mouse pointer there almost instantly. In contrast, a blind user must wait for his screen reader to reach the desired place in a website which takes much more time. The task of a web designer is to help disabled users to identify and to read any desired content on a web page within a reasonable amount of time. To see how easily your website can be accessed by a blind user, start by checking your web page with the Truwex Online Validator.
Truwex can check your entire website
Truwex Factsheet
Download Truwex 2.0 Trial version
Buy Truwex SMB for only $390
Truwex Screenshots
Partnership and Reseller Opportunities with Erigami
Truwex Home
User testimonials
"A very impressive and free automated accessibility checking tool. In addition to the usual text display of issues with links to the relevant accessibility standards, it displays the checked page with highlighted areas for each of the reported issues."
- Kevin Yank, SitePoint.com
"It offers much finer-grained accessibility testing than anything I've used up to this point. I was able to find some nagging accessibility issues with my own site and will refer to it with all new development going forward."
- Trevor Pierce
Read more testimonials and publications about Truwex
Basic Web Site Accessibility Principles:
Keep your web page HTML code simple
Avoid overusing JavaScripts. Consider revising scripts which change web page content following a user action.
Convey text information using text, not images.
Make hyperlink text self-explanatory.
If you do use Flash, read and use the Adobe Flash accessibility guidelines to make it accessible.
Alternative Comments to all Images
Always insert alternative comments with all images and objects (this should be requirement number one for all developers looking to follow web accessibility standards). To comply with this, simply explain your image content in an ALT attribute. And if an image is clickable, explain the purpose of the target page in addition to the image content. If an image does not convey any valuable information and is used solely for design purposes, you can leave the ALT attribute empty, but keep it on the page! Missing ALT attributes is not an accessible practice.
Remember: search engines index ALT attributes. They pay great attention to clickable images where ALT serves as hyperlink text. Providing precise, but well explained alternative comments will help disabled people to understand your web page and increase its visibility to search engines.
Examples:
Empty ALT attribute for design image: <img src="http://checkwebsite.erigami.com/accessibility.html/spacer.gif" width="1" height="20" border="0" alt="" />
ALT attribute for logo image:
<img src="http://checkwebsite.erigami.com/accessibility.html/logo.gif" width="110" height="70" border="0" alt="Erigami company logo" />
ATL attribute to image with a hyperlink:
<a href="http://checkwebsite.erigami.com//projects.html"><img
src="http://checkwebsite.erigami.com/accessibility.html/promo.gif" width="200" height="70" border="0"
alt="Erigami projects description" /></a>
Accessible Hyperlink Names
Provide clear names for all links in your website (hyperlink text should describe the web page you reference). Remember: "Click here" is always a bad choice for a hyperlink name. Disabled users can review a list of all links on a web page, clear text helps them to navigate to a desired link without having to crawl over the entire web page. Clear link text also raises your visibility to search engines. If your link titles correspond with the topics of your referenced page, it will positively affect your page's position with search engines.
Accessibility Testing Using the Tab Key
The simplest method to test accessibility is to use the tab key on a PC keyboard. Every time you press Tab, a browser selects an HTML object on a web page. Both IE and FireFox highlight it using a dotted line. Try to make sure that all important content on your web page can be reached using only the tab key. When doing a "Tab key test," consider two things:
Is it possible to reach the main part of your web page? If not, your web page is not accessible.
Example: Custom controls and expanding content
<img onclick="javascript:return MyExpand();" style="cursor:hand"
src="http://checkwebsite.erigami.com/accessibility.html/images/plus.gif" id="adetails" alt="expand button" />
<div style="display:none" id="ddetails">
[Large fragment of text with important details here]
</div>
The content in DIV tag is hidden initially. A web page visitor can see it only after pressing "Expand" button. However this hidden content is not accessible to keyboard users in IE. The accessibility problem occurs because the button uses device-dependent (mouse dependent in this case) event handler OnClick, and more over it is not even a tab stop, i.e. it is not possible to set an input focus on this button using a keyboard. One possible solution consists in fixing the clickable image:
<a href="javascript:return" MyExpand();" style="cursor:hand"
title="This link will expand or collapse details description"><img
src="http://checkwebsite.erigami.com/accessibility.html/images/plus.gif" id="adetails" alt="Expand button" /></a>
<div style="display:none" id="ddetails">
[Large fragment of text with important details here]
</div>
How many clicks are necessary to reach the main content? If your hand is tired from pressing Tab, you should consider adding a skip link to your web page.
Skip Link
The purpose of a skip link is to provide a quick access to web page content. As we discussed above, a user of assistive technologies reaches web page content step by step. From the Tab test it is clear that this process might take a long time. A major obstacle is the website menu, which repeats on every page of a website with only minor variations. Imagine if every time a visitor opened a web page she had to make 20 steps to start reading. The solution to this problem is a skip link. Skip links provide a way to bypass repetitive navigation menus and jump instantly to the main content.
<a href="http://checkwebsite.erigami.com/accessibility.html/#jumptocontent"><img
src="http://checkwebsite.erigami.com/accessibility.html/spacer.gif" width="1" height="1" alt="Jump to content"></a>
...
<a name="jumptocontent"><img
src="http://checkwebsite.erigami.com/accessibility.html/spacer.gif" width="1" height="1" alt="Content starts here"></a>
Read advanced guide to skip links: by Jim Thatcher
Header Tags
Header tags play an important role in web page navigation. Use level one tags <h1> to highlight a web page head. Enclose section headers in second tier header tags <h2>. Use the lower level headers only when absolutely necessary. A user of assistive technologies can review these headers before reading a web page and jump to any of them. This is especially useful in cases of very long text. Search engines are also interested in header tags (1st and 2nd levels). When search engines evaluate your site, header text has more weight than normal text. Therefore good headers help increase visibility and relevance in search engine queries.
Option Lists
Option lists with many items cause huge problems for users of assistive tools. Remember that disabled users have to access each option consecutively. Therefore, to reach the last item on the list of options, a disabled user must wade through all the preceding items first. Suppose there are 200 countries in the registration form your website uses and the "United States" is somewhere towards the end. How would you like to wait for every option to be read to you before you could make the proper selection?
Solution: use an Optgroup element to split options in Select list into manageable groups.
<select name="countrySelect" >
<optgroup label="Countries from A through C">
<option>Afghanistan</option>
<option>Albania</option>
<option>Algeria</option>
...
</optgroup>
<optgroup label="Countries from D through F">
...
</optgroup>
...
</select>
Accessible Forms
Creating an accessible form means a web designer should explain the purpose of every input. Such a problem does not exist for normal users, they simply see text near the input. However this text might be placed far away from the input in the HTML code, confusing assistive reader technology. The best way to solve this problem is to include text descriptions for input using a <label> tag.
For example:
<label for="email">Enter e-mail address:</label>
<input type="text" name="textbox" id="email"/>
There is an easy way to check if a label is used on a web form: click on text description for input. If the cursor jumps to this input, the <label> tag exists. Use of this tag makes your site more convenient for all users.
An alternative way to provide accessibility to forms is by using a TITLE attribute.
<input type="text" name="query" title="Enter your search criteria" />
Do not forget to use alt text for image buttons:
<input type="image" name="Submit" src="http://checkwebsite.erigami.com/accessibility.html/arrow.gif" alt="Begin your search" />
Layout and Content Tables
There are two main purposes of tables in a web site's design: (1) a table arranges serial data in rows and columns; and (2) a table defines a web page layout. To provide maximum convenience for disabled users, these two types of tables should be treated in different ways.
Table for serial data
Specify column and row header cells in data tables by using a TH element with scope="col"/"row" attribute. Let's take for example a table with personal computer specifications:
<table>
<tr>
<th scope="col">Processor</th>
<th scope="col">Operation system</th>
<th scope="col">Memory</th>
</tr>
<tr>
<td>PC model data</td>
<td>PC model data </td>
</tr>
...
</table>
Do not use TH element or other data table markup (such as "summary" or "title" attribute, or Caption element) for layout tables.
Frames
We do not recommend using frames for websites. If a web page contains frames, it consists of several individual documents, which are displayed in one browser window. In general, several documents are more difficult to understand for the assistive technologies used by disabled users.
Frames are difficult to understand for search engines as well. The content of a web page with frames contains little information to index, just links to other documents. Having no content, a web page's ranking will then be decreased. The frame documents will be indexed separately, which will decrease their relevance and value as well.
Web Page Language
Indicate a page language for every web page. It is pretty simple, but helpful.
<html lang="ru">
Text Color Contrast
Using text with sufficient contrast is always good practice. For most people black text on a white background is the easiest to read. If you use other colors, use Truwex to check that your web page makes use of sufficient contrast and color combinations for maximum visibility.
Fixed Fonts
Just because you can read everything on your web page doesn't mean that others can too. Many of your users need larger font to view text. The ability to enlarge fonts will help senior visitors to read text without special assistive tools.
To follow this accessibility requirement a web developer must use relative fonts rather than absolute ones. A web developer should also define all styles in the CSS and do not use inline styles. A user of assistive tools can redefine the styles defined in CSS to read a web page without limitations.
Inaccessible example:
<span style="font-size: 8px">small text</span>
Accessible example:
<span class="small">small text</span>
where CSS declaration contains:
.small {font-size: 80%;}
© 2007 Erigami, Ltd.
Contacts
Privacy policy
_uacct = "UA-316455-1";
_udn="erigami.com";
urchinTracker();
|
|
| |
Checks | web | page | accessibility | on | compliance | with | WCAG | and | Section | 508, | including | automatic | color | contrast | validation | of | text | elements. | It | shows | issues | on | a | web | page | screenshot, | measures | response | and | d |
|
http://checkwebsite.erigami.com/accessibility.html
Erigami Accessibility and Quality Validation Tool 2008 September
dvd rental
dvd
Checks web page accessibility on compliance with WCAG and Section 508, including automatic color contrast validation of text elements. It shows issues on a web page screenshot, measures response and d
Rules
|
© 2008 Internet Explorer 5+ or Netscape 6+
|
|
Recommended Sites: 1.
Arts -
Business -
Computers -
Games -
Health -
Home -
Kids and Teens -
News -
Recreation -
Reference -
Regional -
Science -
Shopping -
Society -
Sports -
World
Miss Gallery
- Top Anime Hentai
- DVD rental by mail
- Personal Loans - Loans - Loan - Loans - Credit Cards
|