Childcare Enrollment Form Review: Phone and Keyboard Checklist
- Test a complete fictional journey on a phone and with a keyboard.
- Record errors, recovery and the exact meaning of confirmation.
- Use this as an initial review and arrange deeper accessibility evaluation.
Review a childcare enrollment form by completing a realistic application, deliberately making a mistake, and checking what happens next. Use a phone and a keyboard-only pass. A form can look clear on a large screen while hiding a required field, an error message or the final button on a smaller one.
Download the editable CSV worksheet.
Use fictional information in a test environment. Arrange a safe test route before a step that would reserve a real place, charge money or send a message to a family. This checklist is a practical first review, not a complete accessibility audit or certification.
Write the journey before testing
List what a family needs before starting, each form step, any review stage and the exact event that confirms a place. Record whether a submitted form creates a request or a confirmed booking. Your test should finish with that distinction clear.
Check that every requested field has a purpose. The W3C forms tutorial recommends short, simple forms that request relevant information. A question staff might find interesting is not automatically necessary at registration.
Walk through on a phone
Use the form at a normal phone width, then enlarge the text and repeat the important steps. Check the visible form, any help text, errors and confirmation. The W3C explanation of text resizing describes retaining content and functionality when text is enlarged.
| Check | Pass evidence to record |
|---|---|
| Session and price | The selected session, dates and complete price remain understandable |
| Labels | Each field has a visible, meaningful label |
| Instructions | Format examples and required-field instructions appear before submission |
| Long content | Text is readable and controls are not covered or clipped |
| Upload, if required | The supported file choices and recovery from failure are clear |
| Final action | The button says what happens next |
| Confirmation | The status and next step match the submitted request |
Do not rely on a disappearing placeholder as the only label. See W3C's guidance on labeling controls.
Complete a keyboard-only pass
Set aside the mouse or trackpad. Move forward with Tab and backward with Shift+Tab. Follow the visible focus through links, inputs, selections, dialogs and the final action. Check that the order makes sense and that you can leave any popup or dialog without becoming trapped.
If a control cannot be reached or operated, record the exact step and device/browser combination. Do not work around the problem with the mouse and mark the test passed. W3C's preliminary accessibility checks explain focus visibility, keyboard operation and the limits of an initial review.
Test errors and recovery
Leave a required field empty, enter an invalid format, and try again after correcting it. Each error should identify the field and explain how to fix it. Check that previously valid entries remain available so a family does not have to start over.
Then review the success message. It should describe what was submitted and what happens next. W3C provides separate guidance on form validation and user notifications.
Do not assume that an error being visible proves that a screen reader announces it correctly. Include a screen-reader review by someone able to evaluate the full journey before treating accessibility work as complete.
Keep a short issue log
For each issue, record the step, expected result, actual result, severity, owner and retest evidence. Avoid including real child records in screenshots. Fix barriers that prevent completion first, then retest the whole affected journey rather than only the individual field.
Use the enrollment bottleneck worksheet to separate form failures from later staff-review delays. Add unresolved form requirements to your software requirements template.
Bloomily's daycare enrollment overview describes its enrollment workflow. During a demo, ask to complete the same phone, keyboard and recovery checks against the workflow your families would actually use.