W3C validator will notify of typos
The most common mistake when checking a document with the official W3C validator is the use of a nonexistent attribute, while users see the message “There is no attribute X” or “Required attribute X not specified”.
Probably a large percentage of such errors arise due to descriptions. Now, the test version of the W3C validator contains support for recognizing obvious typos, with a suggestion for fixing them. This works similar to typos in search engines, for example, as a result, the message “There is no attribute 'crass' may be displayed. Maybe you meant 'class' or 'classid'? ”
Example:
Thus, the validator should facilitate the correction of the code in order to comply with greater validity ( W3C Systems Team Blog ).
Probably a large percentage of such errors arise due to descriptions. Now, the test version of the W3C validator contains support for recognizing obvious typos, with a suggestion for fixing them. This works similar to typos in search engines, for example, as a result, the message “There is no attribute 'crass' may be displayed. Maybe you meant 'class' or 'classid'? ”
Example:
Thus, the validator should facilitate the correction of the code in order to comply with greater validity ( W3C Systems Team Blog ).