|
Automatic-checked Errors
|
|
|
These are errors that can be defined unambiguosly by direct code check by an inspection software
Examples: images without alt attribute, script without corresponding noscript
|
|
|
Manual checks
|
|
|
These are potential errors, but this can only be determined by human criteria, thus the developer, auditor or user should determine wheter an error exists
Examples:
- table requires a full description at HTML level regarding it contens and structure, but inly if they are used to display an actual data table, not when they are use just for layout.
- if an image is of such complexity that needs more description information in addition to the alt text in the form of an specific linked file.
- if a change in text color has informational meaning other than aesthetical.
- if the page is still accessible and readable when the references to styles and stylesheets are removed.
|
|
|
Correcting in HTML
|
|
|
If the source file for the webpage is plain HTML the correction is straightforward and can be performed automaticaly by software like A-Prompt.
|
|
|
Correcting in programmed webpages
|
|
|
If the source file for the webpage is a programmed page (ASP, CF, PHP) automatic tools as A-Promt that repair only final HTML are not directly aplicable.
The final HTML can be produced in many different ways and coding styles in the programming language, then is practically impossible to apply automatic corrections.
The correction process require more patiente. Usually you access the webpage with the browser, save the HTML for it, and run a checking software over the HTML file.
The errors discovered here are a clue to search in the programmed page for the source of the wrong HTML.
|
|
|
Programmatic solutions and limitations to corrections
|
|
|
Sometimes the programmatic solutions generate HTML/JS code propietary, to which the developer has no access.
In CF is the case of the tags CFFORM that provides fields validation without coding.
In fact, CF creates the JS validation functions. This SCRIPTs have not the corresponding NOSCRIPT, and is not possible to manually correct it if the CFFORM tag is used.
The only workaround this, is to prescind of the CFFORM and write the validation functions manually.
The CFFORM can be used one time as developing tool to produce complete HTML with validations, then this HTML should be used in the fimal programmed page.
In this way access is gain to add NOSCRIPTs or other required corrections.
|
|
|
|
|
|