From ab5855f02c5f78b9779c305d467c7ecf35ed8788 Mon Sep 17 00:00:00 2001 From: Jason Kiss Date: Wed, 8 Feb 2017 15:33:34 +1300 Subject: [PATCH 1/2] Clarify UIA and AX mappings for audio/video and sub-dom controls See issue #80 Also relevant is issue #3 --- index.html | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/index.html b/index.html index a943f442..5120916e 100644 --- a/index.html +++ b/index.html @@ -438,8 +438,8 @@

HTML Element Role Mappings

Control Type: Group
Localized Control Type: "audio"
-
If the controls attribute is present, each control is a child in the UIA tree, and mapped as button, slider, etc. as appropriate for the type of control.
-
Loading and error text objects, along with any control not currently displayed, MAY be present in the UIA and marked as hidden or off-screen.
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as children of the audio element in the accessibility tree, and mapped as appropriate for the type of control (e.g. button or slider).
+
Text objects associated with loading or error messages, and any UI control not currently displayed, MAY be present in the accessibility tree and marked as hidden or off-screen.
@@ -452,12 +452,12 @@

HTML Element Role Mappings

AXRole: AXGroup
- AXSubrole: (nil) + AXSubrole: AXAudio
- AXRoleDescription: "group" + AXRoleDescription: "audio playback"
-
Note: UI controls within the audio element exposed as AXToolbar.
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as descendants of an accessible object with a role of toolbar, and mapped as appropriate for the type of control (e.g. button or slider).
@@ -3603,11 +3603,12 @@

HTML Element Role Mappings

-
- Control Type: Group -
-
If the controls attribute is present, each control is a child in the UIA tree, and mapped as button, slider, etc. as appropriate for the type of control.
-
Loading and error text objects, along with any control not currently displayed, MAY be present in the UIA and marked as hidden or off-screen.
+
+ Control Type: Group +
+
Localized Control Type: "group"
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as children of the video element in the accessibility tree, and mapped as appropriate for the type of control (e.g. button or slider).
+
Text objects associated with loading or error messages, and any UI control not currently displayed, MAY be present in the accessibility tree and marked as hidden or off-screen.
@@ -3620,14 +3621,15 @@

HTML Element Role Mappings

AXRole: AXGroup
- AXSubrole: (nil) + AXSubrole: AXVideo
- AXRoleDescription: "group" + AXRoleDescription: "video playback"
-
Note: UI controls within the video element exposed as AXToolbar.
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as descendants of an accessible object with a role of toolbar, and mapped as appropriate for the type of control (e.g. button or slider).
+ wbr From 518350f1441da3ff111fb10d8916e65655e07d7f Mon Sep 17 00:00:00 2001 From: Jason Kiss Date: Fri, 24 Nov 2017 12:47:51 +1300 Subject: [PATCH 2/2] include note in change log for updates to audio and video elements, issue 80 --- index.html | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/index.html b/index.html index 3bfe1c18..8bab24d3 100644 --- a/index.html +++ b/index.html @@ -436,7 +436,7 @@

HTML Element Role Mappings

Control Type: Group
Localized Control Type: "audio"
-
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as children of the audio element in the accessibility tree, and mapped as appropriate for the type of control (e.g. button or slider).
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as children of the audio element in the accessibility tree, and mapped as appropriate for the type of control (e.g. button or slider).
Text objects associated with loading or error messages, and any UI control not currently displayed, MAY be present in the accessibility tree and marked as hidden or off-screen.
@@ -455,7 +455,7 @@

HTML Element Role Mappings

AXRoleDescription: "audio playback"
-
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as descendants of an accessible object with a role of toolbar, and mapped as appropriate for the type of control (e.g. button or slider).
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as descendants of an accessible object with a role of toolbar, and mapped as appropriate for the type of control (e.g. button or slider).
@@ -3490,7 +3490,7 @@

HTML Element Role Mappings

- video + video No corresponding role
@@ -3502,7 +3502,7 @@

HTML Element Role Mappings

Control Type: Group
Localized Control Type: "group"
-
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as children of the video element in the accessibility tree, and mapped as appropriate for the type of control (e.g. button or slider).
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as children of the video element in the accessibility tree, and mapped as appropriate for the type of control (e.g. button or slider).
Text objects associated with loading or error messages, and any UI control not currently displayed, MAY be present in the accessibility tree and marked as hidden or off-screen.
@@ -3521,7 +3521,7 @@

HTML Element Role Mappings

AXRoleDescription: "video playback"
-
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as descendants of an accessible object with a role of toolbar, and mapped as appropriate for the type of control (e.g. button or slider).
+
Note: If the controls attribute is present, UI controls (e.g. play, volume) are exposed as descendants of an accessible object with a role of toolbar, and mapped as appropriate for the type of control (e.g. button or slider).
@@ -5988,6 +5988,7 @@

Change Log

Substantive changes since moving entirely to the Web Platform Working Group (01-Oct-2016)