From a83deff760d347c37716225f4f64b77cc7133eee Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Mon, 27 Nov 2023 13:06:04 -0500 Subject: [PATCH 1/4] Chore: spec cleanup - update link from accName 1.1 to 1.2 - update ARIA link from 1.1 to ED - alphabetize AAM spec listing --- index.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 2baa3c93..ee102e10 100644 --- a/index.html +++ b/index.html @@ -83,7 +83,7 @@

- HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [[HTML]] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the [[[core-aam-1.2]]] and the [[[accname-aam-1.1]]] for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent. + HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [[HTML]] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the [[[core-aam-1.2]]] and the [[[accname-aam-1.2]]] for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

The HTML-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview. @@ -100,7 +100,7 @@

Introduction

- This specification defines how HTML user agents respond to and expose [=role=], [=state=] and [=ARIA/property=] information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default [[[WAI-ARIA]]] semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[core-aam-1.2]]] ([[core-aam-1.2]]) specification. + This specification defines how HTML user agents respond to and expose [=role=], [=state=] and [=ARIA/property=] information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default [[[wai-aria]]] semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[core-aam-1.2]]] ([[core-aam-1.2]]) specification.

In some cases, often due to features of the HTML host language or the accessibility API in question, an element or attribute's mapping differs from the corresponding ARIA mappings specified in the [[core-aam-1.2]]. Where an HTML element or attribute does not have any default WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification. @@ -115,9 +115,9 @@

Introduction

  • [[[accname-1.2]]]
  • [[[core-aam-1.2]]]
  • HTML Accessibility API Mappings 1.0 (this specification)
    • -
  • [[[svg-aam-1.0]]]
  • MathML AAM 1.0
    • +
  • [[[svg-aam-1.0]]]

    • Accessibility APIs

    From 04db2047d8f13cdde416a322f18ff6c35bd971d9 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Mon, 27 Nov 2023 13:09:21 -0500 Subject: [PATCH 2/4] Update index.html --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index ee102e10..78ae5f87 100644 --- a/index.html +++ b/index.html @@ -83,7 +83,7 @@

    - HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [[HTML]] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the [[[core-aam-1.2]]] and the [[[accname-aam-1.2]]] for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent. + HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [[HTML]] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the [[[core-aam-1.2]]] and the [[[accname-1.2]]] for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.

    The HTML-AAM is part of the WAI-ARIA suite described in the WAI-ARIA Overview. From dde0c90bf05c0edfc0f953484d60ce71e66cb84f Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Mon, 27 Nov 2023 13:13:03 -0500 Subject: [PATCH 3/4] update to 1.2 --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 78ae5f87..afd0ba34 100644 --- a/index.html +++ b/index.html @@ -100,7 +100,7 @@

    Introduction

    - This specification defines how HTML user agents respond to and expose [=role=], [=state=] and [=ARIA/property=] information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default [[[wai-aria]]] semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[core-aam-1.2]]] ([[core-aam-1.2]]) specification. + This specification defines how HTML user agents respond to and expose [=role=], [=state=] and [=ARIA/property=] information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default [[[wai-aria-1.2]]] semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[core-aam-1.2]]] ([[core-aam-1.2]]) specification.

    In some cases, often due to features of the HTML host language or the accessibility API in question, an element or attribute's mapping differs from the corresponding ARIA mappings specified in the [[core-aam-1.2]]. Where an HTML element or attribute does not have any default WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification. From 5583f5cd1843f5c656263e3ce9b238ba669a3918 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Mon, 27 Nov 2023 13:30:18 -0500 Subject: [PATCH 4/4] Update index.html remove redundant core aam link match core aam in listing a11y apis provide abbr for API --- index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index afd0ba34..46103314 100644 --- a/index.html +++ b/index.html @@ -100,7 +100,7 @@

    Introduction

    - This specification defines how HTML user agents respond to and expose [=role=], [=state=] and [=ARIA/property=] information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default [[[wai-aria-1.2]]] semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[core-aam-1.2]]] ([[core-aam-1.2]]) specification. + This specification defines how HTML user agents respond to and expose [=role=], [=state=] and [=ARIA/property=] information provided for Web content. Unless indicated otherwise, an HTML element or attribute with default [[[wai-aria-1.2]]] semantics must be exposed to the platform accessibility APIs according to the relevant WAI-ARIA mappings defined in the [[[core-aam-1.2]]] specification.

    In some cases, often due to features of the HTML host language or the accessibility API in question, an element or attribute's mapping differs from the corresponding ARIA mappings specified in the [[core-aam-1.2]]. Where an HTML element or attribute does not have any default WAI-ARIA semantics, the applicable mapping for each platform accessibility API is defined by this specification. @@ -116,7 +116,7 @@

    Introduction

  • [[[core-aam-1.2]]]
  • HTML Accessibility API Mappings 1.0 (this specification)
    • -
  • MathML AAM 1.0
    • +
  • MathML Accessibility API Mappings 1.0
  • [[[svg-aam-1.0]]]
    • @@ -125,13 +125,13 @@

    Accessibility APIs

    Accessibility APIs covered by this document are:

    - If user agent developers need to expose information using other accessibility APIs, it is recommended that they work closely with the developer of the platform where the API runs, and assistive technology developers on that platform. + If user agent developers need to expose information using other accessibility APIs, it is recommended that they work closely with the developer of the platform where the API runs, and assistive technology developers on that platform.

    For more information regarding accessibility APIs, refer to section 1.1 Accessibility APIs of the [[[core-aam-1.2]]].