site: add type="search" to search input

[sanjaiyan-dev]

Hi, a minor accessibility improvement has been made by adding type="search" to the input tag.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7a028bf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dummdidumm]

Reading https://adrianroselli.com/2019/07/ignore-typesearch.html it sounds like there's little to no benifit or may actually make matters worse in some cases. What arguments are there for adding type="search" in your opinion? @geoffrich do you have any additional insights?

[benmccann]

It looks like there's typically visible differences for the majority of users when using type="search": https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/search#differences_between_search_and_text_types. However, I can't see such differences in Chrome, which I suspect is because of the CSS we've applied meaning that there probably are no differences other than whatever accessibility differences might exist

[geoffrich]

It seems like the accessibility benefits of adding type="search" are minimal, but I don't think it really hurts anything. This page is not used much anyway - it's a fallback page when JS isn't available for the search modal.

[dummdidumm]

Thanks!

[benmccann]

I pushed the same commit to SvelteKit: sveltejs/kit@96993cf