Define the test setup
- Scope
- Workflow and output
- Evidence
- Device, browser, assistive technology
- Next action
- Assess the stated setup
Name the scope
Identify the workflow, output format, device, browser, and assistive technology being reviewed.
Bractis approaches accessibility through everyday clinic work: finding the next action, understanding the record, and receiving care instructions in a usable format.
Our web design target is WCAG 2.2 Level AA. This is a target, not a certification.
A status expressed in words.
Logical keyboard navigation.
Useful information beyond an image.
Design specimen. Accessibility is verified per workflow.
The design system includes requirements for keyboard use, touch, focus, reflow, language, documents, and assistive technology.
Use logical navigation, visible focus, skip links, and keyboard-operable controls.
Read status and next actions through words and symbols alongside color.
Keep the next steps close.
Return to them when you need.
Keep useful text and supported document formats available for patient instructions.
Assess tested workflows, platforms, review dates, and known limitations.
Illustrative design principles. Accessibility conformance requires testing within the stated scope.
Public navigation and shared controls use visible focus, logical order, and keyboard-operable disclosure. Skip links provide a route to the main content.
Touch targets, reflow, and reduced motion are part of the design requirements, alongside assistive-technology testing.
Your reviewed instructions stay together with the visit.
Review needed before signing.
Sync pending. The update is not yet synchronized.
Compare both versions before resolving changes.
Draft, offline, failed, signed, and conflict states need clear labels and next actions. Text, icons, and patterns support the meaning alongside semantic color.
Explore readable save statesPatient information should remain usable beyond a single image or document. The planned scope includes semantic HTML, print, readable text, and accessible PDF where supported.
Language preferences and supported audio or visual aids complement text. Confirm the formats and tested scope available for your clinic.
Read the patient-output guideA design target does not establish that every screen, document, or integration has passed review.
Identify the workflow, output format, device, browser, and assistive technology being reviewed.
Document the limitation
Explain available assistance
Review known limitations and alternative access routes alongside any test results.
Check when evidence was recorded and which version it covers. Evidence will be published as it matures.
Discuss the access needs and formats relevant to your clinic.
No certification is claimed here. WCAG 2.2 Level AA is the web design target. Assessment requires evidence for a defined workflow, version, and testing environment.
Yes. Essential accessibility is part of the planned platform scope across plans. Supported formats and evidence should be confirmed for the workflow you intend to use.
Available formats and tested scope need to be confirmed during setup. The design direction includes readable text, semantic HTML, print, and accessible PDF where supported.
Use the contact form to describe the page or task, the barrier, and the format or assistance you need. Avoid including patient records or sensitive clinical information.
Share the task, the barrier, and the format that would help you use it.
Contact Bractis