The table have : aria-labelledby="ls-question-text-49728X31X104" and role="group"
The head have the aria-hidden="true" because there are readable label
Each tr have the role="radiogroup" and aria-labelledby="answertext49728X31X104SQ01"
Each input have own label.

I can not do better …
Make clear proposition …

See : https://wave.webaim.org/report#/https://demo.sondages.me/49728?lang=fr#

The alert is about «A group of check boxes or radio buttons is not enclosed in a fieldset.» but we have the role action : check https://www.w3.org/WAI/tutorials/forms/grouping/#associating-related-controls-with-wai-aria

See : https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla/-/issues/39

PS : i test with ORCA on firefox … take time : but when navigate : we hear the good label and each only one time except the final one on each radio …
And with skelvanilla : we have the help and expression help by aria-describedby

Give a start of solution with good reason please.

The accessibilty experts says that in normal view the 'role' tag should be omitted, as long as it is a normal HTML formatted table. Only in the mobile view (when it is collapsed) it would apply.

But why ?
It still a radiogroup inside a group …
In mobile or not …

Clearly role are not realted to the diplay part,
It's related to the role …

If role is OK on mobile : it's same role on screen

table role her can not be used : https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Table_Role «the role as having a non-interactive table structure»

Here :we clearly have a group https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/group_role of radio-group https://developer.mozilla.org/en-US/docs/web/accessibility/aria/roles/radiogroup_role

Each line (tr) contain a radiogroup

See : https://validator.w3.org/nu/?doc=https%3A%2F%2Fdemo.sondages.me%2F49728%3Flang%3Dfr : no issue with role here.

(i need to delete the role on skip-navigation …)
Whole table contain group of each radiogroup

It's clearly a table with role group here :
We use aria to group control : https://www.w3.org/WAI/GL/wiki/Using_grouping_roles_to_identify_related_form_controls
With the related aria-labelledby

I can have a discussion with the accessibilty experts : it's not an issue.

I must fix skip-navigation … role before …
https://validator.w3.org/nu/?doc=https%3A%2F%2Fdemo.sondages.me%2F49728%3Flang%3Dfr
https://demo.sondages.me/49728?lang=fr#

And check https://wave.webaim.org/report#/https%3A%2F%2Fdemo.sondages.me%2F49728%3Fnewtest%3DY%26lang%3Dfr%23
Warning on fieldset, then : need role=group …

PR: https://github.com/LimeSurvey/LimeSurvey/pull/2504

There still no reason to remove role in array. Give me one link where you have an information where role=group must not be added ?

(and see there are no issue in webaim or w3C)

There are error on w3c for vanilla , https://validator.w3.org/nu/?doc=https%3A%2F%2Fshnoulle.limequery.com%2F49728%3Fnewtest%3DY%26lang%3Dfr
Not related to role=group … on table https://shnoulle.limequery.com/49728?newtest=Y&lang=fr

PR: https://github.com/LimeSurvey/LimeSurvey/pull/2504

Broken : invalid w3c : https://demo.sondages.pro/464896?newtest=Y&lang=fr#
https://validator.w3.org/nu/?doc=https%3A%2F%2Fdemo.sondages.pro%2F464896%3Fnewtest%3DY%26lang%3Dfr
https://wave.webaim.org/report#/https%3A%2F%2Fdemo.sondages.pro%2F464896%3Fnewtest%3DY%26lang%3Dfr%23 : missing fieldset, replaced by radiogroup : https://www.w3.org/WAI/tutorials/forms/grouping/#associating-related-controls-with-wai-aria

role=presentation : seems better (some a11y specialist advice)
https://validator.w3.org/nu/?doc=https%3A%2F%2Fdemo.sondages.pro%2F49728%3Fnewtest%3DY%26lang%3Dfr
https://wave.webaim.org/report#/https%3A%2F%2Fdemo.sondages.pro%2F49728%3Fnewtest%3DY%26lang%3Dfr%23 : missing fieldset, replaced by radiogroup : https://www.w3.org/WAI/tutorials/forms/grouping/#associating-related-controls-with-wai-aria

