Check against a11y checklist for CR transition

Nobody has claimed this yet.

Results of accessibility questionnaire:

This is a request for transition for all 3 WebAssembly specifications, namely the core spec, which defines the core code format and semantics;
the JS API specification, which provides a JavaScript API for interacting with WebAssembly; and the Web API specification, which describes the integration of WebAssembly with the broader web platform.

All of the analysis herein concerns the changes made since Wasm 1.0. These are listed
here and include the following extension
proposals:
Sign extension instructions; Non-trapping float-to-int conversions; multi-value block types and function results;
reference types, table instructions, and multiple tables; bulk memory and table instructions; SIMD vector instructions. Links to overviews of each proposal can be found in the proposal's respective github repo (these are listed here).

Section	Analysis
If technology allows visual rendering of content	N/A
If technology provides author control over color	N/A
If technology provides features to accept user input	N/A
If technology provides user interaction features	N/A
If technology defines document semantics	N/A
If technology provides time-based visual media	N/A
If technology provides audio	N/A
If technology allows time limits	N/A
If technology allows text content	N/A
If technology creates objects that don't have an inherent text representation	N/A
If technology provides content fallback mechanisms, whether text or other formats	N/A
If technology provides visual graphics	N/A
If technology provides internationalization support	N/A
If technology defines accessible alternative features	N/A
If technology provides content directly for end-users	N/A
If technology defines an API	The JS API is extended to allow references to JS objects to passed to wasm code using the `externref` opaque reference type, and multiple tables of references may now be exported to JS code. We are unaware of any accessibility implications of this.
If technology defines a transmission protocol	N/A

Start with the linked W3C APA accessibility checklist and compare it with the listed Wasm 2.0 changes and the JS API notes. Confirm whether the N/A entries and the stated lack of accessibility implications are complete for the core, JS API, and Web API specifications; done means the transition analysis is checked and any gaps are recorded.

Written by the indexing model from the issue text.

Description

Contributor guide

First steps

Research direction

Assessment