To build accessible ABA portals forms telehealth documents and digital workflows, inventory every client-facing task and test it with keyboard access, screen readers, zoom, captions, color and focus checks, understandable labels, accessible documents, and usable error recovery. Preserve AAC and interpreter participation during telehealth. Offer an effective alternative while defects remain, assign owners and deadlines, and validate fixes with real task completion instead of relying only on automated scores.

Define Rina's exact access unit

Rina measures whether people can finish a task. A compliant-looking home page offers little help when the intake form, signature tool, video, payment screen, or complaint route fails. Teams need the person or cohort, service task, barrier, governing source, decision owner, time window, evidence, and unresolved work before interpreting access.

Build Rina's digital-accessibility product register

Rina records product and vendor, owner, user task, authentication, browser and device, keyboard path, focus order and visibility, labels, headings, landmarks, contrast, zoom and reflow, errors, time limits, CAPTCHA, file upload, accessible PDF or alternate format, captions and transcripts, audio description where needed, telehealth interpreter and AAC layout, chat and relay compatibility, signature, payment, privacy, outage route, manual alternative, defect severity, release gate, vendor ticket, due date, retest, user confirmation, and version. She separates general web guidance from any technical standard that actually applies to the entity or contract.

Protect rights and clinical boundaries in Rina's workflow

Rina's twenty client-facing websites, portals, forms, PDFs, messages, videos, telehealth, signature, scheduling, and payment workflows preserve dignity, privacy, direct client communication, AAC, language and disability access, consent and assent when applicable, safety, complaint routes, and nonretaliation. Access work does not authorize clinical treatment, and a clinical decision cannot erase an applicable access duty.

Work through Rina's fictional example

Rina audits 20 workflows. Fourteen support end-to-end completion. Six remain held for a keyboard trap, an unlabeled portal control, an inaccessible PDF, missing video captions, a timed signature page, and a telehealth layout that hides AAC while screen sharing. Every request, review, offer, hold, decision, implementation, complaint, defect, correction, and closure keeps its source, owner, date, version, and validation evidence.

Use Rina's denominator carefully

End-to-end workflow readiness is 14 of 20, or 70.0%. The six held workflows remain visible. Pages, components, defects, users, tasks, sessions, releases, and validated fixes are different units.

Assign Rina's decisions to qualified owners

Rina's product owner manages defects and vendor work. Accessibility specialists test and interpret relevant standards. Privacy and security owners review data routes. Clinicians protect communication and service content. Operations maintains effective alternatives. The person using assistive technology supplies valuable evidence without carrying responsibility for quality assurance.

Address Rina's main access risk

Automated scanners catch only part of accessibility. Pair them with manual keyboard, assistive-technology, content, document, and task-flow testing.

Test Rina's control with a real task

Rina repeats the failed task after the fix using the same assistive conditions, checks data preservation and error recovery, and records whether the alternative route remained available throughout remediation.

Place Rina's access work inside accountable operations

Rina's digital-accessibility product register uses the CASP Organizational Guidelines public overview only for high-level business, clinical-operations, and risk-management scope in autism service organizations. CASP sells the detailed guidelines. This page's access workflow is Finni's editorial model and requires separate legal, clinical, client, facility, language, digital, payer, and privacy review.

Apply current behavior-analyst ethics to Rina's role

Rina uses the current BACB Ethics Code, which governs BCBA and BCaBA certificants and people who completed an application. The Code addresses nondiscrimination, competence, understandable communication, cultural responsiveness, client involvement, consent and assent when applicable, confidentiality, documentation, referral, and evaluation. BACB has no separate organization or corporation jurisdiction, so entity duties require their own sources and owners.

Scope Title III carefully for Rina

The DOJ Title III overview describes duties for covered businesses open to the public, including equal opportunity, reasonable policy modifications, effective communication, service animals, and physical access. It distinguishes new construction and alterations from barrier removal in existing facilities and recognizes rule-specific limitations. Rina verifies entity, facility, and service scope before applying a requirement.

Make Rina's communication effective

Rina's interaction review draws on DOJ effective-communication guidance for covered title II and title III entities. The needed auxiliary aid or service depends on the communication method, nature, length, complexity, and context. The goal is effective two-way communication with the person receiving services and, when applicable, an appropriate companion.

Treat Rina's digital route as service access

The DOJ web-accessibility guidance explains the agency's view that ADA nondiscrimination and effective-communication duties apply to services offered on the web by state and local governments and public accommodations. DOJ does not present one detailed federal Title III technical standard on that page. Rina therefore identifies the actual law or contract and uses task testing plus effective alternatives.

Check HHS-funded program scope for Rina

The current HHS Section 504 page describes the 2024 Part 84 final rule for programs or activities receiving HHS financial assistance and HHS-conducted programs. It highlights medical-treatment nondiscrimination, accessible medical diagnostic equipment, and web and mobile access. Rina first verifies recipient, program, implementation-date, and current legal status rather than assuming every practice is covered in the same way.

Use the Part 84 fact sheet as a scoped map for Rina

The HHS Section 504 fact sheet summarizes equal opportunity, medical-treatment decisions, communication, reasonable modifications, retaliation, direct-threat analysis, and stated limitations for in-scope recipients. The fact sheet is educational and points to the rule. Rina routes any limitation, safety exception, or denial through qualified review and records another effective action when required.

Verify language-access duties for Rina

The HHS limited-English-proficiency page says Title VI and Section 1557 require covered programs to provide applicable language-access services free of charge. Rina verifies the entity and program, current rule, language need, interpreter and translator qualifications, interaction stakes, privacy, and any broader state or contract requirement. Staff never assume that some conversational English resolves a technical care discussion.

Keep Rina's Section 1557 status current

HHS's June 2026 notice reports partial vacatur of provisions in the 2024 Section 1557 final rule after Tennessee v. Kennedy and says core protections remain in effect. Rina treats current regulatory text, court orders, HHS notices, program scope, compliance dates, and qualified counsel review as separate status evidence. An older checklist cannot settle the current rule.

Preserve AAC throughout Rina's workflow

Rina's communication safeguards use the ASHA AAC practice portal, which describes aided and unaided AAC and says users should always have access to their tools or devices. Primary and backup access, positioning, vocabulary, charging, wait time, privacy, and partner response belong in intake, assessment, service, telehealth, billing, complaints, and transitions.

Choose Rina's next review trigger

Review after a release, vendor change, authentication update, new form or PDF, telehealth feature, complaint, failed task, privacy change, browser update, or governing-standard revision. Record the changed fact, immediate interim access, affected people and programs, governing source, qualified decision owner, deadline, communication, remediation, and validation result.

Close Rina's record with accountable evidence

Review the digital-accessibility product register with Rina, clients and authorized people as applicable, qualified clinical and access professionals, operations leaders, and the specialists named in the manifest. Confirm that disability and language access, clinical appropriateness, professional scope, payer status, capacity, safety, privacy, costs, decisions, complaints, disparities, and remediation remain distinct. Keep this page draft and noindex until every required external review is complete.

Related resources

Sources