# Make the task usable across different ways of accessing it

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

Ten bounded interface checks for keyboard, enlargement, forms, status, speech input, motion, targets and tables.
Collection kind: collection
Source: https://vedokrok.com/collections/make-the-task-usable-across-different-ways-of-accessing-it
Version: 0.1.0

---

## Complete the journey with the keyboard alone

ID: MHC-D-RESEARCH-1100 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/complete-the-journey-with-the-keyboard-alone

Being able to reach a button is not the same as finishing the task.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A feature works with a mouse but keyboard access has not been checked.

### Avoid when

- Some path-dependent input has specific exceptions. This small check does not replace assistive-technology testing or a full accessibility evaluation.

### Explanation

Try a meaningful journey without the pointer: start, edit, submit, recover and leave. Observe focus and available actions at each step. A keyboard check should expose a blocked task, not merely count controls reached by Tab.

### Checklist

- Can you reach and operate every control needed for the task?
- Can you tell where focus is and follow a sensible order?
- Can you leave a dialog or recover from an error without using the mouse?

### Example

A recording dialog opens from the keyboard, but its close control cannot be reached. The journey fails despite a working Start button.

### Check

Can a fresh tester complete and exit the chosen task without pointer assistance?

### Limits

- Some path-dependent input has specific exceptions. This small check does not replace assistive-technology testing or a full accessibility evaluation.

### Evidence and sources

- supports: WCAG 2.1.1 requires functionality to be operable through a keyboard interface, with an exception for input that depends on the path of movement. — RS-EF6E9CB357047C5B. This card inspects ordinary interface tasks, not every path-dependent interaction or accessibility criterion. (Success criterion and intent.)
- RS-EF6E9CB357047C5B: Understanding Success Criterion 2.1.1: Keyboard — https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/keep-the-field-s-identity-after-the-user-starts-typing

---

## Make enlarged text fit the task, not just the screen

ID: MHC-D-RESEARCH-1101 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/make-enlarged-text-fit-the-task-not-just-the-screen

A larger sentence is not helpful when its ending disappears.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Readers enlarge the interface and lose controls or part of the text.

### Avoid when

- Tables, maps and other genuinely two-dimensional content need specific treatment. Do not infer full accessibility from one successful zoom setting.

### Explanation

Test a narrow viewport and substantial zoom with realistic content. Inspect reading order, wrapping and controls, not just font size. WCAG’s reflow criterion includes a 320 CSS pixel width condition and exceptions; use its full wording when assessing conformance.

### Steps

1. Open a content-heavy page and its important form or dialog.
2. Check whether text and controls remain available without unnecessary horizontal travel.
3. Repeat with long labels, validation messages and translated text.

### Example

At high zoom, a card’s actions cover its final paragraph. The defect is lost content, not an unattractive layout.

### Check

Can the reader understand the content and complete the task at the tested enlargement?

### Limits

- Tables, maps and other genuinely two-dimensional content need specific treatment. Do not infer full accessibility from one successful zoom setting.

### Evidence and sources

- supports: WCAG 1.4.10 addresses loss of content or functionality and two-dimensional scrolling at specified narrow viewport dimensions, with exceptions. — RS-D167B40F7DEEBBDF. Some content genuinely requires a two-dimensional layout; passing one viewport test is not full conformance. (Success criterion, 320 CSS pixel width and examples.)
- RS-D167B40F7DEEBBDF: Understanding Success Criterion 1.4.10: Reflow — https://www.w3.org/WAI/WCAG22/Understanding/reflow.html

### Vedokrok editorial review

Test the viewport, then test the text

A narrow layout and readable enlarged text are two checks. Passing one does not settle the other.

#### Make the reflow check reproducible

For vertically scrolling content, test at 320 CSS pixels of viewport width. A 1280 CSS pixel starting viewport at 400% browser zoom is one route; record the actual viewport, not the monitor resolution. For horizontally scrolling content, the corresponding condition is 256 CSS pixels of height. Complete a realistic task and note missing content, blocked controls and lines that require scrolling in both directions.

