On this page
- RNX-950.T001 · Action label clarity
- RNX-950.T002 · Form label association
- RNX-950.T003 · Input error recovery
- RNX-950.T004 · Keyboard completion
- RNX-950.T005 · Submission outcome
- RNX-950.T006 · Focus visibility
- RNX-950.T007 · Text contrast
- RNX-950.T008 · Reflow
- RNX-950.T009 · Control name role and state
- RNX-950.T101 · Required-input instructions
- RNX-950.T102 · Dynamic status announcement
- RNX-950.T103 · Visible-label name containment
- RNX-950.T104 · Focused-target visibility
- RNX-950.T105 · Personal-input purpose identification
- RNX-950.T106 · Pointer target size or spacing
RNX code library · 15 controls
RNX-950Accessible Conversion Interfaces
Read what these checks mean, why they matter and which evidence they concern. Each ID below keeps its canonical place in the RNX hierarchy.
These are free learning summaries, not full technical tests or an industry certification. Specialized checks apply only to the relevant feature. Experimental labels are preserved from the canonical source.
RNX-950.T001
Action label clarity
core readiness
Tell people what a button or action will do.
Why it matters. Clear labels help prevent unintended submissions or purchases.
Illustration — fictional. Request a quote silently commits purchase.
When it applies. Inspected target: action control. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T002
Form label association
core readiness
Connect form fields with meaningful labels.
Why it matters. Reading tools need to announce what information belongs in each field.
Illustration — fictional. A form field looks obvious visually but has no name that a screen reader can announce.
When it applies. Inspected target: input control. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T003
Input error recovery
core readiness
Explain which input failed and how to correct it.
Why it matters. An unexplained error leaves a customer stuck.
Illustration — fictional. Submission fails with unexplained red border only.
When it applies. Inspected target: invalid input case. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T004
Keyboard completion
core readiness
Allow required tasks to be completed with a keyboard.
Why it matters. A trapped focus or unreachable button excludes some visitors.
Illustration — fictional. A popup traps keyboard focus, and the visitor cannot close it or reach the rest of the page.
When it applies. Inspected target: keyboard task. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T005
Submission outcome
core readiness
Report submission success or failure honestly and accessibly.
Why it matters. A reassuring message must not hide a failed request.
Illustration — fictional. Network failure shows Thanks sent with no receipt.
When it applies. Inspected target: submission case. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T006
Focus visibility
core readiness
Show where keyboard focus is on the page.
Why it matters. People navigating without a pointer need to see which control is active.
Illustration — fictional. The visible keyboard-focus outline is removed without any replacement indicator.
When it applies. Inspected target: focus state. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T007
Text contrast
core readiness
Check text contrast against the applicable accessibility rule, including its exceptions.
Why it matters. Faint text can be unreadable even when it looks elegant.
Illustration — fictional. Ordinary text has very low contrast, and no allowed exception applies.
When it applies. Inspected target: text color pair. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T008
Reflow
core readiness
Let content fit a narrow or zoomed view without sideways reading, except where the rule permits it.
Why it matters. This supports people who enlarge text.
Illustration — fictional. Fixed article requires left-right and up-down scrolling.
When it applies. Inspected target: reflow region. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T009
Control name role and state
core readiness
Expose each control's name, function and relevant state to assistive tools.
Why it matters. Appearance alone does not tell a screen reader whether a switch is on.
Illustration — fictional. A switch looks on, but reading tools receive neither its function nor its current state.
When it applies. Inspected target: widget state. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T101
Required-input instructions
core readiness
Show necessary input instructions before an avoidable error.
Why it matters. People should know a required date format before submitting the form.
Illustration — fictional. A required formatted date has no indication or format until unexplained failure.
When it applies. Inspected target: input instruction. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T102
Dynamic status announcement
core readiness
Expose relevant changing status messages to assistive tools.
Why it matters. A visual Saved message is not enough if a screen reader cannot detect it.
Illustration — fictional. Visual Saved message appears but assistive technology cannot detect it.
When it applies. Inspected target: status message. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T103
Visible-label name containment
core readiness
Keep the visible control label within its accessible name where required.
Why it matters. Voice users should be able to activate the words they see.
Illustration — fictional. A button says Buy now on screen but announces Continue to assistive tools.
When it applies. Inspected target: control label. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T104
Focused-target visibility
core readiness
Keep the keyboard-focused target from being fully hidden by site content.
Why it matters. A sticky panel should not cover the button someone is trying to use.
Illustration — fictional. Sticky panel completely hides the focused submit button.
When it applies. Inspected target: focused control. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T105
Personal-input purpose identification
core readiness
Identify recognized personal-information fields in a supported machine-readable way.
Why it matters. This helps tools understand and fill details such as an email address.
Illustration — fictional. An email field lacks the supported purpose label that would help tools identify and fill it.
When it applies. Inspected target: personal input. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-950.T106
Pointer target size or spacing
core readiness
Check touch-target size or spacing against the chosen accessibility rule and its exceptions.
Why it matters. Crowded controls make accidental taps more likely.
Illustration — fictional. A very small button is crowded by other buttons and meets none of the applicable spacing exceptions.
When it applies. Inspected target: pointer target. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.