<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi all,<div><br></div><div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; ">in my opinion it would be great to have a component for accessibility; it could let developers to better focus on accessibility bugs and, on the other hand, blind people to know that accessibility is important for this project and that submitting bug reports of this type is more than encouraged…</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; ">Let's take, for instance, the mac os x version of LO: unfortunately it contains tons of accessibility bugs that make impossible to use it for a blind user; if I would submit them with the label "accessibility" developers could understand faster what works and what doesn't...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; ">Just my opinion; maybe I am late, but I decided to share the opinion from my blind-user waiting for an accessible mac os x version of lo perspective...</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; "> Vincenzo.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal normal normal 12px/normal Helvetica; "><br></div></span></div><div><div>Il giorno 19/ago/2012, alle ore 10:29, Rainer Bielefeld <<a href="mailto:LibreOffice@bielefeldundbuss.de">LibreOffice@bielefeldundbuss.de</a>> ha scritto:</div><br class="Apple-interchange-newline"><blockquote type="cite">Roman Eisele schrieb:<br><blockquote type="cite">Am 18.08.12 03:57, schrieb Marc Paré:<br><blockquote type="cite">Would it make sense to add "Accessibility" as another component to the<br>Bug Assistant? Maybe this would encourage people to submit more<br>accessibility bugs? Not to mention that the component would show at the<br>very first steps of reporting, which may help people find it more easily<br>if they are reporting with the use of a reader?<br></blockquote><br>IMHO we should not have too many components, because this will make it<br>more difficult (instead of easier) to find the matching one, but I<br>second this proposal. Free and open software should be open for as many<br>people as possible, so accessibility is a very important feature for a<br>FLOSS office suite like LibreOffice, and therefore it may be helpful to<br>have a special component for issues related to accessibility. At least<br>the special component will remind us all everyday about the importance<br>of considering accessibility everywhere ;-).<br><br>Just my 2 cents ;-)<br></blockquote><br><br>Hello,<br><br>I agree with Roman, but it might be a problem for a disabled user do have to search BSA until he finds ACCESSIBILITY at UI?<br><br>One way would be to add it as Sub Component to all relevant Components, or of course, adding a component.<br><br>May be we can get advice from <a href="mailto:accessibility@global.libreoffice.org">accessibility@global.libreoffice.org</a>?<br><br>Best regards<br><br>Rainer<br><br>-- <br>Unsubscribe instructions: E-mail to <a href="mailto:accessibility+help@global.libreoffice.org">accessibility+help@global.libreoffice.org</a><br>Problems? <a href="http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/">http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/</a><br>Posting guidelines + more: <a href="http://wiki.documentfoundation.org/Netiquette">http://wiki.documentfoundation.org/Netiquette</a><br>List archive: <a href="http://listarchives.libreoffice.org/global/accessibility/">http://listarchives.libreoffice.org/global/accessibility/</a><br>All messages sent to this list will be publicly archived and cannot be deleted<br><br></blockquote></div><br></div></body></html>