#### Keep the exception local

A genuinely two-dimensional table can need sideways scrolling. Its ordinary text cells, search field and surrounding explanation do not inherit a blanket exemption. Separately check that text can reach 200% enlargement without losing content or function, subject to the Resize Text exceptions. A responsive font-size reduction is not automatically a failure if that enlargement remains possible; fitting the layout alone is not enough.

#### Choose the check for the problem

For a reporting dashboard, record the zoom and viewport, read a long cell, change a filter and reach the next page. This is more informative for a clipped-text defect than a desktop screenshot. It does not replace the keyboard journey (1100), pointer-target check (1108), or a complete accessibility assessment. These are complementary checks, not competing treatments.

**Editorial takeaway:** Leave a reproducible defect: the task, viewport, enlargement, lost information or control, and whether a specific two-dimensional exception actually applies.

#### Editorial evidence

- supports: The reflow conditions and two-dimensional exception are defined by WCAG 2.2 SC 1.4.10. — wcag22-20241212. A normative condition, not evidence that this editorial task checklist establishes overall conformance. (SC 1.4.10, including Notes 1–2)
- limits: Table-related controls and ordinary cell content are not covered by a blanket table exception. — RS-D167B40F7DEEBBDF. Selected guidance passages clarify the original card’s broad boundary; some cell content itself may qualify for an exception. (Understanding the scope of exceptions; Tabular data and grid-based UI)
- contextualizes: Responsive text may shrink in CSS units while still permitting the required text enlargement. — RS-D167B40F7DEEBBDF. Clarifies the distinction from a blanket prohibition on responsive font changes; SC 1.4.4 remains a separate requirement. (Overlap with other success criteria — Resize Text)
- RS-D167B40F7DEEBBDF: Understanding Success Criterion 1.4.10: Reflow — https://www.w3.org/WAI/WCAG22/Understanding/reflow.html
- wcag22-20241212: Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, 12 December 2024 — https://www.w3.org/TR/2024/REC-WCAG22-20241212/

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/test-the-target-and-its-neighbours-not-just-the-icon

---

## Give the colour a second way to speak

ID: MHC-D-RESEARCH-1102 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/give-the-colour-a-second-way-to-speak

The meaning should survive when the colour does not.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Status, charts or errors rely on red, green or another colour code.

### Avoid when

- An unexplained icon can be as ambiguous as a colour. Do not assume that adding any symbol makes the information accessible.

### Explanation

Add a meaningful label, symbol, pattern or other non-colour cue. Keep that cue consistent and understandable in context. This addresses colour dependence; contrast, accessible names and text alternatives still need their own checks.

### Checklist

- Does each important state have information beyond its colour?
- Can a reader distinguish chart series without memorising a colour legend?
- Do error messages identify the problem rather than merely tinting a field?

### Example

A reconciliation table replaces red-only rows with an Error status and a short reason, while retaining colour as an optional aid.

### Check

Can someone explain every important distinction without naming a colour?

### Limits

- An unexplained icon can be as ambiguous as a colour. Do not assume that adding any symbol makes the information accessible.

### Evidence and sources

- supports: WCAG 1.4.1 does not allow colour to be the only visual means of conveying information, indicating an action or distinguishing an element. — RS-3A83AC018AAD7AD1. A text label or pattern does not independently establish sufficient contrast or accessible naming. (Success criterion and intent.)
- RS-3A83AC018AAD7AD1: Understanding Success Criterion 1.4.1: Use of Color — https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/make-the-error-show-the-next-repair

---

## Keep the field’s identity after the user starts typing

ID: MHC-D-RESEARCH-1103 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-the-field-s-identity-after-the-user-starts-typing

A field should not lose its name when it receives an answer.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A form looks clean until its placeholder disappears.

### Avoid when

