Date: prev next · Thread: first prev next last


I can't believe I messed up again, "accessibleRole::CHECK_BUTTON" should be "accessibleRole::TOGGLE_BUTTON". :(
But after digging a little I believe that we should leave it as is at 
the moment. Also note that "real" radio buttons in dialogs already get 
the correct role. See below for more info on why I believe we should 
leave it for now.
I did a testbuild with on Ubuntu only changing TIB_RADIOCHECK to be of 
accessibleRole::RADIO_BUTTON that updated the role of most toolbar 
buttons that have a radio button type of functionality, for example the 
align buttons in the formatting bar. I'm seeing some extra error output 
in the terminal when they have focus, might be some missing pieces 
surrounding the radio button group information, I did not look to closely.
After that I kept digging into other apps on Linux and it seems that for 
example similar buttons in Nautilus use the role TOGGLE_BUTTON. Looking 
at Mac I see some programs for example Pages that uses AXCheckBox (which 
TOGGLE_BUTTON gets mapped to) for this types of buttons. On the other 
hand TextEdit uses Radio group and radio buttons. A part of me still 
think that radio button is more appropriate because that is the 
functionality of these buttons, but there are more pressing issues when 
it comes to accessibility in LibreOffice.
Best Regards,
Niklas Johansson

Julien Nabet skrev 2014-02-26 22:42:
I gave a try but it failed since "accessibleRole::CHECK_BUTTON"doesn't exist (and no "Role::CHECK_BUTTON")
I give up with this.

Julien

On 26/02/2014 22:17, Niklas Johansson wrote:
I'm very sorry I mislead you with a copy and paste error in my previous message. TIB_CHECKABLE should have been TIB_RADIOCHECK.
So
TIB_CHECKABLE => Role::CHECK_BUTTON
And
TIB_RADIOCHECK => Role::RADIO_BUTTON

So it is not trickier than you thought.

I really need to start triple check my messages before I send them. :(

Again very sorry for the confusion.

/Niklas

onsdagen den 26:e februari 2014 skrev julien2412 <serval2412@yahoo.fr <mailto:serval2412@yahoo.fr>>:
    Thank you Niklas for your feedback, so it's more tricky than I
    thought:
    TIB_CHECKABLE => Role::RADIO_BUTTON (and not  Role::CHECK_BUTTON as
    "CHECKABLE" may mislead)
    Then, what about TIB_RADIOCHECK which contains "RADIO" and "CHECK"?


    Considering all this, I'll let this aside since I'm just a newbie
    about all
    this and so could easily make a mistake.

    Julien



    --
    View this message in context:
    
http://nabble.documentfoundation.org/About-Role-RADIO-BUTTON-and-Role-CHECK-BUTTON-tp4099101p4099182.html
    Sent from the Accessibility mailing list archive at Nabble.com.

    --
    To unsubscribe e-mail to:
    accessibility+unsubscribe@global.libreoffice.org <javascript:;>
    Problems?
    http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
    Posting guidelines + more:
    http://wiki.documentfoundation.org/Netiquette
    List archive:
    http://listarchives.libreoffice.org/global/accessibility/
    All messages sent to this list will be publicly archived and
    cannot be deleted


--
To unsubscribe e-mail to: accessibility+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.