sergei-maertens
commented
1 year ago I want to use this user story to simplify and remove WYSIWYG options from this configuration, since it leads to invalid markup and hence styling issues with the "required" asterisks.
When I looked into this, there was no reason to use a template tag for this instead of a plain variable. This should simply produce a template with {{ privacy_url|urlize }} or similar in there.
There are also further accessibility issues with including interactive elements (like a link) inside the label of a checkbox (or form field in general), as clicking the label is linked to the input. The recommendations are to put the link below the label in a separate description field.
None of this is currently technically possible, mind you.
joeribekker
Thema / Theme
Frontend
Omschrijving / Description
The website containing the privacy policy of our municipality is called 'privacyverklaring', hence this is how we would like to refer to it throughout the forms. However, it is currently statically determined to be called 'privacybeleid' - as-in, the obligatory { % privacy_policy % } tag in the privacy policy field statically prints 'privacybeleid'.
Added value / Toegevoegde waarde
No response
Aanvullende opmerkingen / Additional context
It is possible to change it with a workaround, though in this case the link doesn't correspond to the 'Privacybeleid URL' field anymore making it potentially confusing in case the OF-instance is managed by multiple users.