- Some controls have context-specific labelling patterns. A technical label association alone does not make confusing wording clear.

### Explanation

Give each control an appropriate label and associate it programmatically with that control. Use help text for format or context rather than asking the placeholder to do every job. Check the filled-in state, not only the empty mockup.

### Steps

1. Identify what information each field requests in ordinary language.
2. Keep its label available and connect it to the control in the implementation.
3. Test the field with existing content, an error and assistive technology.

### Example

A Date field keeps its label and format instruction visible after the user enters a value that needs correction.

### Check

Can the user identify the requested information without clearing the field or remembering a vanished hint?

### Limits

- Some controls have context-specific labelling patterns. A technical label association alone does not make confusing wording clear.

### Evidence and sources

- supports: WAI guidance describes associating labels with form controls and warns against relying on placeholder text as a replacement for labels. — RS-2D9BD74385B2CA55. A programmatic label and a usable visible instruction solve related but distinct needs. (Associating labels and placeholder discussion.)
- RS-2D9BD74385B2CA55: Labeling Controls — https://www.w3.org/WAI/tutorials/forms/labels/

### Vedokrok editorial review

Check that a field keeps the name you gave it

A label can remain on screen yet name the wrong field, or no field at all. Check both what people see and what software exposes.

#### Keep the purpose visible

Fill an ordinary text field, then return to it. Can you still tell what it asks for? Keep a clear label outside the placeholder; put format help beside it. For example, a Project code field should still say Project code after someone enters PX-42.

#### Check the connection

For an HTML text field, one standard route is a label element whose for value matches the field’s unique id. Inspect that connection and click the label to check which field receives focus. This is one supported pattern, not a requirement to use it for every kind of control.

#### Inspect the name the field actually exposes

In the browser’s accessibility inspector, read the field’s computed Name, not just its nearby text. An aria-label or aria-labelledby can override the ordinary label. Compare the name with the intended field purpose, then repeat with a filled value and an error. Record the browser and assistive technology when checking how the field is presented in use.

**Editorial takeaway:** Keep one short record: visible label, linked control and computed name. A correct link or successful click alone does not establish a usable name. Some controls can rely on clear surrounding context; a hidden name cannot replace visible instructions that the user still needs.

#### Editorial evidence

- supports: WAI describes explicit HTML label association through matching for and id values. — RS-2D9BD74385B2CA55. Tutorial updated 2024-05-13; selected passages inspected 2026-10-06. The explicit link is one route. Context can sometimes support a visually hidden label; that does not make hidden-only labeling a general recommendation. (Associating labels explicitly; Associating labels implicitly; Hiding label text)
- supports: For applicable HTML controls, H44 describes matching label for and control id values, a unique id and activation through the associated label. — RS-40861BB2A7F4C707. Technique updated 2026-01-12; selected passages inspected 2026-10-06. This is a sufficient technique within its stated scope, not a requirement that every control use an external label or a whole-interface conformance test. (Description; elements that use explicitly associated labels; Tests)
- supports: Placeholder text is not an appropriate replacement for a field label; ARIA naming can override native label associations. — RS-71603CB81AF21C2D. Understanding page updated 2026-04-05; selected passages inspected 2026-10-06. This is the inspected locator for the placeholder warning; the Labeling Controls tutorial was not found to contain the placeholder discussion attributed to it in the historical base item. That historical record remains unchanged. (Identifying label text for components; Accessible Name and Description Computation specification)
- limits: Visible field identity, programmatic naming and visible instructions address related but distinct needs. — RS-71603CB81AF21C2D. The filled-field example, inspector sequence and record are editorial application of the guidance, not observed user results. A placeholder may still be the visible text evaluated for Label in Name when no other label exists; that does not make placeholder-only design good labeling. No assistive-technology test was performed for this draft. (Identifying label text for components; Accessible Name and Description Computation specification)
- contextualizes: Chrome DevTools exposes computed accessibility properties, while markup inspection does not establish successful assistive-technology navigation. — RS-B01B06F4F3B23F5F. Official tool documentation updated 2026-05-28; selected passages inspected 2026-10-06. Supports the feasibility and limits of the inspector step. Other browsers may expose equivalent information through different tools; no browser or assistive-technology runtime test was performed. (Overview of accessibility features in Chrome DevTools; The Accessibility tab; View an element’s computed accessibility properties)
- RS-2D9BD74385B2CA55: Labeling Controls — https://www.w3.org/WAI/tutorials/forms/labels/
- RS-40861BB2A7F4C707: H44: Using label elements to associate text labels with form controls — https://www.w3.org/WAI/WCAG22/Techniques/html/H44
- RS-71603CB81AF21C2D: Understanding Success Criterion 2.5.3: Label in Name — https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html
- RS-B01B06F4F3B23F5F: Accessibility features reference — Chrome DevTools — https://developer.chrome.com/docs/devtools/accessibility/reference

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/make-the-error-show-the-next-repair

