Do HTML `<form>` and `<dialog>` elements require an accessible name?

[gsharpsharp]

Describe your concern

In the WAI-ARIA spec, the form and dialog roles are labeled "Accessible Name Required." Does this mean that HTML authors are required to specify an accessible name for <form> and <dialog> elements (e.g. with an aria-label or aria-labelledby attribute) in order to comply with the WAI-ARIA spec?

The question could theoretically be asked about the <img> and <table> elements as well, but it looks like they have other native mechanisms for specifying accessible names as described in HTML Accessibility API Mappings, section 4.1.10 and section 4.1.11 respectively.

(EDIT: Just to clarify, I'm asking if the implicit ARIA semantics of the <form> and <dialog> elements given in the ARIA in HTML specification require these elements to have accessible names as prescribed by the WAI-ARIA specification. I know that the names of the HTML elements and ARIA roles are not directly related.)

Link to the version of the specification or documentation you were looking at at.

Link to documentation: https://w3c.github.io/aria/

Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)? Yes

[stevefaulkner]

In the WAI-ARIA spec, the form and dialog roles are labeled "Accessible Name Required." Does this mean that HTML authors are required to specify an accessible name for

and

elements (e.g. with an aria-label or aria-labelledby attribute) in order to comply with the WAI-ARIA spec?

no. What it means is if you use an explicit role. <div role=“dialog”> for example, you must provide an accessible name. The ARIA spec cannot define conformance requirements for native HTML elements.

[scottaohara]

to further @stevefaulkner's answer, here's the issue i filed to help correct this common misunderstanding - https://github.com/w3c/aria/issues/2180