🇬🇧 Hello LimeSurvey community,I would like to share a project we are currently working on at the University of Lille in France.We are developing an optimized LimeSurvey theme called AllySurvey, based on the native LimeSurvey theme structure, with a strong focus on digital accessibility.The objective is to improve the user experience of LimeSurvey questionnaires for all users, including people with disabilities, by aligning the theme as much as possible with the French accessibility framework RGAA 4.1 and international WCAG 2.1 A/AA recommendations.This work is mainly intended for use in the higher education and research sector, where LimeSurvey is widely used for surveys, institutional forms, research questionnaires, student feedback, administrative procedures and teaching-related evaluations.The current version we are working on is AllySurvey 2.76+.Main areas of improvement include:

• better keyboard navigation;
• improved focus visibility;
• skip links and semantic structure improvements;
• improved form field readability;
• clearer error messages and mandatory field indications;
• better support for screen readers;
• improved contrast and visual readability;
• responsive/mobile accessibility improvements;
• accessibility toolbar for users;
• progressive improvements on complex question types.

The goal is not to replace a full accessibility audit of each final survey, because accessibility also depends on the questionnaire content, wording, configuration and question types used. However, we hope this theme can provide a stronger and more accessible base for LimeSurvey users.The project is currently available on GitHub:
github.com/LecerfRaphael/limesurvey-ally...lille-rgaa/tree/main We would be very happy to receive feedback from the LimeSurvey community, especially from developers, accessibility experts, universities and organizations using LimeSurvey in public sector or education contexts.If this work can be useful to the project, we would also be interested in discussing how some accessibility improvements could potentially inspire future native LimeSurvey enhancements.Thank you for your work on LimeSurvey and for keeping this important open source tool alive.Best regards,
Raphaël Lecerf
University of Lille
Digital Department / DAWAM Service

___________________________________________________________________________________________________________________________________
 🇫🇷 Bonjour à toutes et à tous,Je souhaite partager avec la communauté LimeSurvey un projet actuellement mené à l’Université de Lille.Nous travaillons sur un thème LimeSurvey optimisé pour l’accessibilité numérique, nommé AllySurvey, avec pour objectif d’améliorer l’expérience utilisateur des questionnaires en ligne, notamment pour les personnes en situation de handicap.Ce travail s’appuie sur les bonnes pratiques du RGAA 4.1 et des recommandations WCAG 2.1 niveaux A et AA.Le thème est principalement pensé pour les usages de l’enseignement supérieur et de la recherche, où LimeSurvey est largement utilisé pour les enquêtes institutionnelles, les questionnaires pédagogiques, les travaux de recherche, les évaluations, les démarches administratives ou encore les retours utilisateurs.La version actuellement en cours de diffusion est AllySurvey 2.76+.Les principaux axes d’amélioration portent notamment sur :

• la navigation au clavier ;
• la visibilité du focus ;
• les liens d’évitement ;
• la structure sémantique HTML ;
• la lisibilité des champs de formulaire ;
• les messages d’erreur et champs obligatoires ;
• la compatibilité avec les lecteurs d’écran ;
• les contrastes et la lisibilité visuelle ;
• l’affichage mobile ;
• l’ajout d’une barre d’accessibilité ;
• l’amélioration progressive de certains types de questions complexes.

Ce thème ne remplace évidemment pas un audit complet d’un questionnaire final, car l’accessibilité dépend aussi du contenu, du paramétrage, des consignes rédigées et des types de questions utilisés. Il vise toutefois à fournir une base plus robuste et plus accessible pour les utilisateurs de LimeSurvey.Le projet est disponible sur GitHub :
github.com/LecerfRaphael/limesurvey-ally...lille-rgaa/tree/main Nous serions très intéressés par les retours de la communauté LimeSurvey : développeurs, référents accessibilité, universités, établissements publics ou structures utilisant LimeSurvey dans un contexte institutionnel.Si certains éléments peuvent être utiles au projet LimeSurvey, nous serions également ravis d’échanger sur la manière dont ces améliorations pourraient inspirer de futures évolutions natives de l’outil.Merci à la communauté et aux mainteneurs pour leur travail autour de LimeSurvey.Bien cordialement,
Raphaël Lecerf
Université de Lille
Direction du numérique / Service DAWAM

