Quick jump to flag: 10 | 12 | 31 | 33 | 55 | 56 | 58 | 59 | 61 | 65 | 74 | 76 | 78 | 80 | 81 | 82 | 83 | 100 | 101 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 127 | 128 | 129 | 132 | 133

For the CSS flags (600-699), see the CSS Checker Flags topic.

NOTE: Many flags are being (and have been) phased out in favor of individual message control via the message ID feature. Other flags have been removed from use due to obsolescence.

The TNPL Scripts (programs) in the included configuration file (htmlvalV240.cfg) may act differently depending on what validator flags are set. This allows you to further customize the behavior and validation of CSS HTML Validator by toggling flags. Listed below are the effects that having certain flags set (or unset) will cause to documents being validated with the included configuration file.

Setting a flag usually causes certain messages, warnings, and/or errors to be enabled for display. Most of these messages, warnings, and errors begin with "[x]" where x is the validator flag that can be unchecked or checked in order to disable or enable the message, respectively. This lets you easily determine which flag you need to disable if you see a message that you do not want to be displayed during a validation. However, remember that when you uncheck a flag, you may be disabling multiple messages. Therefore, to determine most or all of the effects of disabling a specific flag, you can use the below information.

hmtoggle_plus1More Information about Flags

•Quick jump to unused flag: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 11 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 32 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 57 | 60 | 62 | 63 | 64 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 75 | 77 | 79 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 126 | 130 | 131 | 134 | 135

•If you only want to disable a single message or want to know more about disabling messages, then see the disabling messages help.

•Flags that are not listed are probably not used, depending on what configuration file you are using. Flags not listed may be used in future configuration files.

•If you're using a newer configuration file, then some flags may be used that are not documented here. If you are using an older configuration file, then some flags documented may not be used.

•In rare cases, the effects of some flags may also differ according to the edition and/or version of CSS HTML Validator being used (if so, then this will be noted in the flag's description).

•If you're writing your own TNPL scripts then you can use the unused flags for your own use. We recommend that you start at the highest unused flag number (i.e. 180) and work your way backward. This offers the best chance of avoiding conflicting flag problems with future versions of the configuration file that may make use of new flags.

Flag Descriptions

Flag 10

Displays a comment about how you can disable certain messages by unchecking validator flags. You will probably want to disable this message by unchecking flag 10. The reason for this message is to make you aware of how easy it is to disable messages that you may not want to see by disabling flags.

Flag 12

When unchecked, does not change the priority of HTML Validator before validating a document. This means that HTML Validator usually runs at normal priority. When checked, the priority will be set to low before each validation if HTML Validator believes that it is best that it should work in the background (for instance, when HTML Validator is run from command line parameters). This will more easily allow you to do work with other applications while CSS HTML Validator processes documents in the background.

Flag 31

•Displays a message if any of the following elements are contained within another tag of the same type: "abbr", "acronym", "b", "big", "cite", "code", "dfn", "em", "h1", "h2", "h3", "h4", "h5", "h6", "i", "kbd", "q", "s", "samp", "small", "strike", "strong", "sub", "sup", "tt", "u", "var". Example: "<b> Bold <b> Bold again </b></b>" would generate a message for the second "b" element.

•NOTE: "var" and "samp" generate warning messages by default, because these elements nested in themselves are more likely to be incorrect due to their semantics.

Flag 33

•Displays a message if certain attributes have values that have leading or trailing spaces, such as the "href", "name", and "target" attributes for "a", and the "src" attribute for "img".

Flag 55

•Displays a warning message if certain block-level elements are used within certain other block-level elements, like using "h2" or "ul" in a heading tag.

Flag 56

•Displays a warning message if a block-level element like "table" or <h1> is used within a "p" tag that has an explicitly end tag. To benefit from this checking and for good style, you should close your "p" tags.

Flag 58 (Uncheck for "errors only" mode)

Uncheck this flag to run the validation in "errors only" mode. In this mode, only errors are displayed and some "less important" errors may not be displayed, such as when an attribute value is not quoted. Use this mode to target the most significant errors.

Flag 59 (Uncheck for "errors and warnings only" mode)

Uncheck this flag to run the validation in "errors and warnings only" mode. In this mode, only errors and warnings are displayed and some "less important" errors and warnings may not be displayed. This mode is more thorough than "errors only" mode.

Flag 61

Checks the spelling of certain attribute values, like the values for the "alt" and "summary" attributes. The value for "content" is also checked for "meta" description tags. Spell checking must be enabled or this flag has no effect.

Flag 65 (Recognized DOCTYPEs)

•Checks the DOCTYPE against a list of recognized DOCTYPEs and generates a warning message if the DOCTYPE is not in the list. See also flag 78.

•Recognized DOCTYPEs are

•<!DOCTYPE HTML>

•<!DOCTYPE html>

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html401/strict.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html401/frameset.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/1998/REC-html40-19980424/strict.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN" "http://www.w3.org/TR/1998/REC-html40-19980424/frameset.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

•<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">

•<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.2//EN" "http://www.wapforum.org/DTD/wml12.dtd">

•<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.3//EN" "http://www.wapforum.org/DTD/wml13.dtd">

•<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD WML 2.0//EN" "http://www.wapforum.org/dtd/wml20.dtd">

•<!DOCTYPE HTML SYSTEM "about:legacy-compat">

•<!DOCTYPE html SYSTEM "about:legacy-compat">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/html401-rdfa-1.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa Lite 1.1//EN" "http://www.w3.org/MarkUp/DTD/html401-rdfalite11-1.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+ARIA 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-aria-1.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.1//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic11.dtd">

•If this flag is changed, then reload CSS HTML Validator (or the configuration) for it to take effect.

•When checking to see if a DOCTYPE is recognized, a case-sensitive compare is made.

•Multiple contiguous whitespace characters are changed to a single space character so that valid DOCTYPEs with multiple contiguous whitespace characters or line breaks can still match a recognized DOCTYPE.

•If a match is not found, then any even number of single quotes are converted to double quotes and the DOCTYPE is tested again.

•NOTE: A DOCTYPE may still be technically valid if it doesn't pass this test. If a valid DOCTYPE doesn't pass this test, then you can 1) format the DOCTYPE so that it matches one of the above (recommended), 2) ignore the warning, or 3) uncheck the flag so that the test is not performed.

