WCAG 2.1 support table

HTML Techniques

The validator supports rules which can be validated without understanding the textual description of the content. E.g. it cannot suggest to use <abbr> or <dl> where appropriate or similar when to use the lang or dir attributes.

Technique Description Support
H2 Combining adjacent image and text links for the same resource No
H4 Creating a logical tab order through links, form controls, and objects No
H24 Providing text alternatives for the area elements of image maps Planned
H25 Providing a title using the title element Yes
H28 Providing definitions for abbreviations by using the abbr element No
H30 Providing link text that describes the purpose of a link for anchor elements.Use wcag/h30 to validate. Only checks for presence of text. Yes
H32 Providing submit buttons.Use wcag/h32 to validate. Yes
H33 Supplementing link text with the title attribute No
H34 Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline No
H35 Providing text alternatives on applet elements Planned
H36 Using alt attributes on images used as submit buttons.Use wcag/h36 to validate. Only checks for presence of text. Yes
H37 Using alt attributes on img elements.Use wcag/h37 to validate. Only checks for presence of text or explicit alt="" for decorative images. Yes
H39 Using caption elements to associate data table captions with data tables Planned
H40 Using description lists No
H42 Using h1-h6 to identify headings No
H43 Using id and headers attributes to associate data cells with header cells in data tables No
H44 Using label elements to associate text labels with form controls.Use input-missing-label to validate. Rule is only enabled by default in document mode (htmlvalidate:document). Yes
H45 Using longdesc No
H46 Using noembed with embed Planned
H48 Using ol, ul and dl for lists or groups of links No
H49 Using semantic markup to mark emphasized or special text No
H51 Using table markup to present tabular information No
H53 Using the body of the object element Planned
H54 Using the dfn element to identify the defining instance of a word No
H56 Using the dir attribute on an inline element to resolve problems with nested directional runs No
H57 Using language attributes on the html element.Use element-required-attributes to validate. lang is a required attribute on <html> elements. Yes
H58 Using language attributes to identify changes in the human language No
H59 Using the link element and navigation tools No
H60 Using the link element to link to a glossary No
H62 Using the ruby element No
H63 Using the scope attribute to associate header cells and data cells in data tables.Use element-required-attributes to validate. scope is a required attribute on >th< elements. Yes
H64 Using the title attribute of the frame and iframe elements.Use element-required-attributes to validate. title is a required attribute on <frame> and <iframe> elements. Yes
H65 Using the title attribute to identify form controls when the label element cannot be used Planned
H67 Using null alt text and no title attribute on img elements for images that AT should ignore.Use wcag/h67 to validate. Yes
H69 Providing heading elements at the beginning of each section of content Planned
H70 Using frame elements to group blocks of repeated material No
H71 Providing a description for groups of form controls using fieldset and legend elements.element-required-content validates presence of <legend> inside <fieldset>, but not whenever <fieldset> itself is used. Yes
H73 Using the summary attribute of the table element to give an overview of data tables Planned
H74 Ensuring that opening and closing tags are used according to specification.Use close-order and void to validate. Yes
H75 Ensuring that Web pages are well-formed.Non-well-formed pages will cause parser errors which cannot be ignored. Yes
H76 Using meta refresh to create an instant client-side redirect.Use meta-refresh to validate. Yes
H77 Identifying the purpose of a link using link text combined with its enclosing list item No
H78 Identifying the purpose of a link using link text combined with its enclosing paragraph No
H79 Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells No
H80 Identifying the purpose of a link using link text combined with the preceding heading element No
H81 Identifying the purpose of a link in a nested list using link text combined with the parent list item under which the list is nested No
H83 Using the target attribute to open a new window on user request and indicating this in link text No
H84 Using a button with a select element to perform an action No
H85 Using OPTGROUP to group OPTION elements inside a SELECT No
H86 Providing text alternatives for ASCII art, emoticons, and leetspeak Partial planned
H88 Using HTML according to spec.Use the content model rules to validate. Yes
H89 Using the title attribute to provide context-sensitive help No
H90 Indicating required form controls using label or legend Planned
H91 Using HTML form controls and links Planned
H93 Ensuring that id attributes are unique on a Web page.Use no-dup-id to validate, preferably in document mode. Yes
H94 Ensuring that elements do not contain duplicate attributes.Use no-dup-attr to validate. Yes
H95 Using the track element to provide captions Planned
H96 Using the track element to provide audio descriptions Planned
H97 Grouping related links using the nav element No
H98 Using HTML 5.2 autocomplete attributes Planned