---

## Make the error show the next repair

ID: MHC-D-RESEARCH-1104 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/make-the-error-show-the-next-repair

Invalid is a verdict, not an instruction.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A form rejects input but leaves people guessing what to change.

### Avoid when

- Do not reveal private account information through detailed errors. Avoid blaming the user for network failures or conditions they cannot repair.

### Explanation

Connect the message to the affected field and explain the correctable problem in plain language. Preserve useful context so the user can repair the entry rather than restart blindly. Test what happens after correction as well as the first error.

### Steps

1. Describe the specific problem the system can actually detect.
2. Show where to fix it and give an example or constraint when useful.
3. Submit a corrected value and check that the message and state update consistently.

### Example

Instead of Something went wrong, a form says that the end date precedes the start date and identifies the relevant field.

### Check

Can a user make a valid correction without a moderator translating the message?

### Limits

- Do not reveal private account information through detailed errors. Avoid blaming the user for network failures or conditions they cannot repair.

### Evidence and sources

- supports: WAI guidance calls for errors to be identified and described so users can understand and correct them. — RS-4EAE438AF6261A91. Error wording must not expose sensitive information or claim knowledge the system lacks. (Error notifications and correction guidance.)
- RS-4EAE438AF6261A91: User Notifications — https://www.w3.org/WAI/tutorials/forms/notifications/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/announce-the-result-without-stealing-the-user-s-place

---

## Announce the result without stealing the user’s place

ID: MHC-D-RESEARCH-1105 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/announce-the-result-without-stealing-the-user-s-place

Finished should not be a message only sight can hear.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A background action changes status but assistive-technology users receive no useful signal.

### Avoid when

- Not every update deserves an alert. Repeated progress announcements can overwhelm the information they were meant to reveal.

### Explanation

Make relevant status information programmatically available without unnecessarily moving focus. Choose an announcement pattern appropriate to the urgency. Test with the actual assistive technology; adding a live region is an implementation choice, not proof of a good experience.

### Steps

1. Identify the result or progress change the user needs to know.
2. Provide an appropriate status message rather than shifting focus to decorative feedback.
3. Check that it is announced once, at a useful time, without interrupting every small change.

### Example

After an upload, the interface announces Processing complete while the user remains in the field they were editing.

### Check

Can the user tell what happened and continue the task without losing their place?

### Limits

- Not every update deserves an alert. Repeated progress announcements can overwhelm the information they were meant to reveal.

### Evidence and sources

- supports: WCAG 4.1.3 addresses status messages that assistive technology can present without receiving focus. — RS-DF1D065015C67030. Not every interface change is a status message; excessive or urgent announcements can be disruptive. (Success criterion and intent.)
- RS-DF1D065015C67030: Understanding Success Criterion 4.1.3: Status Messages — https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html

### Vedokrok editorial review

Choose the status message before the announcement

A changed screen is not always a status message. First identify the information and whether the user's context changes.

