View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20049 | Bug reports | Accessibility | public | 2025-04-05 12:03 | 2026-10-29 17:03 |
| Reporter | OMdev | Assigned To | c_schmitz | ||
| Priority | none | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Product Version | 6.6.x | ||||
| Summary | 20049: When the question error appears, the screen reader does not read out the error — that is a major problem. | ||||
| Description | This issue refers to a lack of accessibility for users who rely on screen readers. When a user encounters an error while answering a question (such as missing required fields or entering invalid input), the error message is displayed visually but not announced by the screen reader. As a result, visually impaired users may not realize that an error has occurred or what action is needed to correct it. Ensuring that screen readers can detect and announce error messages is essential for creating an inclusive and accessible user experience. | ||||
| Steps To Reproduce | Steps to Reproduce
Expected ResultThe screen reader should read out the error messages when validation fails. Actual ResultThe screen reader does not read out the error messages, making it inaccessible for users relying on assistive technology. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 18 | ||||
| Complete LimeSurvey version number (& build) | Version 6.5.2+240402 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | Chrome | ||||
| Database type & version | NA | ||||
| Server OS (if known) | |||||
| Webserver software & version (if known) | |||||
| PHP Version | NA | ||||
| Git branch / Pull Request URL | |||||
| related to | 19648 | closed | Add question help, Expressin dynamic help to aria-describedby | |
| related to | 09106 | in code review | c_schmitz | Add some 'error' in tite and list error before showing question |
| related to | 20327 | closed | c_schmitz | Vanilla Theme: Failing criterion 4.1.2 WCAG2 Level A - Validation modal window warning is not accessible |
|
@DenisChenu, this may be of interest for you as well. We had a client testing their survey for accessibility standards. If there are multiple unanswered mandatory questions, the screen reader reads the errors in one go and the reference to the affected question is missing so you do not really know which question to check. |
|
|
@tibor.pacalat, we can reproduce this issues. We were even told by some Limesurvey users that due to strict WCAG regulations this is a show stopper for their projects. |
|
|
There are 2 solution
Unsure on the best choice. Skelvanilla 6 don't have all previous feature (skelvanilla 5) but this one work. |
|
|
Confirmed in 6.15.5 - (rif:id.21) WCAG2 Level A - Principle violation 4.1.2 https://www.w3.org/TR/WCAG21/#name-role-value |
|
|
The error popup is now read out by screen readers. The list of errors at the top of the page, and each field announcing its own error, come with PR #5421 in the next minor version. |
|
|
Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=41131 |
|
|
Fixed in Release 7.9.0+261029 |
|
|
LimeSurvey: master 359ccdc3 2026-10-28 14:26 Details Diff |
Fixed issue 20049: Screen readers did not read out the error popup shown when a mandatory question was not answered or an answer was invalid Dev The alert modal gets tabindex="-1" so Bootstrap moves the focus into it, aria-labelledby/aria-describedby point to its title and message (Vanilla and Fruity TwentyThree both use these TemplateConfig attributes) Dev The rest of the issue (error summary, aria-invalid/aria-describedby on the inputs, focus after the popup is closed) is fixed in PR #5421 on develop-minor |
Affected Issues 20049 |
|
| mod - application/models/TemplateConfig.php | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-05 12:03 | OMdev | New Issue | |
| 2025-04-05 13:55 | Mazi | Note Added: 82375 | |
| 2025-04-05 13:55 | Mazi | Bug heat | 0 => 2 |
| 2025-04-10 10:35 | Mazi | Note Added: 82409 | |
| 2025-04-10 15:13 | DenisChenu | Note Added: 82411 | |
| 2025-04-10 15:13 | DenisChenu | Bug heat | 2 => 4 |
| 2025-04-10 15:14 | DenisChenu | Note Added: 82412 | |
| 2025-04-10 15:14 | DenisChenu | Relationship added | related to 19648 |
| 2025-08-07 13:58 | guest | Bug heat | 4 => 10 |
| 2025-08-07 14:07 | tassoman | Note Added: 83186 | |
| 2025-08-07 14:07 | tassoman | Bug heat | 10 => 12 |
| 2025-09-11 22:35 | segui | Issue Monitored: segui | |
| 2025-09-11 22:35 | segui | Bug heat | 12 => 14 |
| 2026-10-28 14:26 | c_schmitz | Note Added: 86925 | |
| 2026-10-28 14:26 | c_schmitz | Bug heat | 14 => 16 |
| 2026-10-28 14:27 | c_schmitz | Changeset attached | => LimeSurvey master 359ccdc3 |
| 2026-10-28 14:27 | c_schmitz | Note Added: 86926 | |
| 2026-10-28 14:27 | c_schmitz | Assigned To | => c_schmitz |
| 2026-10-28 14:27 | c_schmitz | Status | new => resolved |
| 2026-10-28 14:27 | c_schmitz | Resolution | open => fixed |
| 2026-10-28 14:27 | c_schmitz | Relationship added | related to 09106 |
| 2026-10-29 14:42 | LimeBot | Note Added: 86942 | |
| 2026-10-29 14:42 | LimeBot | Status | resolved => closed |
| 2026-10-29 14:42 | LimeBot | Bug heat | 16 => 18 |
| 2026-10-29 17:03 | c_schmitz | Relationship added | related to 20327 |