<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - ACCESSIBILITY: Issues with tabbed dialogs on Mac OS X" href="https://bugs.documentfoundation.org/show_bug.cgi?id=67943#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - ACCESSIBILITY: Issues with tabbed dialogs on Mac OS X" href="https://bugs.documentfoundation.org/show_bug.cgi?id=67943">bug 67943</a> from <a class="email" href="mailto:iplaw67@tuta.io" title="Alex Thurgood <iplaw67@tuta.io>"> Alex Thurgood</a> <pre>Hi Julien, The link you posted previously in <a href="show_bug.cgi?id=67943#c6">comment 6</a>, points to a now deprecated accessibility API. The current API that should be used : <a href="https://developer.apple.com/documentation/appkit/nsaccessibilitytabgrouprole?language=objc">https://developer.apple.com/documentation/appkit/nsaccessibilitytabgrouprole?language=objc</a> points to a specific tabgroup role, but again, is not particularly helpful. The subrole page also has a tabButtonSubrole : <a href="https://developer.apple.com/documentation/appkit/nsaccessibilitytabbuttonsubrole?language=objc">https://developer.apple.com/documentation/appkit/nsaccessibilitytabbuttonsubrole?language=objc</a> See also this discussion here about TextMate, where a similar problem was encountered when using VoiceOver in a tabbed setting: <a href="https://github.com/textmate/bugs/issues/7">https://github.com/textmate/bugs/issues/7</a> Also, it seems that the Chromium project addressed a similar issue here : <a href="https://groups.google.com/a/chromium.org/forum/#!topic/chromium-reviews/vK3ReXKiJi0">https://groups.google.com/a/chromium.org/forum/#!topic/chromium-reviews/vK3ReXKiJi0</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>