AXSubrole of <annotation> #14
Comments
blueboxd
pushed a commit
to blueboxd/chromium-legacy
that referenced
this issue
Oct 20, 2021
This CL introduces the minimal number of MathML roles so that one can implement role and attribute mapping for ATK and AX API [1]. Exact roles for some tags are still being discussed on the spec side and might change in the future [2] [3] [4] [5] [6]. On Windows and Android platforms, math roles is a bit undefined and so some dummy role mapping is used right now. Node tests are added to cover all elements of MathML Core. These new tests also verify that the MathML element tags are exposed as an AtkObject attribute. [1] https://w3c.github.io/mathml-aam/ [2] w3c/mathml-aam#9 [3] w3c/mathml-aam#11 [4] w3c/mathml-aam#12 [5] w3c/mathml-aam#13 [6] w3c/mathml-aam#14 AX-Relnotes: MathML elements are exposed in the accessible tree with specific roles. Bug: 6606, 1038895, 1051115, 1038897, 1038898, 1038899, 1038900, 1038901, 1038911, 1038913, 1052420 Change-Id: I7e857a0cfc05616a30bf4842e334c1dfde082d49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3207929 Commit-Queue: Frédéric Wang <fwang@igalia.com> Reviewed-by: Nektarios Paisios <nektar@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/main@{#933442}
mjfroman
pushed a commit
to mjfroman/moz-libwebrtc-third-party
that referenced
this issue
Oct 14, 2022
This CL introduces the minimal number of MathML roles so that one can implement role and attribute mapping for ATK and AX API [1]. Exact roles for some tags are still being discussed on the spec side and might change in the future [2] [3] [4] [5] [6]. On Windows and Android platforms, math roles is a bit undefined and so some dummy role mapping is used right now. Node tests are added to cover all elements of MathML Core. These new tests also verify that the MathML element tags are exposed as an AtkObject attribute. [1] https://w3c.github.io/mathml-aam/ [2] w3c/mathml-aam#9 [3] w3c/mathml-aam#11 [4] w3c/mathml-aam#12 [5] w3c/mathml-aam#13 [6] w3c/mathml-aam#14 AX-Relnotes: MathML elements are exposed in the accessible tree with specific roles. Bug: 6606, 1038895, 1051115, 1038897, 1038898, 1038899, 1038900, 1038901, 1038911, 1038913, 1052420 Change-Id: I7e857a0cfc05616a30bf4842e334c1dfde082d49 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3207929 Commit-Queue: Frédéric Wang <fwang@igalia.com> Reviewed-by: Nektarios Paisios <nektar@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/main@{#933442} NOKEYCHECK=True GitOrigin-RevId: d6d648b6dc54c1c78936dc506e5ccebe23cee7a3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cc @cookiecrook @asurkov
Currently, AXSubrole of
<annotation>is TBD.That element is used to display alternative text annotation for a MathML formula (LaTeX source, Maple commands, etc) and with the default style of MathML Core,
<annotation>is hidden and won't be exposed. However, it's possible that someone changes that style (e.g. via a user stylesheet to force displaying LaTeX annotation instead of MathML). See https://w3c.github.io/mathml-core/#semantics-and-presentationI wonder whether exposing them the same as
<mtext>make sense? That is something like:The text was updated successfully, but these errors were encountered: