In a synthetic nested-dialog flow, closing a child returns focus to its parent correctly, but closing the parent leaves no visible focus because its original trigger was replaced.
Product and software research / Survey guide
Product and software research · A focused questionnaire
Nested dialog focus return survey
Understand focus recovery when a child dialog and its parent close in separate steps.
Opens product registration. Example questions are not imported automatically.
PLAN A BOUNDED FOLLOW-UP
Define separate return targets for the two closures and an explicit fallback when the original trigger no longer exists; verify the sequence with keyboard testing.
After the change, ask users to describe focus after each closure, including the replaced-trigger case. Record failures separately for child and parent transitions; a successful survey response is not an accessibility certification.
Synthetic planning example. A repeat survey alone does not establish causation.
From question to next step
Make the feedback useful.
Set the decision
Understand focus recovery when a child dialog and its parent close in separate steps.
Invite relevant voices
Ask immediately after the person closes a child dialog and then its parent. Include a separate test where the parent’s original trigger is removed or replaced; record observed focus at each closure.
Choose an action
Define separate return targets for the two closures and an explicit fallback when the original trigger no longer exists; verify the sequence with keyboard testing.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
In a synthetic nested-dialog flow, closing a child returns focus to its parent correctly, but closing the parent leaves no visible focus because its original trigger was replaced.
Choose an action to test
Define separate return targets for the two closures and an explicit fallback when the original trigger no longer exists; verify the sequence with keyboard testing.
Check the experience again
After the change, ask users to describe focus after each closure, including the replaced-trigger case. Record failures separately for child and parent transitions; a successful survey response is not an accessibility certification.
A useful starting point
Record the focus destination after each closure.
A nested dialog has two closure transitions to investigate. Returning from a child to its parent may work while the later return to the main page fails. These prompts keep the transitions separate and identify the case where the original trigger no longer exists.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
After closing a child dialog, which control in its still-open parent did you expect to receive focus?
Record the intended return point inside the parent and the observed destination. This separates recovery from a child dialog from the later return to the main page.
What happened to keyboard navigation after you closed the parent dialog as well?
Trace the second closure independently: readers may recover correctly inside the parent but lose their place when it closes. Keep the two transitions distinct in the investigation.
Which step lost the trigger control because it had been removed or replaced?
Identify a removed or replaced trigger so the interface team can investigate an explicit fallback destination. Do not assume focus can return to an element that no longer exists.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. After closing a child dialog, which control in its still-open parent did you expect to receive focus? What happened to keyboard navigation after you closed the parent dialog as well? Which step lost the trigger control because it had been removed or replaced?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| After closing a child dialog, which control in its still-open parent did you expect to receive focus? | Optional written explanation; none or not applicable accepted | Record the intended return point inside the parent and the observed destination. This separates recovery from a child dialog from the later return to the main page. |
| What happened to keyboard navigation after you closed the parent dialog as well? | Optional written explanation; none or not applicable accepted | Trace the second closure independently: readers may recover correctly inside the parent but lose their place when it closes. Keep the two transitions distinct in the investigation. |
| Which step lost the trigger control because it had been removed or replaced? | Optional written explanation; none or not applicable accepted | Identify a removed or replaced trigger so the interface team can investigate an explicit fallback destination. Do not assume focus can return to an element that no longer exists. |
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.
Read the answers carefully
What these answers cannot establish.
Ask about the specific dialog sequence and accept not applicable. User feedback does not replace keyboard testing or certify accessibility compliance.
In a synthetic nested-dialog flow, closing a child returns focus to its parent correctly, but closing the parent leaves no visible focus because its original trigger was replaced. Ask about the specific dialog sequence and accept not applicable. User feedback does not replace keyboard testing or certify accessibility compliance.
Before you send it
Check what your wording assumes.
Did keyboard navigation work?
What happened to keyboard navigation after you closed the parent dialog as well?
The prompt names the second transition in a nested flow instead of duplicating the broad keyboard-navigation guide.
Before you send it
Questions, answered.
Who should receive this questionnaire?
Keyboard users who tried a child-and-parent dialog sequence and interface owners investigating the return destinations. Include only the steps each person encountered; voluntary responses do not establish a representative sample.
When should I ask these questions?
Ask immediately after the person closes a child dialog and then its parent. Include a separate test where the parent’s original trigger is removed or replaced; record observed focus at each closure.
What does “After closing a child dialog, which control in its still-open parent did you expect to receive focus?” help investigate?
Record the intended return point inside the parent and the observed destination. This separates recovery from a child dialog from the later return to the main page.
What does “What happened to keyboard navigation after you closed the parent dialog as well?” help investigate?
Trace the second closure independently: readers may recover correctly inside the parent but lose their place when it closes. Keep the two transitions distinct in the investigation.
What does “Which step lost the trigger control because it had been removed or replaced?” help investigate?
Identify a removed or replaced trigger so the interface team can investigate an explicit fallback destination. Do not assume focus can return to an element that no longer exists.
What would a practical follow-up look like?
Define separate return targets for the two closures and an explicit fallback when the original trigger no longer exists; verify the sequence with keyboard testing. After the change, ask users to describe focus after each closure, including the replaced-trigger case. Record failures separately for child and parent transitions; a successful survey response is not an accessibility certification.
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.
Inside the product
Create a manual draft and check the questions
The real SurveyTeams screenshot shows a separate labelled synthetic event survey. It demonstrates the manual builder, not this questionnaire already loaded and not the task described in the software being evaluated.
- Create a manual draft and explain its purpose: Understand focus recovery when a child dialog and its parent close in separate steps.
- Copy or select only applicable questions from this page. Add them as optional text prompts; the download is an editorial definition, not a product importer.
- Check the respondent preview, allow none or not applicable, and apply this handling limit: Ask about the specific dialog sequence and accept not applicable. User feedback does not replace keyboard testing or certify accessibility compliance.
Creation and preview were exercised in the observed account. Distribution, results and other features are separate workflows and depend on account conditions.
Build with SurveyTeams
Draft your own nested dialog focus return 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