Enumerate visible text and annotations, including component instances.
Content quality · Workhuman AI practice
One meaning across the interface
I adapted the copy workflow to inspect related strings and annotations together, then verify the change by meaning rather than a single spelling.
ux-copy
The problem
Why this belongs
in the workflow.
An exact-string replacement can fix a visible label while missing the same concept in an accessibility annotation.
What the skill makes explicit.
Distinguish a local override from a correction to a shared component.
Use a broader verification predicate to catch equivalent wording and punctuation variants.
Evidence and learning
From instructions
to practice.
The skill records a search that missed an annotation with slightly different wording. That failure became a rule for broader discovery and verification.
Contribution and evidence scope
The source documents the incident and the revised procedure. It does not establish a product-wide copy audit or a measured improvement.
Source: the supplied ux-copy skill and associated records. Internal component identifiers and company endpoints are omitted.
Process flow
How this skill handles a task.
An exact-string replacement can fix a visible label while missing the same concept in an accessibility annotation.
- 01
Discover related text
Find labels and related accessibility annotations.
- 02
Check component context
Identify instance overrides versus shared defaults.
- 03
Update consistently
Update visible copy and its quoted annotations together.
- 04
Verify broadly
Search by meaning, including punctuation variants.
Does any old wording remain?
Deliver consistent labels and matching annotations.
Search equivalent wording and punctuation; correct and recheck.
Editorial map of the documented instructions, not a recorded execution.
Inside the skill
Instructions you can inspect.

Copy and a11y annotations move together
When an annotation quotes the copy (aria-describedby … "Supported: SRT (English only)") and the copy changes, the annotation now points at text that does not exist. When changing copy, always search for the old string inside annotations too and update it in the same pass. An annotation quoting dead copy is worse than no annotation: the engineer builds the wrong version.