New E-learning
Data Entry Field
A data entry field allows the learner to freely type in data using the keyboard (word, sentence, number). It must always be paired with a visible, explicit label, along with guidance on the expected format and, in the event of an error, an understandable message.
Two variants in Storyline 360
- Text Entry: free alphanumeric input (word, sentence, short text).
- Numeric Entry: input restricted to digits (amount, duration, calculation result).
Structural point of caution
The data entry field is announced as an edit region by assistive technologies, but its visible label is never programmatically associated with the field in Storyline. The accessible name must therefore be entered manually for each field (see the Accessibility section).
When to use a data entry field
- Short open-ended answer: keyword, number, date, technical term to be recalled.
- Personalizing the module: the learner's first name reused later via a variable.
- Free-recall question, when finding the answer in a list would be too easy
When not to use a data entry field
- An answer to be chosen from a known, closed set: use radio buttons, checkboxes, or a choice list.
- A written answer with no possible automatic correction: provide for self-assessment or submission outside the module.
- Input sensitive to spelling, case, or accents with no configured tolerance.
Implementation
- Go to Insert → Data Entry
- Choose "Text Entry" or "Numeric Entry"
- Draw the insertion area on the slide
- Rename the automatically generated variable (TextEntry, TextEntry1…) with an explicit name: maintenance, triggers, and review all depend on it
Accessible name (mandatory)
- Right-click the field → "Accessibility…"
- Check that the object is visible to accessibility tools
- Enter the Alt text (also editable from the Focus Order panel)
- Since the visible label placed next to the field is not programmatically linked to it, the Alt text must repeat that label exactly, without abbreviating or contradicting it.
- A field with no Alt text is announced using the object's name in the timeline ("TextEntry1"): not compliant.
Label and input help
- Visible, permanent label, placed above the field.
- Never use the field's default text as the sole label: it disappears as soon as typing starts and must be cleared by the learner.
- State before the field the expected format, unit, maximum length, and whether it is mandatory, in text rather than through an asterisk alone.
Input validation and error handling
- Explicit text error message, never conveyed by color or an icon alone.
- State the nature of the error and the expected correction ("Enter a number between 1 and 10").
- Always allow a new attempt without losing the input already entered.
- For text-entry questions: list all accepted variants (case, accents, singular/plural, abbreviations). Do not penalize a spelling mistake when the learning objective concerns the substance of the answer.
Structural rules
- A single input objective per slide; visually group each field with its label.
- Do not ask again for information already provided: reuse the variable (%FirstName%).
- No time limit on an entry; if a time constraint exists, it must be extendable or disableable.
On this page
Keyboard interaction
The tab order must follow the visual logic: label above the field, progression from top to bottom.
| Key | Function |
|---|---|
| Tab/Shift+Tab |
|
| Space/Enter | activate the "Submit" button » |