Banners and notices

Banners are added using macros that are usually inserted below the page metadata, alongside the page sidebar macro. For example, in the block below, the {{SecureContext_Header}} macro has been used to indicate that the AudioDecoder interface is only available in a secure context, the {{AvailableInWorkers}} macro has been used to indicate that the AudioDecoder interface is only available in window context and dedicated worker context, and {{SeeCompatTable}} has been added to indicate that the interface is experimental.

---
title: AudioDecoder
slug: Web/API/AudioDecoder
page-type: web-api-interface
status:
  - experimental
browser-compat: api.AudioDecoder
---

{{APIRef("WebCodecs API")}} {{SeeCompatTable}} {{SecureContext_Header}} {{AvailableInWorkers("window_and_dedicated")}}

You need to add the following macros manually:

• {{SecureContext_Header}} — this generates a Secure context banner that indicates the technology is only available in a secure context.
• {{AvailableInWorkers}} — this generates a Available In Workers note that indicates that the technology is available in worker context.

The following macros are automatically added to the content in order to match the statuses stored in the browser compat data repository:

• {{SeeCompatTable}} — generates a This is an experimental technology banner that indicates the technology is experimental.
• {{Deprecated_Header}} — generates a Deprecated banner that indicates that use of the technology is discouraged.
• {{Non-standard_Header}} — generates a Non-Standard banner that indicates that use of the technology is not part of a formal specification, even if it is implemented in multiple browsers.

Update the feature status in the browser-compat-data repository in order to change these values.

Occasionally, browser vendors disagree on how a feature is developing, and some may oppose it in its current form. In exceptional cases, MDN documents technologies in this state to encourage the web community to experiment with them, provide feedback, and help browser vendors reach a consensus.

It is important to clarify the current standardization status of such features to readers. While a longer-term solution for representing this information is not final, we are doing the following for specific high-profile technologies to avoid confusion:

• Adding this banner to the landing page for that feature (not for every subpage for the feature):

  md

  > [!WARNING]
  > This feature is currently opposed by <number> browser vendor(s). See the [Standards positions](#standards_positions) section below for details of opposition.
  

  • Replace <number> with the number of browser vendors opposing the feature.
  • Use vendor or vendors as appropriate.

• Adding a "Standards positions" section to the same page as the above banner, as a sub-section of the standard "Specifications" section.