Scribus Forums

Scribus => PDF Generation => Topic started by: micro on January 26, 2021, 04:16:42 AM

Title: Incorrect tab order for radio buttons
Post by: micro on January 26, 2021, 04:16:42 AM
Scribus 1.5 introduced the PDF form radio button - a welcome addition.

Grouping several radio buttons makes them act properly - e.g. selecting a button will automatically deselect other buttons in the same group. Also the left/right arrow keys can be used to change the selected button once the user has clicked one of the buttons. So far so good.

However tabbing to the radio buttons from another field (e.g. text box or checkbox) does not respect the Level assigned to the radio button group; instead the radio button gets tabbed into only after all other text / checkboxes / combo boxes / list boxes. If there are multiple radio button groups, the tab order does respect the relative Levels of the 2 groups, but they are only tabbed to after all other form fields including those assigned lower levels.

I have attached a simple .sla & corresponding exported .pdf as an example. The tab order according to Levels assigned should go:


However tabbing through the exported PDF yields the following order:


Providing proper tab order control is important for usability and accessibility.

I realise this is a new feature in development. Just reporting my observations. Happy to report as a bug if that is recommended and appropriate.


[attachment deleted by admin]
Title: Re: Incorrect tab order for radio buttons
Post by: micro on June 03, 2021, 04:03:34 AM
No replies in 4 months so I guess this is a low priority issue for most.

Our business will not publish interactive forms without correct tab order, meaning the great effort put into Scribus for proper radio buttons is unfortunately of no use to us until this issue is resolved. We consider accessibility and usability mandatory requirements.

I've now opened a bug on this:

https://bugs.scribus.net/view.php?id=16579
Title: Re: Incorrect tab order for radio buttons
Post by: micro on June 07, 2021, 01:29:36 PM
I can confirm this is now fixed in the latest 1.5.8svn - sensational!

Many thanks to jghali.