On this page
- RNX-910.T001 · Title existence
- RNX-910.T002 · Character decoding
- RNX-910.T003 · Language declaration
- RNX-910.T004 · Viewport usability
- RNX-910.T005 · Title subject accuracy
- RNX-910.T006 · Title differentiation
- RNX-910.T007 · Title readability
- RNX-910.T101 · Language-change identification
- RNX-910.T102 · Title-language alignment
RNX code library · 9 controls
RNX-910Document Identity and Title Quality
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-910.T001
Title existence
core readiness
Check that a page has a nonempty title.
Why it matters. Whether that title describes the page correctly is a separate check.
Illustration — fictional. A page has no title, or it contains two conflicting titles.
When it applies. Inspected target: html head. 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-910.T002
Character decoding
core readiness
Make text characters display correctly, including accented names.
Why it matters. Broken character handling can change a business's identity.
Illustration — fictional. An accented business name turns into unreadable symbols because the character settings disagree.
When it applies. Inspected target: html encoding. 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-910.T003
Language declaration
core readiness
Declare the page's actual language.
Why it matters. Browsers and reading tools need the right language to handle the text.
Illustration — fictional. A French page declares its language as English.
When it applies. Inspected target: document language. 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-910.T004
Viewport usability
core readiness
Let the layout adapt to a phone and allow zooming.
Why it matters. People should not need perfect vision or a large screen to read it.
Illustration — fictional. A fixed-width page forces phone users to move sideways to read every line.
When it applies. Inspected target: viewport. 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-910.T005
Title subject accuracy
core readiness
Make the title describe the page's real subject.
Why it matters. Old prices or false promises can attract the wrong expectation.
Illustration — fictional. Free repair in title when no free service exists.
When it applies. Inspected target: title. 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-910.T006
Title differentiation
core readiness
Give pages with different purposes distinguishable titles.
Why it matters. This helps people recognize which result or browser tab they need.
Illustration — fictional. Five different service pages use only the brand name.
When it applies. Inspected target: title set. 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-910.T007
Title readability
core readiness
Write a title a person can understand.
Why it matters. A string of repeated search phrases is harder to read than a clear name.
Illustration — fictional. A title repeats the word software several times instead of naming the product clearly.
When it applies. Inspected target: title. 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-910.T101
Language-change identification
core readiness
Identify meaningful language changes within a page where the accessibility rule applies.
Why it matters. Reading tools need to pronounce a foreign-language passage correctly.
Illustration — fictional. A long French passage is treated as English by reading tools because its language change is not identified.
When it applies. Inspected target: language span. 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-910.T102
Title-language alignment
core readiness
Use a title in the language appropriate to the page.
Why it matters. A leftover title from another language can confuse the intended reader.
Illustration — fictional. French service copy retains unrelated English-template title.
When it applies. Inspected target: title. 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.