<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - No text spoken by screen reader for "Borders" dropdown button items in Calc's formatting toolbar (NVDA on Windows)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=140762">bug 140762</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>caolanm@redhat.com, quikee@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - No text spoken by screen reader for "Borders" dropdown button items in Calc's formatting toolbar (NVDA on Windows)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=140762#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - No text spoken by screen reader for "Borders" dropdown button items in Calc's formatting toolbar (NVDA on Windows)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=140762">bug 140762</a>
from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>Michael, thanks for the fix!
Caolán and Tomaž have kept after these facets of AT, but there are lots of
places in the UI that need similar rework (e.g. provision of SVX strings) to
make the widgets meaningful to AT--rather than just sounding generic item IDs.
(In reply to Michael Weghorn from <a href="show_bug.cgi?id=140762#c7">comment #7</a>)
...
<span class="quote">> Therefore, from how I understand it so far, the case covered here is
> different from what <a class="bz_bug_link
bz_status_NEW "
title="NEW - Better support for Assistive Technology tools by exposing descriptive tooltips text with keyboard navigation"
href="show_bug.cgi?id=113488">tdf#113488</a> covers.
> </span >
That is fair, <a class="bz_bug_link
bz_status_NEW "
title="NEW - Better support for Assistive Technology tools by exposing descriptive tooltips text with keyboard navigation"
href="show_bug.cgi?id=113488">bug 113488</a> is about a difference in accessible event & focus
handling between keyboard only navigation vs what happens on mouse over or
mouse click.
Here once triggered, the focus driven accessible events did sound with keyboard
movement--they just had no meaningful descriptions.
That is fixed now, but still have the issue of difference between mouse-over or
click versus keyboard focus.
Focus requiring a mouse action is detrimental to AT. Keyboard only movements
need to provide similar accessible event triggers. And that is the crux of bug
113488 -- never silent, and best to expose the more descriptive text with every
keyboard movement inside a widget.</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>