![Rachel Andrew](https://web.dev/images/authors/rachelandrew.jpg) Rachel Andrew Technical Writer [GitHub](https://github.com/rachelandrew) [LinkedIn](https://www.linkedin.com/in/rachelandrew) [Mastodon](https://front-end.social/@rachelandrew) [Bluesky](https://bsky.app/profile/rachelandrew.bsky.social) [Homepage](https://rachelandrew.co.uk)

<br />


Published: September 3, 2026

<br />

Interop 2027 launches today! As in previous years, the project begins with a
[call for
proposals](https://github.com/web-platform-tests/interop/issues/new/choose).
This is your chance to tell us which web platform features you would love to see
included in the project next year. When the proposal period ends on **September
23rd** all features will be considered according to [this
process](https://github.com/web-platform-tests/interop/blob/main/2027/selection-process.md).

## What makes a good project proposal?

The Interop project aims to take things that have already been through the
standards process, and make them interoperable. Therefore, the first thing to
consider is whether your idea has a stable specification, and no outstanding
objections from one or more browser vendors. Past features have typically been
implemented in at least one browser before becoming part of the project.

Features that have a stable implementation should also have the other thing
that's needed for a successful proposal---a good test suite. The success of a
feature in the project is based on browsers passing these tests, so we need to
know that there are enough tests in the first place.

Find out more information by reading the [Proposal
Guide](https://github.com/web-platform-tests/interop/blob/main/proposal_guide.md).
This guide includes some additional signals that can help to boost the chances
of your proposal succeeding.

## Inspiration for 2027

As we head towards the end of the third quarter of the year, there's been great
progress on the accepted proposals for [Interop
2026](https://wpt.fyi/interop-2026). In fact, all browsers are in a much
stronger position than at the same time last year, in terms of progress to 100%.
![The dashboard for Interop 2026 features showing Experimental browsers. Scores as follows: Chrome 98, Edge 98, Firefox 96, Safari 92.](https://web.dev/static/blog/interop-2027-proposals/image/dashboard2026.png) [Interop 2026 dashboard](https://wpt.fyi/interop-2026) 3 September, 2026

[As we explained at the beginning of 2026](https://web.dev/blog/interop-2026.md.txt), many of the
features this year showed up as top features mentioned in developer surveys such
as The State of CSS, or were in the top 20 in the [developer signals
repository](https://github.com/web-platform-dx/developer-signals/issues?q=is:issue+state:open+sort:reactions-%2B1-desc+label:feature).

Use [webstatus.dev](https://webstatus.dev/) to identify features that meet the
requirements for good proposals, and check out the [developer signals
repository](https://github.com/web-platform-dx/developer-signals/issues?q=is:issue+state:open+sort:reactions-%2B1-desc+label:feature)
to see if there are any published use cases to help support your case.

## Help make 2027 a success

Even if you don't have a feature to propose, keep an eye on the growing [list of
proposals](https://github.com/web-platform-tests/interop/issues/) and like and
comment on the submissions you think are most important. Share the call for
proposals on social media, and in any developer communities you are part of, and
help us to make the web more interoperable once again!