#### Separate feedback from a new place to work

A status message reports an outcome, waiting, progress or an error without changing the user's context. An export tool's completion notice beside the form can qualify while focus stays in place. An error dialog that takes focus and an options panel opening are different cases: check the dialog or control's own accessibility, rather than adding an alert by habit. WCAG 4.1.3 does not require new feedback for every change.

#### Make ordinary feedback available with its meaning

For non-urgent updates, WAI describes a role=status container that exists before the message arrives. Where this pattern fits, put the update and the context needed to understand it inside that container. If the whole phrase needs announcing, WAI advises explicit aria-atomic=true because some environments do not apply the role's atomic default. In an export tool, hearing 'Two files ready' is useful; hearing only 'Two' leaves the result unclear. This is one implementation pattern, not the only allowed technique.

#### Test the experience, not an announcement count

Record the browser, assistive technology and settings; trigger the change while doing another part of the task. Check access to the meaningful update and unnecessary interruptions. Useful progress feedback may be intermittent, and assistive technology may delay or suppress it according to user preferences. 'Spoken exactly once' is not the criterion. This check complements actionable error wording in 1104; it does not certify the whole interface.

**Editorial takeaway:** Leave a test record: what changed, why it is a status message, how its meaning is exposed, and what happened in the tested setup.

#### Editorial evidence

- supports: SC 4.1.3 concerns programmatically determinable status information that can be presented without taking focus. — wcag22-20241212. Normative scope, not a mandate for one spoken announcement or a complete conformance test. (SC 4.1.3; glossary: status message)
- limits: Ordinary expansion and focus-taking dialogs fall outside this status-message criterion; timing can reflect user preferences. — RS-DF1D065015C67030. Selected guidance qualifies the earlier once-only instruction. Other accessibility requirements remain applicable. (Intent; Benefits; Status message examples; Examples of changes that are not status messages; Other uses of live regions or alerts)
- supports: The ARIA22 pattern establishes the status container before an update and retains meaningful context within it. — w3c-aria22-status. The role defines atomic updates by default; WAI recommends explicit aria-atomic=true where the whole message is needed because support differs. This optional technique still needs testing in the intended environment. (Description; Tests, Procedure 1–3)
- RS-DF1D065015C67030: Understanding Success Criterion 4.1.3: Status Messages — https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html
- wcag22-20241212: Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, 12 December 2024 — https://www.w3.org/TR/2024/REC-WCAG22-20241212/
- w3c-aria22-status: ARIA22: Using role=status to present status messages — https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA22

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.

---

## Let voice commands use the label people can see

ID: MHC-D-RESEARCH-1106 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/let-voice-commands-use-the-label-people-can-see

The screen says Save. The hidden name should not insist on Commit artifact.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A visible button name does not work as expected with speech input.

### Avoid when

- This does not mean every accessible name must be identical to its visible label. Repeated controls may need additional distinguishing context.

### Explanation

Inspect the control’s accessible name and compare it with its visible label. The name should contain that label’s text so voice users can refer to what they see. Additional useful context may follow; unrelated replacement wording can break the connection.

### Checklist

- Does the accessible name contain the visible label text?
- Has a custom accessibility attribute replaced the ordinary label with different wording?
- Can a speech-input user identify and activate the intended control?

### Example

A visible Start recording control no longer has the unrelated accessible name Begin audio capture workflow.

### Check

Does the tested voice command match the visible control without requiring knowledge of hidden wording?

### Limits

- This does not mean every accessible name must be identical to its visible label. Repeated controls may need additional distinguishing context.

### Evidence and sources

- supports: WCAG 2.5.3 requires the accessible name to contain the text presented in a control’s visible label. — RS-71603CB81AF21C2D. Additional name text can be appropriate; unrelated replacement wording can prevent voice users from matching the visible control. (Success criterion and speech-input explanation.)
- RS-71603CB81AF21C2D: Understanding Success Criterion 2.5.3: Label in Name — https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html

