diff --git a/index.bs b/index.bs
index ccf1db8..62bd5de 100644
--- a/index.bs
+++ b/index.bs
@@ -36,6 +36,13 @@ urlPrefix: https://whatpr.org/webidl/1465.html; spec: WEBIDL
text: quota; url: quotaexceedederror-quota
+
+ spec:proofreader-api; type:dfn; text:get the language availabilities partition
+ spec:writing-assistance-apis; type:dfn; text:get the language availabilities partition
+ spec:proofreader-api; type:dfn; text:compute language availability
+ spec:writing-assistance-apis; type:dfn; text:compute language availability
+
+
Introduction
The translator and language detector APIs expose the ability to translate text between human languages, and detect the language of such text. They are complementary to any built-in browser UI features for these purposes, giving web developers the ability to trigger these operations programmatically and integrate them into their applications. This can be especially useful for operating on user input, or text retrieved from the network.
@@ -465,10 +472,6 @@ When translation fails, the following possible reasons may be surfaced to the we
This table does not give the complete list of exceptions that can be surfaced by the translator API. It only contains those which can come from certain [=implementation-defined=] steps.
-
Permissions policy integration
-
-Access to the translator API is gated behind the [=policy-controlled feature=] "translator", which has a [=policy-controlled feature/default allowlist=] of [=default allowlist/'self'=].
-
The language detector API
@@ -795,13 +798,32 @@ When language detection fails, the following possible reasons may be surfaced to
This table does not give the complete list of exceptions that can be surfaced by the language detector API. It only contains those which can come from certain [=implementation-defined=] steps.
+
+
Privacy considerations
+
+Please see [[WRITING-ASSISTANCE-APIS#privacy]] for a discussion of privacy considerations for the translator and language detector APIs. That text was written to apply to all APIs sharing the same infrastructure, as noted in [[#dependencies]].
+
Permissions policy integration
+Access to the translator API is gated behind the [=policy-controlled feature=] "translator", which has a [=policy-controlled feature/default allowlist=] of [=default allowlist/'self'=].
+
Access to the language detector API is gated behind the [=policy-controlled feature=] "language-detector", which has a [=policy-controlled feature/default allowlist=] of [=default allowlist/'self'=].
-Privacy considerations
-Please see [[WRITING-ASSISTANCE-APIS#privacy]] for a discussion of privacy considerations for the translator and language detector APIs. That text was written to apply to all APIs sharing the same infrastructure, as noted in [[#dependencies]].
+iframe Permissions
+
+By default, these APIs are only available to top-level {{Window}} object, and to their same-origin iframes. Access to the APIs can be delegated to cross-origin iframes using the Permissions Policy allow="" attribute:
+
+
+
+ The translation service available to the top-origin is accessible to the example.com origin through allow attribute.
+
+
+
+
+
+ These APIs are unavailable in workers due to the complexity of setting up a responsible document for each worker to check permissions policy status. For more details, see [this discussion](https://github.com/webmachinelearning/translation-api/issues/18#issuecomment-2705630392). This restriction might be relaxed in the future.
+
Security considerations