Very interesting, but I don't think this has anything to do with "Comfort Update". I might move this to "Development", I think that is the better forum.

Good evening. Thank you @Holch, indeed the post is in a better category.
Have a good evening.

Great, a new one !
I have to test it more completly

I see some improvement for  LimeSurvey core too, for example, in my opinion:

• Les dates sont présentées sous forme de trois champs clairs : Jour / Mois / Année. : the option already exists in LimeSurvey, why not use it directly ?
• Email, phone, etc. input: Why not use question theme here? I know it's not a theme system, but clearly, same purpose. See  EmailInput  for an example.
• Option “Autre, précisez” : my opinion : must be reported and fixed in core
• Tableaux, matrices et questions complexes : please, this need to be fixed in the core too. (and work for near whole HTML in subquestoions)
• About aria-described, we don't use same solution. I think have aria-descibed directly in HTML is the way to do. The issue is reported in mantis
• About initRankingQuestionsA11y: Please, can you check if it can be in core ? In my opinion : we must add a "Show dropdown" for acccessibility : just show a button at start :  github.com/LecerfRaphael/limesurvey-ally...cessibilite.js#L3884 . I have an RGAA reported about HTML shown ifor screen reader are not the same than not screen reader. Unsure on the best way to fix here. I have this quetsion theme too :  rankingDropDown  (not 7.X checked)
• Wrning for the fieldset/legfen system, if Survey mlanager add some tag in quetsiontext : the survey are not valid . I use an option here to use header, i think i add an option to use fieldset/label
• About  github.com/LecerfRaphael/limesurvey-ally...tructure-required.js , see  skelvanilla system  for usage of custom validity. But I set it as an option because using validity disable save when error

I look further and do some test, but please :if you can report and/or contribute to improve LimeSurvey core, it can be great.

Hello
New version template independant Limesurvey 6/7
[Theme release] AllySurvey V2.85 – Accessible standalone theme for LimeSurvey 6

forums.limesurvey.org/forum/development/...eme-for-limesurvey-6

Good Day
Raphaël

Hello
New version template independant Limesurvey 6/7
[Theme release] AllySurvey V2.85 – Accessible standalone theme for LimeSurvey 6

forums.limesurvey.org/forum/development/...eme-for-limesurvey-6

Good Day
Raphaël

♿🚀 The AllySurvey 2.85 LimeSurvey theme keeps evolving!

Hello everyone,
The accessible theme for LimeSurvey is gaining new options designed to simplify questionnaire administration... without needing to directly modify the template code. 👨‍💻

New features now available include:
⏱️ Session management
Session duration and warning times can be customized directly within the theme options.

 


🌍 Option language
Theme settings adapt to the LimeSurvey administration language, including new wording available in French.

 

💬 Custom messages
You can now directly define:
• the message displayed when a questionnaire is closed;
• a custom error message.

A particularly handy feature for real-world scenarios. For example:
"Due to a high volume of registrations, the questionnaire is temporarily suspended. Please check back on this page in a few days."
No more need to add specific conditions or hard-code the text into a theme Twig file. 👍

 

📧 Independent support contact
The support contact's name and email address can differ from those of the questionnaire administrator.

🖼️ Image management via options
Logos, background images, footer illustrations, or images associated with messages can be uploaded directly through the theme settings.

 

🔗 Iframe embed code generation
AllySurvey 2.85 also makes it easier to embed a questionnaire into another website by generating an iframe code that is ready to copy and paste.

The goal remains the same: making LimeSurvey easier to administer, more flexible to customize, and—above all—more accessible, while minimizing technical modifications made directly to the theme files. ♿💻

 

Small administrative features that can save a lot of time on a daily basis! 😊

➡️ More info on GitHub: github.com/LecerfRaphael/AllySurvey2.85

Have a good day

Raphael

Hi,

My personal opinion : a lot part are clearly out of theme management system ! And you are not sure it work on real situation.

For example: session issue (and there are a plugin for this) or iframe system.

My opinion : You are creating a custom template tailored to your specific needs.
However, this deviates from the RGAA template’s intended purpose, so it will be less useful for everyone, harder to maintain over the long term, and more difficult to get external contributions for.

For information, I am currently working on an RGAA template project (reviewed by tanaguru), with two goals: to make as many corrections as possible to the core of LimeSurvey, and, when that is not possible, to include the correction in the template.