•To add a new recognized DOCTYPE, go to the Configuration Editor (Pro and Enterprise editions only) and use the setValueString(3, DOCTYPEstring) function in the onConfigLoad() function (choose the Functions radio button in the Programs tab of the Configuration Editor and find the onConfigLoad() function). Do not include the '<' character at the beginning of the DOCTYPE or the '>' character at the end of the DOCTYPE. Example: setValueString(3, '!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"');

•W3C list of valid DTDs (new window).

IMPORTANT MESSAGE ABOUT ACCESSIBILITY STANDARDS AND GUIDELINES: CSS HTML Validator cannot and does not check for total accessibility compliance. There are many complex accessibility issues that can only be addressed by human judgment. It is the web developer's duty to ensure appropriate compliance. However, CSS HTML Validator is designed to help a web developer create or redesign documents so that they are compliant.
 
Section 508 accessibility links.

Flag 74

•Displays an error message when non-XHTML 1.1 elements are used in a XHTML 1.1 document.

•Some of the non-XHTML 1.1 elements that generate an error message when used are: "applet", "basefont", "bgsound", "center", "comment", "dir", "embed", "font", "frame", "frameset", "iframe", "ilayer", "isindex", "keygen", "layer", "listing", "marquee", "menu", "multicol", "nextid", "nobr", "noembed", "noframes", "nolayer", "plaintext", "s", "server", "sound", "spacer", "strike", "u", "wbr", "window", "wml", "xmp"

Flag 76

Similar to flag 74 but for strict HTML 4.0/4.01 documents.

Flag 78

•Adds DOCTYPEs with omitted URIs to the list of recognized DOCTYPEs. See also flag 65.

•Recognized DOCTYPEs added are

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

•<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">

•<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> (New v22.0211)

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

•<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">

•<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN">

•If this flag is changed, then reload CSS HTML Validator (or the configuration) for it to take effect.

Flag 80

•Displays an error message when certain non-XHTML 1.1 attributes are used with certain elements in a document that has an XHTML 1.1 DOCTYPE.

•"onafterprint", "onbeforecopy", "onbeforecut", "onbeforepaste", "onbeforeprint", "oncontextmenu", "oncopy", "oncut", "ondragstart", "onmouseenter", "onmouseleave", "onmousewheel", "onpaste", or "onselectstart" event attribute is used

