<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 - Libreoffice Notebookbar is not exposing accessible events needed for screen reader users."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=109425">bug 109425</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;">Keywords</td>
<td>
</td>
<td>implementationError
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>caolanm@redhat.com, michael.meeks@collabora.com, sbergman@redhat.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Libreoffice Notebookbar is not exposing accessible events needed for screen reader users."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=109425#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Libreoffice Notebookbar is not exposing accessible events needed for screen reader users."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=109425">bug 109425</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>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=109425#c8">comment #8</a>)
<span class="quote">> (In reply to V Stuart Foote from <a href="show_bug.cgi?id=109425#c4">comment #4</a>)
> > ...correct implementation of
> > assistive technology is _required_ across the UI but fortunately is simple
> > to implement in UI.
>
> We could understand MUFFIN in a way to create a Notebookbar variant
> explicitly focusing on accessibility. </span >
Separate implementations for Accessibility is not an answer, that is not how we
or any application supports a11y. Instead we provide framework for effective
keyboard navigation and then attach accessible events across the UI. The
integrated accessible events for components of the Notebookbar are missing.
<span class="quote">> On the other hand we clearly defined
> the minimum requirements for keyboard interaction
> <a href="https://wiki.documentfoundation.org/Design/SideBar">https://wiki.documentfoundation.org/Design/SideBar</a></span >
Sure and keyboard navigation on the Notebookbar(s) are mostly correct, but even
if keyboard navigation is sequenced correctly with no traps or dropouts, we
need to correctly implement our existing support for GetAccessible() event
handling of each widget. Also need to ensure correct packing order for TAB
sequence across the Notebookbar(s), and support our use of Tooltips as
annotation exposed to the AT. Picking up the accelerators and any defined
short-cuts would just be gravy for an improved UX for a11y dependent users.
This remains to be fixed on all of the Notebookbar flavors for MUFFIN
interface.</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>