### Vedokrok editorial review

Keep the visible command intact in the accessible name

Adding helpful hidden words can split the phrase a person sees. Check the whole label inside the actual name.

#### Compare the label with Name, not Description

For a control with a visible text label, inspect its computed Name in the browser’s accessibility inspector. Keep the label’s words together and in order. A button reading Export report does not retain that phrase in the name Export monthly report. Export report for March does. Do not demand a character-for-character match: capitalization and most punctuation do not determine this check.

#### Add context without breaking the command

Putting the visible label first is a WCAG best practice, not a separate requirement. Monthly Export report still contains the phrase, although it does not follow that preference. Extra help can belong in Description instead. An aria-describedby association supplies a description; it cannot repair a missing phrase in Name. Check any aria-label or aria-labelledby that overrides the visible text.

#### Then try the intended command

Use the visible phrase with the supported speech-input setup and record which control responds. Record the browser, speech tool and settings. If it fails, inspect the name and the interaction; matching text alone does not guarantee operation. Icon-only controls still need appropriate names, but this visible-text comparison does not cover them.

**Editorial takeaway:** Save the visible label, computed Name and observed command result separately. A screen reader may speak a description after the name, so hearing the visible words somewhere is not enough. This is a focused naming check, not a full accessibility evaluation.

#### Editorial evidence

- supports: WCAG 2.2 SC 2.5.3 requires a control’s name to contain its visible text label; placing that text first is stated as best practice. — RS-7E7303084DD310BE. W3C Recommendation 2024-12-12; criterion and note inspected 2026-10-06. The normative containment requirement and best-practice prefix placement are distinct. This is a standard, not an efficacy study. (2.5.3 Label in Name, Level A, criterion and note)
- supports: G208 describes including the visible text string intact and in order. — RS-6C3E14DD9FB8E707. Technique updated 2025-09-24; selected passages inspected 2026-10-06. Informative sufficient technique, not an additional normative rule. The Export report examples are original editorial illustrations. (Description; Tests, Procedure 1)
- supports: Inserting a hidden word between the words of a visible label can break the label-to-name match. — RS-D6D6626D1A7300E2. Failure technique updated 2026-05-18; selected passages inspected 2026-10-06. Used for the specific interrupted-phrase counterexample; no claim that every speech tool fails on every such control. (Example 2; Tests)
- supports: ARIA naming can override native text; aria-describedby contributes a description rather than an accessible name. — RS-71603CB81AF21C2D. Understanding page updated 2026-04-05; selected passages inspected 2026-10-06. Screen-reader speech may include both name and description. Inspector comparison and the recorded speech trial are editorial checks; this draft reports no real speech-input or screen-reader test. (Accessible Name and Description Computation specification)
- limits: Label in Name does not apply where a control lacks a visible text label, and capitalization and most punctuation are not decisive for its matching check. — RS-71603CB81AF21C2D. Selected passages inspected 2026-10-06. Other naming requirements still apply. Symbols and mathematical expressions have specific treatment in the full guidance; this card does not offer a universal literal-string algorithm or full conformance judgment. (Intent; Symbolic text characters; Punctuation and capitalization)
- contextualizes: Chrome DevTools exposes computed accessibility properties, while markup inspection does not establish successful assistive-technology navigation. — RS-B01B06F4F3B23F5F. Official tool documentation updated 2026-05-28; selected passages inspected 2026-10-06. Supports the feasibility and limits of the inspector step. Other browsers may expose equivalent information through different tools; no browser or assistive-technology runtime test was performed. (Overview of accessibility features in Chrome DevTools; The Accessibility tab; View an element’s computed accessibility properties)
- RS-71603CB81AF21C2D: Understanding Success Criterion 2.5.3: Label in Name — https://www.w3.org/WAI/WCAG22/Understanding/label-in-name.html
- RS-7E7303084DD310BE: Web Content Accessibility Guidelines (WCAG) 2.2 — https://www.w3.org/TR/2024/REC-WCAG22-20241212/
- RS-6C3E14DD9FB8E707: G208: Including the text of the visible label as part of the accessible name — https://www.w3.org/WAI/WCAG22/Techniques/general/G208
- RS-D6D6626D1A7300E2: F96: Failure due to the accessible name not containing the visible label text — https://www.w3.org/WAI/WCAG22/Techniques/failures/F96
- RS-B01B06F4F3B23F5F: Accessibility features reference — Chrome DevTools — https://developer.chrome.com/docs/devtools/accessibility/reference

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/keep-the-field-s-identity-after-the-user-starts-typing