•"name" used with the "a", "applet", "form", "frame", "iframe", "img", and "map" elements

•"target" used with the "a", "area", "base", "form", or "link" elements

•"align", "hspace", or "vspace" used with the "applet" element

•"align", "alink", "background", "bgproperties", "credit", "height", "leftmargin", "marginheight", "marginwidth", "nowrap", "instructions", "link", "logo", "scroll", "text", "topmargin", "vlink", "width" used with the "body" element

•"align" or "valign" used with the "caption" element

•"compact" used with the "dl" element

•"align", "color", "noshade", "size", or "width" used with the "hr" element

•"scroll" used with the "html" element

•"align", "border" used with the "img" element

•"hspace", or "vspace" used with the "img" element

•"align" used with the "legend" element

•"type", "value" used with the "li" element

•"align", "border", "hspace", or "vspace" used with the "object" element

•"compact", "start", or "type" used with the "ol" element

•"width" used with the "pre" element

•"align", "bgcolor", "bordercolor", "bordercolorlight", "bordercolordark", "height", "hspace", or "vspace" used with the "table" element

•"background", "bgcolor", "bordercolor", "bordercolorlight", "bordercolordark", "height", "nowrap", or "width" used with the "td" or "th" elements

•"background", "bgcolor", "bordercolor", "bordercolorlight", or "bordercolordark" used with the "tr" element

•"compact" or "type" used with the "ul" element

Flag 81

Similar to flag 80 but for strict HTML 4.0/4.01 documents.

Flag 82

Similar to flag 80 but for strict XHTML 1.0 documents.

Flag 83

Similar to flag 74 but for strict XHTML 1.0 documents.

Flag 100 (DOCTYPEs with relative URIs)

•Adds DOCTYPEs with relative URIs to the list of recognized DOCTYPEs. Relative URIs are not recommended so you may want to uncheck this flag. See also flag 65.

•Recognized DOCTYPEs added are

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">

•<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "DTD/xhtml1-frameset.dtd">

Flag 101

•Similar to flag 74 but for XHTML Basic 1.0 and XHTML Basic 1.1 documents.

Flag 112 (HTML Tidy)

Uncheck this flag to run the validation in "HTML Tidy messages only" mode. In this mode, only HTML Tidy messages are displayed. Using this mode will automatically enable the option to include HTML Tidy results in the validation, so it is not necessary that that option be enabled when in "HTML Tidy messages only" mode.

Flag 113 (Random Search Engine Tips)

Displays a randomly selected search engine tip. NOTE: General search engine messages must be enabled in the Validator Engine Options for this message to be generated.

Flag 115 (Nsgmls)

Uncheck this flag to run the validation in "Nsgmls messages only" mode. In this mode, only nsgmls messages are displayed (nsgmls is a DTD based validator). Using this mode will automatically enable the option to include nsgmls results in the validation, so it is not necessary that that option be enabled when in "Nsgmls  messages only" mode.

Flag 116 ("cf" elements)

Uncheck this flag to ignore elements that begin with "cf" and to display a message indicating how many "cf" elements were ignored (if more than 1). If working with CFML (ColdFusion Markup Language), then you may want to uncheck this flag.

Flag 117 (image dimension checking)

Checks image dimensions by comparing user specified "height" and "width" values to actual image dimensions where possible (these checks can only be made under certain circumstances).

NOTE: Image dimensions checks are only made when the needed information (the actual image dimensions) are immediately available. Because of this, any messages generated may not be generated on the first validation, but instead may be generated on subsequent validations after the link checker (which runs in the background after the validation is complete) has obtained the actual image dimensions.

Flag 118 (preceding and/or trailing whitespace in contained text checking)

Checks for preceding and trailing whitespace characters of the text content of certain elements like "a" and "title".

Disable this flag if you don't want to check for this and/or want a small performance improvement.

Flag 119 (duplicate control name checking in forms)

Checks for duplicate control name checking in forms. Disabling this flag is more efficient than disabling single messages using the message ID feature.

Flag 120 (XHTML Mobile DOCTYPEs)

•Adds XHTML Mobile DOCTYPEs to the list of recognized DOCTYPEs.

•Recognized DOCTYPEs added are

•<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" "http://www.wapforum.org/DTD/xhtml-mobile10.dtd">

•<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.1//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile11.dtd">