no roles + remove role=radiogroup
https://demo.sondages.pro/184865?newtest=Y&lang=fr#
w3c valide https://demo.sondages.pro/184865?newtest=Y&lang=fr#
https://wave.webaim.org/report#/https%3A%2F%2Fdemo.sondages.pro%2F184865%3Fnewtest%3DY%26lang%3Dfr%23 missing fieldset NOT replaced then no grouping

Since i have another solution
and current PR broke HTML validity
I take it.

To be done

1. Replace role="group" by role="presentation"
2. Remove the thead
3. Replace all th by td

See https://www.w3.org/WAI/WCAG21/Techniques/failures/F46

For RGAA (French) we need to remove colgroup : there are an issue open : https://github.com/DISIC/RGAA/issues/111

Must respect WCAG Criterion right ?

There are an issue with NVDA : depend on configuration
The input need an aria-labelledby is own label.

Can be tested here : https://master.sondages.pro/932473?newtest=Y&lang=en
(with last skelvanilla)

About layout table (table role="presentation")
Show as warning in WEBAIM

WAVE Web Accessibility Evaluation Tool
powered by
WebAIM
Address:
Styles:OFFON
Reference

*Layout table
What It Means
A layout table is present.
Why It Matters
Layout tables exist merely to position content visually - to create columns, insert spacing, or align content neatly for sighted users. Their content is not at all tabular in nature. Layout tables should not be used in HTML5. They can introduce reading and navigation order issues. Screen readers may interpret them as data tables (i.e., announcing column and row numbers), especially if they contain table header (<th>) cells. This introduces significant overhead on screen reader users.
What To Do
In almost every case, layout tables can be replaced with other HTML elements and styled with CSS to achieve the desired visual presentation. If the table contains tabular data, provide appropriate header (<th>) cells. If the layout table remains, verify that the reading and navigation order of table content (based on underlying source code order) is logical and give it role="presentation" to ensure it is not identified as a table to screen reader users.
The Algorithm... in English
A <table> element is present that does not contain any header (<th>) cells.

Maybe need role=group wrapper on each multiple question …

Thank you - will show it to the expert and get feedback.

Is this in the last skelvanilla release already? That would be the easiest way to test for us.

@DenisChenu ?

Just come back from holiday …

It's a master LimeSurvey fix …

I can update https://github.com/encuestabizdevgit/extends_extends_skelvanilla_accessibility

https://github.com/encuestabizdevgit/extends_extends_skelvanilla_accessibility/tree/tablerole

@DenisChenu Can you check Cliq?

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&amp;id=33667

Fixed in Release 5.3.27+220725

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&amp;id=33683

For DEV : https://github.com/LimeSurvey/LimeSurvey/tree/develop

• create a fork of skelvanilla

@ollehar and @c_schmitz : for your client : https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla/-/tree/tablerole

Not compatible with 3.X (no row … ).

Reverted
Wit for BS5 ready to create a new pull request for core.

develop : https://github.com/LimeSurvey/LimeSurvey/pull/2839
Draft currently

I hesitate between 2 solutions, both pass the (basic) RGAA and WCAG tests. But I wonder what is the best solution for users.

I ask on a french forum : https://forum.alsacreations.com/topic-6-90205-1-Champs-de-formulaire-en-tableau-LimeSurvey.html and on https://groupes.renater.fr/sympa/info/rgaa mailing liste (waiting for moderation).

The 2 solutions are here

• using role="presentation" : https://www.shnoulle.net/test/arrayWCAG/tableau_role-presentation.html
• using default role : https://www.shnoulle.net/test/arrayWCAG/tableau_role-table.html
• using default role but hide default label for screen reader : https://www.shnoulle.net/test/arrayWCAG/tableau_role-table-2.html

default role make less update but i think presentation role is better for screen reader : i think same string label is read more than one time for each input … : one time for label and one for time for header.

If anybody can test it can be interesting.

Other ideas

role=presentation : https://www.shnoulle.net/test/arrayWCAG/tableau_role-presentation.html
role=table 1 : https://www.shnoulle.net/test/arrayWCAG/tableau_role-table.html
role=table 2 https://www.shnoulle.net/test/arrayWCAG/tableau_role-table-2.html

For role=presentation : i need to move col with to cell width.

It make a lot of work …

Let's go for table role with columnheader and hidden label

https://github.com/LimeSurvey/LimeSurvey/pull/2888

Last time : Olle tell me you work more on this.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&amp;id=34427