<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: [ATK] Use WebCore Accessibility's AccessibilityText for AtkObject name and description"
href="https://bugs.webkit.org/show_bug.cgi?id=157822">157822</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>AX: [ATK] Use WebCore Accessibility's AccessibilityText for AtkObject name and description
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Accessibility
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jdiggs@igalia.com
</td>
</tr>
<tr>
<th>CC</th>
<td>webkit-bug-importer@group.apple.com
</td>
</tr>
<tr>
<th>Blocks</th>
<td>157187
</td>
</tr></table>
<p>
<div>
<pre>WebKitGtk never switched fully over to use AccessibilityText for AtkObject name and description. As a result, we have code we don't need and which is in some cases incorrect with respect to the HTML AAM and/or AccName spec.
In addition, there are a number of places where we're taking the AXDescription as the AtkObject description. This would seem logical on the surface, but as outlined in the OR of <a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: [ATK] Layout tests related to text alternative computation need to be done differently"
href="show_bug.cgi?id=157187">bug 157187</a>, it's wrong.
I'm making this bug a blocker to <a class="bz_bug_link
bz_status_NEW "
title="NEW - AX: [ATK] Layout tests related to text alternative computation need to be done differently"
href="show_bug.cgi?id=157187">bug 157187</a> so we can fix the exposure and update the layout tests in a way that will hopefully be clear (enough) to verify the code change is not introducing any regressions. After that, we can (I will) come up with a proposal with respect to how we do cross-platform text alternative calculation layout tests.
Patch will be forthcoming.</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>