•<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.2//EN" "http://www.openmobilealliance.org/tech/DTD/xhtml-mobile12.dtd">

•Requires CSS HTML Validator Home/Pro DLL version 9.02 or higher to add these DOCTYPEs.

Flag 121 (HTML5 Obsolete Elements)

•For HTML 4 and older type documents, generates a warning message for elements that are considered entirely obsolete in HTML5 (like "acronym", "applet", "big", "center", "font", "s", "u", and more) to help authors develop more future compatible documents.

Flag 122 (HTML5 Obsolete Attributes)

•For HTML 4 and older type documents, generates a message for attributes that are considered obsolete or entirely obsolete in HTML5 to help authors develop more future compatible documents.

Flag 123 (General compatibility messages for HTML5)

Displays messages to help create documents that are compatible with more browsers. The messages under these flags are HTML5 specific.

•In some cases (like where compatibility may still be an issue) displays a general compatibility message if a new HTML5 attribute is used. Note: There are some exceptions for some attributes (like "async" and "sandbox" which are now widely supported) and attributes for which a more specific message should be generated.

•In some cases (like where compatibility may still be an issue) displays a general compatibility message if a new HTML5 attribute value is used.

Flag 124 (Random Accessibility Tips)

Displays a randomly selected accessibility tip. NOTE: Accessibility checking must be enabled in the Validator Engine Options for this message to be generated.

Flag 125 (Legacy ICRA label checking)

Uncheck this flag to enable legacy ICRA label checking. The ICRA labeling engine has been discontinued.

Flag 127 (Disable proprietary extension categories for HTML5 documents)

When an HTML5 DOCTYPE is encountered, obsolete proprietary browser extension categories are automatically disabled and deactivated so that the proprietary tags and attributes will generate errors.

Flag 128 (Omitted end tag messages)

Displays various "omitted end tag" messages when certain optional end tags are omitted (like "body", "li", "td", "th", etc)

Flag 129 (Warnings/errors for HTML5 attributes in non-HTML5 documents)

Displays warning messages (or error messages for standards-compliant validations) when HTML5 attributes are used in non-HTML5 documents (like in HTML 4.01 documents)

Flag 132 (Omitted start tag messages)

Displays various "omitted start tag" messages when certain optional start tags are omitted (like "colgroup", etc)

Flag 133 (Random Mobility Tips)

Displays a randomly selected mobility (mobile development messages) tip. NOTE: Mobile development messages must be enabled in the Validator Engine Options for this message to be generated.

Obsolete / Legacy Flags

Because many messages controlled by flags are obsolete and have been removed or replaced, and because the flag method of controlling message output is being phased out (in favor of the message ID feature), many flags are now considered obsolete and/or legacy and are no longer used. You can find most or all of these flags here.

hmtoggle_plus1Obsolete / Legacy flags