---

## Make non-essential interaction motion optional

ID: MHC-D-RESEARCH-1107 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/make-non-essential-interaction-motion-optional

A transition should not make someone pay a physical price for pressing a button.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Navigation or feedback triggers sliding, zooming or other substantial motion.

### Avoid when

- Some animation is essential to explaining movement. Provide appropriate alternatives and avoid claiming that one setting makes all content symptom-free.

### Explanation

Offer a way to suppress non-essential motion triggered by interaction, while preserving the information and action. WCAG addresses this in a Level AAA criterion; do not relabel it as a blanket AA rule or a ban on every animation.

### Steps

1. Identify which motion communicates essential information and which is decoration.
2. Provide a reduced-motion path or honor a relevant user preference in the implementation.
3. Test that state changes remain clear when movement is removed.

### Example

A completed exercise changes status immediately in reduced-motion mode instead of sending the card spinning across the screen.

### Check

Can the same task be understood and completed with non-essential motion disabled?

### Limits

- Some animation is essential to explaining movement. Provide appropriate alternatives and avoid claiming that one setting makes all content symptom-free.

### Evidence and sources

- supports: WCAG 2.3.3 at Level AAA requires interaction-triggered motion animation to be disableable unless essential to the functionality or information. — RS-39E8C1ACB624F97C. The criterion is not a universal ban on animation or a standalone certification of vestibular safety. (Success criterion and level.)
- RS-39E8C1ACB624F97C: Understanding Success Criterion 2.3.3: Animation from Interactions — https://www.w3.org/WAI/WCAG22/Understanding/animation-from-interactions.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/announce-the-result-without-stealing-the-user-s-place

---

## Test the target and its neighbours, not just the icon

ID: MHC-D-RESEARCH-1108 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/test-the-target-and-its-neighbours-not-just-the-icon

The finger meets the clickable area, not the design file.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Small controls are difficult to activate without hitting something else.

### Avoid when

- CSS pixels are not physical screen pixels. Passing the minimum criterion does not prove comfort or suitability for every user.

### Explanation

Inspect the actual pointer target and its spacing from nearby targets. WCAG 2.5.8 uses a 24 by 24 CSS pixel minimum with defined exceptions, including qualifying spacing. Apply the complete condition rather than treating one icon dimension as the whole test.

### Steps

1. Measure the implemented hit area, not only its visible artwork.
2. Check adjacent controls, spacing and any applicable exception.
3. Try the important task on the intended input device and viewport.

### Example

A tiny visible icon has a larger implemented target, while two adjacent text actions overlap their effective hit areas. They need different fixes.

### Check

Can the user reliably choose the intended action without an unintended neighbour receiving it?

### Limits

- CSS pixels are not physical screen pixels. Passing the minimum criterion does not prove comfort or suitability for every user.

### Evidence and sources

- supports: WCAG 2.5.8 at Level AA specifies a 24 by 24 CSS pixel minimum target or applicable exceptions, including qualifying spacing. — RS-447E7F1844CB9DDF. Do not replace the complete criterion with a claim that every target must be enlarged to the same dimensions. (Success criterion and exception explanations.)
- RS-447E7F1844CB9DDF: Understanding Success Criterion 2.5.8: Target Size (Minimum) — https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html

