| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 20487 | Bug reports | Accessibility | public | 2026-04-13 15:26 | 2026-04-14 08:57 |
| Reporter | buhtz | Assigned To | |||
| Priority | none | Severity | feature | ||
| Status | new | Resolution | open | ||
| Summary | 20487: Format of "Non-numerical answer option prefix" not specified to users | ||||
| Description | Hello, I tried to set it to another value and got the message that the format does not fit or need to be right. But I don't know what the format is because the error message does not tell it. Expected behavior: Sidenote: On my system the prefix is by default set to "AO" (two letters). I am not sure if this is default to LimeSurvey or just to my instance. If it is upstream default please take it as an extra bug report. The prefix is followed by numbers; e.g. "AO01" (letter A, letter O, number 0, number 1). Having letter O and number 0 side by side makes it hard to read. | ||||
| Additional Information | LimeSurvey 6.16.2 on my universities server where I am not the admin | ||||
| Tags | No tags attached. | ||||
| Bug heat | 2 | ||||
| Complete LimeSurvey version number (& build) | 6.16.16+260408 | ||||
| I will donate to the project if issue is resolved | |||||
| Browser | |||||
| Database type & version | |||||
| Server OS (if known) | |||||
| Webserver software & version (if known) | |||||
| PHP Version | |||||
 |
I agree the format is not communicated to the user in any way. looking at the markup, it must meet the pattern [A-Za-z]{0,3} so lowercase/uppercase letters zero to three characters long |
|
|
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input "Note: If using the pattern attribute, inform the user about the expected format by including explanatory text nearby. You can also include a title attribute to explain what the requirements are to match the pattern; most browsers will display this title as a tooltip. The visible explanation is required for accessibility. The tooltip is an enhancement." So, two issues here. No feedback for any user (could be explanatory text and optionally title attribute). Also breaks accessibility (must have explanatory text, title attribute is not acceptable) |
|
|
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/pattern Usability and accessibility considerations Only relying on the title attribute for the visual display of text content is discouraged, as many user agents do not expose the attribute in an accessible manner. Although some browsers show a tooltip when an element with a title is hovered, that leaves out keyboard-only and touch-only users. This is one of the several reasons you must include information informing users how to fill out the control to match the requirements. While titles are used by some browsers to populate error messaging, because browsers sometimes also show the title as text on hover, it therefore shows in non-error situations, so be careful not to word titles as if an error has occurred. |
|
|
bug, not feature request |
