ORIGINAL WHB RESEARCH GUIDE · NOVEMBER 3, 2026
Published by the Welcome Home Bridge Editorial Team. Original nonclinical public-information research; not a WCAG certification, clinical recommendation or availability claim.
A listing is useful only when its information can be reached
A housing listing may contain an address, a price range and a contact button and still be unusable. A visitor using a keyboard may not be able to open its details. A mobile reader may have to scroll sideways to see the entire fee. An image of house rules may not have a text equivalent. A link labeled “click here” may give no clue where it goes when read out of context.
These are not questions about whether a particular residence provides appropriate care. They are questions about whether public business information is accessible, comprehensible and traceable. A practical audit can address them without collecting a resident's name, diagnosis, treatment history or referral information.
The World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 2.2, Recommendation dated December 12, 2024, provide a technical reference for accessible digital content. The guidelines cover more than mobile screens: they address perceivable content, operable controls, understandable interaction and robust compatibility with assistive technology. This article translates selected principles into a focused public-listing review. It does not certify WCAG conformance or determine any operator's legal obligations.
Audit the five tasks a visitor must complete
Rather than starting with a decorative homepage score, test a representative listing from entry to exit.
1. Find the correct property and understand what the listing represents
Read the page title and first heading without relying on a photograph. Does the listing identify the business or residence unambiguously? Is the geographic area expressed in readable text? Are “housing,” “treatment” and “certification” used with their actual meanings rather than blended into a generic approval badge?
A listing should distinguish information supplied by an operator from information checked against a public registry. A label such as “verified” needs a definition and a date. For source distinctions, see the Welcome Home Bridge evidence ledger and California verification guide.
Audit evidence: capture the heading hierarchy, the displayed business name, the source of any credential and the date the claim was checked. Do not capture individual resident information.
2. Read the cost and house-rule information without decoding an image
A price embedded only in a flyer image is difficult to resize, copy, search or hear through a screen reader unless an equivalent accessible presentation is provided. Publish material charges and general terms as real text, with clear headings and labels. If a fee is only an estimate or has conditions, say so next to the number.
Check at narrow mobile widths and at increased text size. WCAG 2.2 includes 1.4.10 Reflow and 1.4.4 Resize Text; the practical objective is that essential information remains readable without two-dimensional scrolling or lost content under applicable conditions. This does not imply every visual layout must be identical on every device.
Audit evidence: note the tested viewport, zoom or text settings, any clipped charge, and the exact field affected. Link to the housing cost research guide for the questions behind the amounts.
3. Reach contact information without a mouse
Tab through the listing from the top. Can a visitor reach the business phone link, website and any correction mechanism? Is keyboard focus visible? Does a dialog or menu trap focus or hide the next control? Are links descriptive when taken out of surrounding text?
WCAG 2.2 addresses keyboard operation (2.1.1), visible focus (2.4.7), focus not obscured (2.4.11) and link purpose (2.4.4). These are specific checks, not a claim that passing a keyboard walkthrough establishes full conformance.
Audit evidence: record the device/browser, the control label, the action attempted and whether the task completed. A broken contact button is a business-data defect as well as a usability defect.
4. Distinguish unknown information from negative answers
“Not confirmed” and “not offered” are different. An unanswered question about transportation should not become a definitive “no transportation” label. A room described in a months-old listing should not be presented as currently available. Give each time-sensitive field a last-confirmed date and an accessible explanation of its status.
Avoid communicating status only with green or red color. WCAG 1.4.1 Use of Color is relevant: text labels such as “operator-reported,” “last checked,” or “not confirmed” carry the meaning even when color cannot be perceived.
Audit evidence: review one stale field and verify that the date and uncertainty remain visible to screen readers and mobile users. The written inquiry protocol shows how to request business-only clarification.
5. Correct a mistake without submitting a personal story
A correction route should identify the business field at issue and what public evidence supports the change. It should not ask a visitor to upload a discharge summary, identify a resident or disclose clinical history. Provide a clear response expectation without promising a specific turnaround time the team cannot meet.
A simple operational record can include the affected public URL, field name, claimed correction, source URL, received date, reviewer decision and published correction date. Separate private business correspondence from public change history. For the site's existing route, see request a directory correction.
Audit evidence: test the publicly described process with a fictional business-only example in a controlled environment; do not submit a real resident's data.
Use a severity rubric, not an invented compliance badge
A useful internal triage model distinguishes:
- Critical task blocker. Example: Contact control cannot be reached by keyboard. Response: Escalate for immediate remediation before representing the listing as usable.
- Material information loss. Example: Full fee is clipped on a narrow screen. Response: Fix content presentation and retest with increased text size.
- Ambiguous information. Example: Availability has no confirmation date. Response: Label as unconfirmed until a dated business source is available.
- Clarity improvement. Example: Link says only “more.” Response: Replace with an action-specific label.
This rubric is an editorial operational proposal, not a W3C severity scale, legal classification or accessibility certification. Automated scans can help flag errors, but manual keyboard, zoom, reading-order and assistive-technology checks remain necessary. Record what was actually tested, not “accessible” as a blanket assertion.
A repeatable 30-minute listing review
For one representative page, spend five minutes identifying the primary visitor tasks; ten minutes checking a narrow screen and enlarged text; five minutes traversing keyboard controls; five minutes checking source labels and freshness; and five minutes writing a prioritized defect record. The time allocation is a suggested internal workflow, not a research finding or formal conformance method. Repeat on templates and exceptional records after changes.
An audit record should contain the page URL, test date, browser and viewport, task attempted, observed result, reproducible steps, severity, owner and retest outcome. If a screen reader was not used, state that explicitly. If a browser test was blocked, mark it unverified rather than passed.
The boundary between public information and individual care
A readable listing does not verify that a property is licensed, certified, accepting residents or suitable for an individual. It cannot replace operator confirmation, independent credential checks, clinical judgment or authorized placement workflows. Welcome Home Bridge's public education and research content does not represent live bed inventory or patient onboarding; regulated platform capabilities remain subject to separate release gates.
Improving the clarity and accessibility of general housing information is a worthwhile publishing discipline on its own. It makes the limits of the information easier to see, which is as important as making the information easier to find.
Primary source and further reading
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation December 12, 2024 (current linked Recommendation version at drafting): W3C December 12, 2024 Recommendation (latest W3C text). Referenced success criteria: 1.4.1, 1.4.4, 1.4.10, 2.1.1, 2.4.4, 2.4.7, 2.4.11. W3C is the source for the technical accessibility criteria; the housing audit and prioritization framework are original editorial applications.
- Welcome Home Bridge, Recovery Housing Evidence Ledger, published November 2, 2026.
- Welcome Home Bridge, Recovery Housing Inquiry Protocol, published November 2, 2026.