### Vedokrok editorial review

Measure the hit area, then draw the spacing circles

“There is some space” is not a target-size test. Use the implemented clickable region and record which condition it meets.

#### Check size before spacing

For the WCAG 2.5.8 minimum, a solid 24 by 24 CSS pixel square, aligned with the page axes, must fit inside the target. A circular hit area only 24 pixels across cannot contain that square. Treat it as undersized and check an applicable exception. Measuring the surrounding artwork or its bounding box alone can give the wrong answer.

#### Use the actual spacing rule

For each undersized target, centre a circle of 24 CSS pixels in diameter on its bounding box. Check it against every nearby target and every other undersized target’s circle: overlapping either fails the spacing exception. Other exceptions cover a conforming equivalent control on the same page, inline text, unmodified browser controls and essential presentation; verify the relevant condition rather than assuming all small controls fail.

#### Record the repair, not just a verdict

Imagine a round close control above a large clickable preview. Making its icon bolder changes neither hit area nor clearance. Inspect the actual geometry and choose enlargement, separation or a justified exception. Geometry is a better check for this defect than icon dimensions; testing the task with intended input devices addresses a different question. Neither check proves comfort for every user or complete accessibility.

**Editorial takeaway:** For each suspect control, record the hit-area shape, CSS dimensions, relevant neighbours and the size or exception condition. Recheck after the layout changes.

#### Editorial evidence

- supports: The minimum target criterion permits spacing and four other defined exceptions. — wcag22-20241212. The circle must clear both other targets and other undersized-target circles; an editorial checklist is not conformance certification. (SC 2.5.8, Spacing through Essential)
- supports: Size uses an inscribed page-aligned square; a 24-pixel circular target is undersized. — RS-447E7F1844CB9DDF. Selected explanation corrects a possible bounding-box false pass. CSS pixels are not physical screen pixels. (Size requirement, Figures 1–3; Spacing)
- limits: Meeting the minimum target condition does not ensure ease of activation for everyone. — RS-447E7F1844CB9DDF. No participant test, measured improvement or universal target-size recommendation is claimed. (Intent — Note; Spacing — Note)
- RS-447E7F1844CB9DDF: Understanding Success Criterion 2.5.8: Target Size (Minimum) — https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html
- wcag22-20241212: Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, 12 December 2024 — https://www.w3.org/TR/2024/REC-WCAG22-20241212/

Editorial version: 1.0.0 · evidence checked 2026-10-06 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/complete-the-journey-with-the-keyboard-alone

---

## Keep the headers attached when the table leaves your screen

ID: MHC-D-RESEARCH-1109 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-the-headers-attached-when-the-table-leaves-your-screen

Bold text is not a relationship.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A table is readable visually but confusing with assistive technology or after export.

### Avoid when

- Complex tables may need a simpler alternative. A correct source document does not guarantee that an export preserves its structure.

### Explanation

Identify the row and column headers that give each value its meaning. Represent those associations semantically in the chosen format, and check the exported result separately. Keep complex headings only when the task genuinely needs them.

### Steps

1. Name what a reader must know to interpret a data cell.
2. Use appropriate header associations and a useful table description or caption.
3. Inspect representative cells in the delivered format, including cells under grouped headings.

### Example

A status table must preserve both the business unit and reporting period for each value, not merely bold the top row.

### Check

Can a non-visual reader recover the relevant headers while moving through the table?

### Limits

- Complex tables may need a simpler alternative. A correct source document does not guarantee that an export preserves its structure.

### Evidence and sources

- supports: WAI table guidance uses semantic header and data-cell relationships so table structure is available beyond visual presentation. — RS-4952EB9FEE9EB4C3. Complex tables and exports need format-specific verification; bold text is not a semantic header. (Table structure and header associations.)
- RS-4952EB9FEE9EB4C3: Tables Tutorial — https://www.w3.org/WAI/tutorials/tables/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-colour-a-second-way-to-speak
