- From: Dasein. <notifications@github.com>
- Date: Sat, 26 Feb 2022 12:00:58 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/714/1052536858@github.com>
> 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 --- https://github.com/whatwg/html/issues/5811 - Fwiw, and if setting the other stuff aside, I would also agree with the functional benefits being worth it for a Semantic Markup/HTML <**_**search**_**> element. _Even if compromises on the direction for implementing this would need to be found._ :3 **_**Many apologies if this response is expressed incorrectly or otherwise against any established guidelines, but felt it'd be important to atleast voice it ☺️**_** -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/714#issuecomment-1052536858 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/714/1052536858@github.com>
Received on Saturday, 26 February 2022 20:01:12 UTC