Flag 1 (Internet Explorer specific messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 2 (Netscape specific messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 3 (Deprecation messages)

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled by the message ID feature.

Flag 4 (Obsolete messages)

The elements listed here ("bq", "comment", "fn", "listing", "nextid", "note", "plaintext", and "xmp") were considered so obsolete that they were removed from the configuration file and are now treated as unrecognized elements.

Flag 5 (General compatibility messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 6 (Helpful tip messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 7 (Style messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 8 (Search engine messages)

This flag is no longer in use in v14.00+. The messages previously controlled by this flag are now controlled by the message ID feature and the option that enables search engine messages in the Validator Engine Options.

Flag 9 (More deprecation messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 11

This flag is no longer in use in v6.00+. To turn on or off sound, disable or enable sound in the Validator Engine Options.

Flag 13

This flag is no longer in use in v17.00+.

Flags 14, 15, 16, 17, 18

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 19 (Proprietary HTML editor attributes)

This flag is no longer in use in v22.00+. The messages previously controlled by this flag have been removed or are now controlled by the message ID feature.

Flag 20 (SMIL style messages)

This flag is no longer used because SMIL support is now considered obsolete.

Flag 21 (WebTV/MSN TV specific messages)

This flag is no longer used because WebTV/MSN TV support is now considered obsolete.

Flag 22

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 23 (WebTV/MSN TV Comments)

This flag is no longer used because WebTV/MSN TV support is now considered obsolete.

Flag 24

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flags 25, 26, 27

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 28

This flag is no longer in use in v14.00+.

Flag 29 is no longer used.

Flag 30

This flag is no longer in use in v14.00+.

Flag 32

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flags 34, 35

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 36

This flag is no longer in use in v20.02+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flags 37, 38, 39

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 40 is no longer used.

Flag 41

This flag is no longer in use in v8.00+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 42

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 43

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 44 is no longer used.

Flags 45, 46

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 47 (Using lists to indent)

This flag is no longer used because the incorrect use of the "li" element for indenting that was allowed by disabling this flag is no longer supported.

Flags 48, 49

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 50 is no longer used.

Flags 51, 52

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 53

This flag is no longer in use in v21.00+. The messages previously controlled by this flag are now controlled by the message ID feature.

Flag 54

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 57

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 60

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 62 (Netscape specific warning messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag are now controlled by the message ID feature.

Flag 63

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 64

This flag is no longer in use in v17.00+.

Flag 66, 67 (Accessibility)

These flags are no longer in use in v21.00+.

Flags 68, 69

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 70 (Accessibility)

This flag is no longer in use in v19.0131+. The messages previously controlled by this flag are now controlled by the message ID feature.

Flag 71

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 72 (Section 508 Standards)

This flag is no longer in use because it has been replaced with the built-in option to check a document against Section 508 requirements. This option is in the Validator Engine Options.

Flag 73

This flag is no longer in use in v19.01+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 75

This flag is no longer in use in v12.00+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 77

•Displays a warning message if certain tags (like "font" and "center") are used with a strict HTML 4.0/4.01 or XHTML document.

•This flag is automatically disabled in later configuration files because this functionality was replaced by improved functionality (see flags 74, 76, and 83).

•Requires CSS HTML Validator Home/Pro DLL version 5.02 or higher or these warning messages cannot be disabled if they appear.

Flag 79

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 84

•Displays a warning message if certain attributes (like "align", "bgcolor", and "width") are used in a strict HTML 4.0/4.01 or XHTML document.

•This flag is automatically disabled in later configuration files because this functionality was replaced by improved functionality (see flags 80, 81, and 82).

•Requires CSS HTML Validator Home/Pro DLL version 5.02 or higher or these warning messages cannot be disabled if they appear.

Flags 85, 86, 87, 88, 89

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 90

This flag is no longer in use in v21.00+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flags 91, 92, 93, 94, 95, 96

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 97 (Opera specific messages)

This flag is no longer in use in v21.00+. The messages controlled by this flag were obsolete and have been removed from the program.

Flag 98 is no longer used.

The single message controlled by this flag has been removed in v6.00+.

Flag 99

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flags 102, 103, 104, 105, 106

These flags are no longer in use in v6.00+. The single message previously controlled by each flag is now controlled exclusively by the message ID feature.

Flag 107 (Search Engine messages)

This flag is no longer in use in v21.00+. The messages previously controlled by this flag are now controlled by the message ID feature.

Flag 108

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 109

This flag is no longer in use in v6.00+. The single message previously controlled by this flag is now controlled exclusively by the message ID feature.

Flag 110

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 111 (Search Engine Tips)

This flag is no longer in use in v8.00+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 114 (Suppress legacy messages)

This flag is no longer in use in v24.00 because there is now an option to control legacy messages in the Message Output options.

Flag 126 (Insecure content on HTTPS pages)

This flag is no longer in use in v20.02+. The messages previously controlled by this flag are now controlled exclusively by the message ID feature.

Flag 130 (Disable "rel" attribute value checking)

This flag is no longer in use in v14.00+. Improved "rel" attribute value checking is now enabled by default.

Flag 131 (General compatibility messages for HTML 5.1)

This flag is no longer in use in v21.00 because HTML 5.1 is no longer relevant.

Flag 134 (General compatibility messages for HTML 5.2)

This flag is no longer in use in v21.00 because HTML 5.2 is no longer relevant.

Flag 135 (General compatibility messages for HTML 5.3)

This flag is no longer in use in v21.00 because HTML 5.3 is no longer relevant.

Remaining Flags

As of the time of this writing, the remaining flags that are not listed are not currently used and are for future use. You may also use them for your own use if you are writing your own tag name programs. If you do this, then we recommend that you start with the last flag (flag 180) and work your way backwards to limit conflicts with future uses of new flags.