Skip to main content

Clear to read.
Practical to use.

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.

Designed to be understood
AaReadable words.
Visible meaning.
Draft for review

A status expressed in words.

Tab
A clear place to focus

Logical keyboard navigation.

Text stays available

Useful information beyond an image.

Design specimen. Accessibility is verified per workflow.

Make each step
understandable and usable.

The design system includes requirements for keyboard use, touch, focus, reflow, language, documents, and assistive technology.

  1. Visit workspace
    YOUR NEXT STEP
    Review visit summary
    TabMove focus
    01

    Find your way

    Use logical navigation, visible focus, skip links, and keyboard-operable controls.

  2. Draft recordReview before signing
    Signed recordReview completed
    Sync pending Saved on this device
    02

    Understand the state

    Read status and next actions through words and symbols alongside color.

  3. Visit instructions Sample

    Your plan,
    clearly written.

    Keep the next steps close.
    Return to them when you need.

    Aa Readable textPrint
    03

    Read the care plan

    Keep useful text and supported document formats available for patient instructions.

  4. Accessibility review Example
    Workflow
    Visit summary
    Environment
    Browser + keyboard
    Version / date
    Record with review
    Evidence needs a defined scope
    04

    Review the evidence

    Assess tested workflows, platforms, review dates, and known limitations.

Illustrative design principles. Accessibility conformance requires testing within the stated scope.

Keep navigation
within reach.

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.

Illustrative clinic workspace
PATIENT INSTRUCTIONS

A clear next step.

Read the visit summary

Your reviewed instructions stay together with the visit.

TabMove focus↵Open or close
Illustrative keyboard navigation · The outline identifies the focused item.
  1. 01Find the current focus
  2. 02Move through controls in a logical order
  3. 03Open and close disclosures from the keyboard
Draft

Review needed before signing.

Saved locally

Sync pending. The update is not yet synchronized.

Conflict

Compare both versions before resolving changes.

Illustrative states. Each state has a distinct symbol and an explicit next action.

Read the meaning
behind the status.

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 states

Keep care instructions
available as readable text.

Patient 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 guide

Check accessibility
against the actual workflow.

A design target does not establish that every screen, document, or integration has passed review.

Illustrative review

Define the test setup

Scope
Workflow and output
Evidence
Device, browser, assistive technology
Next action
Assess the stated setup
Review required
Review the environment actually tested.

Name the scope

Identify the workflow, output format, device, browser, and assistive technology being reviewed.

Illustrative comparison

Make limitations visible

Known gap

Document the limitation

Alternative route

Explain available assistance

Review alongside test results
Keep alternative access visible.

Keep gaps visible

Review known limitations and alternative access routes alongside any test results.

Illustrative review

Evidence has a version

Scope
Reviewed workflow
Evidence
Version and review date
Next action
Check evidence currency
Review required
No test date or result is implied.

Follow the review date

Check when evidence was recorded and which version it covers. Evidence will be published as it matures.

Questions about
accessible use.

Discuss the access needs and formats relevant to your clinic.

Is Bractis certified as fully accessible?

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.

Is essential accessibility part of every plan?

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.

Will every document format be supported at launch?

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.

How can I report a barrier or request another format?

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.

Tell us what
you need to access.

Share the task, the barrier, and the format that would help you use it.

Contact Bractis