Which control lacked a useful name?
A control lacking a useful name identifies an accessible label that does not communicate its action or purpose. Review its actual task context with assistive technology.
Product and software research / Survey guide
Product and software research · Practical survey guide
Screen reader labeling survey
Find missing context in spoken interface labels.
Opens product registration. Example questions are not imported automatically.
FOLLOW THE FEEDBACK
- Understand the context
Which control lacked a useful name?
- Investigate the friction
What information was announced unexpectedly?
- Choose a next check
What label would clarify the action?
A planning aid, not automated analysis of your answers.
A useful starting point
Questions to understand the actual experience.
Find missing context in spoken interface labels. Use the prompts relevant to your audience and allow people to skip situations they did not encounter. Keep response handling consistent with what you explain in the invitation.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
What information was announced unexpectedly?
An unexpected announcement identifies spoken context that differs from the control's intended purpose or state. Review accessible names and timing in the actual task, without claiming conformance from one assistive-technology observation.
What label would clarify the action?
A clarifying label identifies wording needed to distinguish a control's action and context. Check the accessible name and behavior rather than claiming conformance from a suggested label.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which control lacked a useful name? What information was announced unexpectedly? What label would clarify the action?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Repeated unnamed buttons are difficult to distinguish.
Choose an action to test
Give controls action-specific accessible names.
Check the experience again
After trying the change, repeat “Which control lacked a useful name?” with people who experienced it. Check whether they still describe the original issue: repeated unnamed buttons are difficult to distinguish. Compare explanations and sample context, rather than claiming the change caused an improvement.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which control lacked a useful name? | Optional short text | Retain the specific point or condition described; avoid replacing it with an unexplained rating. |
| What information was announced unexpectedly? | Optional written explanation | Keep context that distinguishes different experiences. Do not request disability diagnoses. |
| What label would clarify the action? | Optional improvement suggestion | Keep the suggested change separate from whether it has been tested. Give controls action-specific accessible names. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Before you send it
Check what your wording assumes.
Would you agree that everything about screen reader labeling was clear and easy?
Which control lacked a useful name?
The first wording combines an assumed positive outcome with two different judgments. The revised prompt asks about a specific experience and permits an inconvenient or uncertain answer.
From question to next step
Make the feedback useful.
Set the decision
Start with the decision: Find missing context in spoken interface labels.
Invite relevant voices
Invite people with relevant experience. Ask after someone has encountered the situation described in “Which control lacked a useful name?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
Choose an action
Give controls action-specific accessible names.
Read the answers carefully
Keep the conclusion within the evidence.
Do not request disability diagnoses.
Repeated unnamed buttons are difficult to distinguish. This is a synthetic example, not a customer result. Do not request disability diagnoses.
Before you send it
Questions, answered.
Who should receive this questionnaire?
Product users who attempted the described task. Ask only about steps each person encountered; do not treat a voluntary response sample as representative.
When should I ask these questions?
Ask after someone has encountered the situation described in “Which control lacked a useful name?”, while they can still recall the details. For material testing, show the actual draft first; for planning, ask before the next relevant activity.
What should I investigate in the answers?
Repeated unnamed buttons are difficult to distinguish. This is an illustrative pattern to look for, not a claim about your respondents. Do not request disability diagnoses.
What would a practical follow-up look like?
Give controls action-specific accessible names. After trying the change, repeat “Which control lacked a useful name?” with people who experienced it. Check whether they still describe the original issue: repeated unnamed buttons are difficult to distinguish. Compare explanations and sample context, rather than claiming the change caused an improvement.
How should I ask “What information was announced unexpectedly?”?
An unexpected announcement identifies spoken context that differs from the control's intended purpose or state. Review accessible names and timing in the actual task, without claiming conformance from one assistive-technology observation. Use an optional written explanation when predefined choices would hide relevant context.
Can I use the questions in SurveyTeams?
Copy the prompts or download TXT, CSV, JSON, or a Markdown worksheet, then adapt them in your own survey. The CTA opens registration; it does not import this example automatically. Verify available features in your account.
Build with SurveyTeams
Draft your own screen reader labeling questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗Continue exploring