Using Reflection Forms with a Keyboard or Larger Text

Choose the task and use invented text first

Choose one useful task: entering a brief note, changing a choice, reading a summary or clearing the page. You do not need to complete every form on the site to check that task. Avoid real names or personal disclosures while you explore the controls.

In the current mood-note tool, the three boxes are optional and the result counts boxes containing text. It does not analyse mood, save a history or export filled entries. Its blank download contains prompts, not your current answers. [4] Those distinctions matter before testing whether you can reach or keep a result.

Try the invented line “After the planning call, the date was still unknown.” Add a second sentence on a new line if useful. This is a reading/input check, not a clinical example, a reported user test or proof that your browser works like somebody else’s.

Check focus, editing and a way out

Use your browser’s normal keyboard navigation to move through the page. Common starting keys are Tab and Shift+Tab; actual controls and assistive-technology modes may use additional commands. Find the visible focus indicator before entering text, and check the field’s label rather than relying only on a hint that disappears.

WCAG 2.2 requires keyboard operation of content functionality, with a narrow exception for inherently path-dependent input, and requires a way to move keyboard focus away from a component. [1, SC 2.1.1–2.1.2] These are expectations for the interface, not a demand that you learn a workaround or repeatedly attempt an inaccessible task.

Enter the invented line, move back into it, correct “planning” to “booking,” and then leave the field. Check whether you can reach the relevant result or Clear control and return to normal reading. A field accepting characters does not establish that every button, menu or result is reachable.

If focus disappears, an overlay covers the control or you cannot move away, stop that check. Record the specific task and last visible control without including personal text. SC 2.4.7 concerns visible focus; SC 2.4.11 requires focused components not be entirely hidden by author-created content. [1] No real browser or screen-reader audit is claimed here.

Enlarge text and follow the complete answer

Use the browser’s text-size or zoom settings that suit you. W3C’s Resize Text criterion addresses text up to 200% without loss of content or functionality, except captions and images of text; its explanation includes text-based controls and labels. [1][2] Check intermediate settings as well as the final size.

Read the field label, both sentences, the result and the action labels. Look for clipped last lines, overlapping instructions or a button whose text is hidden. Increasing the outer box is not the same as making the text legible; shrinking the text to fit a table defeats this reading task.

Reflow is a separate criterion: vertically scrolling content should work at a width equivalent to 320 CSS pixels without requiring scrolling in two dimensions, subject to exceptions for content needing two-dimensional layout. Data tables can fall within that exception. [1, SC 1.4.10] A table may need horizontal scrolling; the surrounding explanation and individual cells still need readable content.

MDN describes a textarea as a multi-line plain-text editing control. Its appearance, size and resizability can vary with browser and CSS. [3] Do not assume that a visible drag handle is the only usable way to read an entry. Check the actual configuration or use another suitable format.

Separate three kinds of difficulty

MDN explains that disabled textareas are not focusable, whereas readonly ones can be focused and selected. [3] That general distinction does not certify a particular interface or mean a skipped optional control is a failure.

Use a simpler format without creating a new obligation

The tool’s blank TXT worksheet is an alternative place to write; you may use a text editor, paper, your chosen accessible application or no saved record. Check the label and order of the fields in that format too. A text file can still be hard to use in an unsuitable reader.

If you copy an entry separately, inspect the actual destination. The plain-text record guide covers labels, order, line breaks and unknown information. For who can access the copy, use the journal privacy guide. Neither a keyboard check nor a local file guarantees privacy.

The downloadable usability record asks for page, browser/device, text-size setting, task, observed issue and alternative. Those are optional practical notes, not a complete WCAG audit or a required complaint form. A reflection can end without a score, answer or stored file.

Use the optional blank record

Open the original blank TXT record. It contains prompts, not personal entries entered in another page.

REFLECTION FORM USABILITY CHECK — optional, use invented text
PAGE / TOOL:
BROWSER / DEVICE / TEXT-SIZE OR ZOOM SETTING:
ONE TASK: input / edit / choice / read result / clear / leave
INVENTED TEXT USED:
LABEL AND LAST VISIBLE FOCUSED CONTROL:
ACTUAL OBSERVATION / STEP THAT COULD NOT BE COMPLETED:
WAS THE WHOLE ENTRY AND RESULT READABLE:
ALTERNATIVE FORMAT CHOSEN / STOP:
This record is not a WCAG conformance audit and contains no personal reflection.