Re: [w3ctag/design-reviews] HTMLPopupElement - <popup> (#680)

> A `<popup>` is something that has these qualities:

That doesn't really help. Those are behaviors, not semantics or types of controls. (I.e. the things that feed into roles.)

Below you propose that the role should be dialog. That implies that instead of being a new element, this should be some sort of mode of the dialog element, since the dialog element already occupies the semantic space of dialogs. (E.g., `<dialog type="light-dismiss">` or `dialogEl.showWithLightDismiss()`.)

> In general, the `<dialog>` element is already in a somewhat similar boat, no? I.e. a `<dialog>` can be used for a number of UI purposes, such as dialogs, tooltips, toasts, etc. But the platform uses role=dialog and it's up to the developer to specialize further with ARIA attributes if it is being used for a more-specific purpose such as a tooltip.

No, this isn't correct. The dialog element can only be used for dialogs. Tooltips or toasts should be done using `<div>`s or similar. (Or perhaps a new element, if someone were bold enough to propose one... I seem to recall something of that sort for toasts.) If you use `<dialog>` but then override its exposure to accessibility tech using `role=something else`, the element is being misused.

We need to figure out what the similar semantic space, and corresponding role, is for popup. The explainer example seems to give several types of controls: menus, form element suggestions, content pickers, and teaching UI. What is the ARIA role for each of these? Perhaps each should have a separate element, not `<popup>`, which implements the appropriate semantics (and behaviors?? I can't imagine a teaching UI needs the exact same behaviors as a menu). Or perhaps some of those are better suited for `<dialog>` instead of `<popup>`.

I apologize that this is rather fundamental criticism, but I do feel like I've raised it repeatedly since the beginning of this endeavor, without much response. I appreciate getting some concrete engagement at this point.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/680#issuecomment-943472331