[w3ctag/design-reviews] <search> HTML element (Issue #714)

Braw mornin' TAG!

I'm requesting a TAG review of the `<search>` HTML element.

This new element allows authors to express the semantics of "a set of form controls or other content related to performing a search or filtering operation".

This is an especially desired semantic because it is something that an ARIA landmark role exists for (role="search"), but today can only be expressed with ARIA. Adding a dedicated element allows authors to follow the [first rule of ARIA](https://w3c.github.io/using-aria/#rule1) (~ "don't use ARIA if you can avoid it") and is part of the [co-evolution process](https://w3c.github.io/aria/#co-evolution) between ARIA and HTML.

  - Explainer¹ (minimally containing user needs and example code): inline in https://github.com/whatwg/html/pull/7320

  - Specification URL: draft at https://whatpr.org/html/7320/grouping-content.html#the-search-element

  - Tests: TODO
  - User research: No formal research per se, just discussions and one [Twitter poll](https://twitter.com/domenic/status/1437891692926017537)
  - Security and Privacy self-review²: I believe this is not necessary here but am happy to draw one up if you need one.
  - GitHub repo (if you prefer feedback filed there): https://github.com/whatwg/html/

  - Primary contacts (and their relationship to the specification):
      - Domenic Denicola (@domenic), Google, spec editor
      - Carolyn MacLeod (@carmacleod), IBM, idea proposer
      - Scott O'Hara (@scottaohara), Microsoft, wrote much of the spec text
  - Organization(s)/project(s) driving the specification: I guess the three companies listed above?
  - Key pieces of existing multi-stakeholder review or discussion of this specification:
    - Lots of discussion on https://github.com/whatwg/html/issues/5811

    - Some discussion in HTML triage call: https://github.com/whatwg/html/issues/7385

  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):
    - https://bugs.chromium.org/p/chromium/issues/detail?id=1294294


Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: None currently
  - The group where the work on this specification is currently being done: WHATWG
  - Major unresolved issues with or opposition to this specification: one web developer adamantly believed that this element should have form submission functionality; as briefly explained in the explainer and discussed in detail in the issue, this was not palatable to implementers, other web developers, or the accessibility community. (So, I'm not sure if this counts as "unresolved", since we've resolved to move ahead with the current approach.)
  - This work is being funded by: I guess the three companies listed above?

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @domenic, @carmacleod, @scottaohara

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/714

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/714@github.com>