Denis Chenu

> Ehm, I think disabling buttons that do nothing is a bit more UX friendly. I really don't think since the button is after the selection. Maybe adding customValidity then....

> Disabled buttons can have a tooltip to explain why, we do this in some places. Not sure it's worth it here... tooltip is not shown … see https://designsystem.digital.gov/components/tooltip/ don't...

Fixed in https://github.com/LimeSurvey/LimeSurvey/pull/2533

> Expiry date for the password is something that maybe should be part of the password requirment plugin, imho. Warning : all password system are linkend to AuthDB only ....

> > a field to set an expiry date for the user > > I would not implement this. However, a simple field/toggle to enable/disable a user would be of...

> Is the user expiring, or the password? User acces via AuthDB … not via other authentication method …

Don't ask mle to review something i'm not OK. Else : if you have a aria-labelledby : you need a role=group

Need more work I test a solution with role="presentation" currently : But with this one : https://validator.w3.org/nu/?doc=https%3A%2F%2Fdemo.sondages.pro%2F464896%3Fnewtest%3DY%26lang%3Dfr _Error: The role attribute must not be used on a tr element which...

Alt solution : https://demo.sondages.pro/49728?newtest=Y&lang=fr# role="presentation" for table, remove all thead and th to have really a table deicated to presentation. @c-schmitz can you ask ?

Replace by https://github.com/LimeSurvey/LimeSurvey/pull/2512