<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Accessibility of MathML links"
href="https://bugs.webkit.org/show_bug.cgi?id=161081#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Accessibility of MathML links"
href="https://bugs.webkit.org/show_bug.cgi?id=161081">bug 161081</a>
from <span class="vcard"><a class="email" href="mailto:cfleizach@apple.com" title="chris fleizach <cfleizach@apple.com>"> <span class="fn">chris fleizach</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=161081#c4">comment #4</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=161081#c3">comment #3</a>)
> > Comment on <span class=""><a href="attachment.cgi?id=286711&action=diff" name="attach_286711" title="WIP Patch">attachment 286711</a> <a href="attachment.cgi?id=286711&action=edit" title="WIP Patch">[details]</a></span>
> > WIP Patch
> >
> > View in context:
> > <a href="https://bugs.webkit.org/attachment.cgi?id=286711&action=review">https://bugs.webkit.org/attachment.cgi?id=286711&action=review</a>
> >
> > > Source/WebCore/accessibility/AccessibilityMathMLElement.cpp:62
> > > + if (node && node->isLink())
> >
> > I don't know if we want to change the math role away from what it is to a
> > link.
> > if you put the href on a <mfrac> then that might mess up the math tree
> > that's created
>
> (In reply to <a href="show_bug.cgi?id=161081#c3">comment #3</a>)
> > I don't know if we want to change the math role away from what it is to a
> > link.
> > if you put the href on a <mfrac> then that might mess up the math tree
> > that's created
>
> We definitely do not want to have the role overridden (although that's maybe
> not too much a trouble if href is only used on mrow). That's why I did not
> ask review for this patch ;-)
>
> > it seems like either we should
> > a) expand the concept of roles so that an object can have more than one role
> > b) make being a link an attribute as well as a role (probably the easiest
> > path)
> > c) make a fake element representing the link that becomes the parent of the
> > object
>
> I believe we should get feedback from AT developers but my guess would be
> that on their side: c) won't need any effort , b) will need a minor effort
> and a) will be more complex.
>
> Actually I'm curious about c), since that might help to remove anonymous
> nodes for mfenced if we decide to rewrite its renderer class (<a class="bz_bug_link
bz_status_NEW "
title="NEW - [meta] Removing/rewriting the mfenced implementation"
href="show_bug.cgi?id=160509">bug 160509</a>).</span >
i’m concerned C) might have adverse affects too. if you put this on a node within a math term, it might also change the expected hierarchy and break something. i think b) might be the easiest although we’ll need to change ATs for mac. iOS should be able to easily adopt this since a link is already an attribute</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>