Chrome UX with MathJax SVG output
Closed this issue · 4 comments
In the context of #2 we had removed a SVG-specific hack to fix a bug wrt MathJax v3. The "natural" result (cf our tests) is that the mjx-container element becomes the tree root and the svg gets role=presentation.
This leads to bad UX on Chrome: when navigating the tree, Chrome complains about a graphic without description and suggests to users to use the context menu to activate automatic (machine learning) captioning.
Authors can workaround this by calling sre-to-tree on the svg instead of the container but perhaps an SVG-specific hack is appropriate after all.
Coming back to this, it seems mostly a documentation issue to me. We need to educate people that with the SVG output, they should run sre2tree on the SVG node, not its mjx-container.
Coming back to this, it seems mostly a documentation issue to me. We need to educate people that with the SVG output, they should run sre2tree on the SVG node, not its mjx-container.
Should that education/documentation happen here? I'm not sure. Without the aria-tree-walker, you won't run into the problem since you can't navigate past the container anyway.
I changed the test to mention this issue.
Should that education/documentation happen here? I'm not sure. Without the aria-tree-walker, you won't run into the problem since you can't navigate past the container anyway.
Let's close this then.