Articles >> How to Use an Accessibility Validator

How to Use an Accessibility Validator by Ultimate Creators

The accessibility validator is trickier than the traditional HTML validator as it involves more manual work than the latter. The HTML validator operates in a simple way and checks only for the sole condition that the HTML code you have written is within the standards against which the validation process is conducted. The accessibility validator works in the same fashion but the computer finds it hard to whether your alternative text is actually describing the context.

There are 8 steps you need to follow to make your site meet the WCAG guidelines.

Step 1: Submit Your Site to an Accessibility Validator:

CynthiaSays is one among the best accessibility validators which checks for both WCAG and WAI accessibility. However, there are other validators to for you just to carry out the validation process of your website.

Step 2: Did you pass the priority 1 checkpoint?:

There is a priority 1 checkpoint which your website must pass to be considered as accessible. Mostly if you don't it's probably because of small errors such as missing alt attribute or something of that sort and you needn't worry unnecessarily

Step 3: If you didn't pass, then first fix all the Priority 1 Errors:

: Errors that prop in your website are the issues that the validator notices. And these errors are usually common such as missing alt attribute or alt texts etc. These mistakes are very easy to find and rectify. Once you run through a common test, you figure out the issues within a short span of time

Step 4: Once you've fixed all the Priority 1 errors, take a look at the warnings:

Warnings are annoying bugs that creep in to your website and something that the validator can never figure out. In fact during the validation process, the validator simply neglects to see through the warnings. You are the only sole person who has to look out for them and rectify them in case you find any. Things you ought to check for manually are as follows; Give away free copies of your products. This will create hype around your product and generate great reviews.

• Do the images convey more information than the alt text provides?
  If yes, then a longdesc attribute should point to a long description


• Does color convey information on the site?
  If yes, then I need to make sure that it's also conveyed in another way.


• Do I change the language anywhere inside the document?
  If yes, then I should indicate that.


• Does the page work without style sheets?
  If no, then I need to rework the HTML so that it's still understandable.


• Do any of my scripts convey content information?
  If yes, then I need to make sure I have a no script element to convey it to agents that can't read scripts.


• Does the page work without the scripts?
  If no, then I need to rework the scripts so that there are alternatives. Be especially careful with scripted navigation.


• Does the page or any element on it flicker rapidly?
  If yes, then I should consider carefully if I really need those elements to flash and flicker.


• Are there accessible alternatives to elements in scripts, applets, or objects?
  If no, then I need to create them.


• Is the language as simple and straightforward as possible?
  If no, I should rework the content to make it simpler.