Accessibility
Learn how LabPreCheck supports blind users, screen readers, keyboard navigation, and accessible browser-based dental workflows.
Browser-Based Access
Core workflows are built around browser semantics, form labels, keyboard operation, and status text.
Assistive Technology Support
Screen-reader labels, landmarks, status announcements, and field relationships help users move through the same workflow.
Non-Visual Workflow Paths
Visual clinical materials keep file names, types, and available actions accessible so users can continue the workflow.
Accessibility Commitment
LabPreCheck is built to support blind users and other users who rely on assistive technology.
LabPreCheck is a browser-based workflow application for dental practices and labs. The product is designed to support people who use screen readers, keyboard navigation, and other assistive technologies.
Our accessibility work is guided by the Web Content Accessibility Guidelines, with a current focus on screen-reader and keyboard support that can be delivered without changing the existing visual product experience.
Product Support
The product accessibility model is based on semantic structure, clear labels, and predictable interaction behavior.
LabPreCheck uses semantic HTML, accessible names, and progressive enhancement patterns so assistive technology can understand the same workflow that sighted users see on screen.
Primary navigation and page structure use landmarks and meaningful headings.
Forms use explicit labels, helper text, and field-level error relationships wherever the user needs to act.
Dialogs and overlays manage focus, identify their purpose, and provide keyboard paths for close actions.
Loading, validation, and submission outcomes use text and assistive-technology status patterns instead of relying on color alone.
Non-Visual Workflows
Visual dental materials are handled with accessible surrounding workflow controls.
Some dental workflows involve images, scans, shade references, PDFs, or 3D meshes. LabPreCheck does not claim that visual clinical content can be fully interpreted non-visually by software alone. Instead, the application provides accessible ways to navigate, label, upload, download, submit, and act on that content.
Tooth selection supports direct tooth-number entry.
Shade entry supports direct text input and screen-reader-readable quick-pick controls.
File uploads expose labels, supported file guidance, and selected file metadata.
Preview-only visual materials are paired with file names, types, and available actions so users can continue the workflow non-visually.
Testing And Review
Accessibility work is verified through automated checks and manual interaction testing.
Accessibility is not a one-time switch. LabPreCheck treats it as an implementation and verification practice across shared components, public pages, and authenticated workflow surfaces.
Automated accessibility checks are used to catch common WCAG and ARIA issues.
Keyboard navigation is reviewed for public pages, forms, dialogs, and custom controls.
Screen-reader review is part of the release checklist for accessibility-sensitive changes.
Supported Environments
Modern browsers and current assistive technology provide the best accessibility experience.
Use a current browser release.
Use current assistive technology where possible, such as VoiceOver or NVDA.
Contact support if an accessibility barrier prevents a practice or lab workflow from being completed.