Accessibility status, including what is still unproven.
Fluid targets WCAG 2.2 AA as a product and review standard. This page reports implementation safeguards and their evidence scope; it does not claim WCAG conformance, universal usability, or an accepted accessibility statement.
Product target
WCAG 2.2 AA
A design and acceptance target—not a conformance result.
Source safeguards
Regression-locked
Key shared semantics, focus, responsive, and preference patterns have source contracts.
Assistive technology
Not accepted
Current screen-reader and representative authenticated journey evidence is absent.
Conformance report
Not published
No independent audit, VPAT, or scoped conformance statement is claimed.
Interaction safeguards under regression control
These controls reduce known barriers. They remain engineering evidence until the rendered product is accepted with users, browsers, devices, and assistive technologies.
Keyboard and landmarks
Public and application shells provide a skip link and named main landmark. Native links, buttons, disclosures, menus, dialogs, and form controls are preferred over reconstructed interaction semantics.
Persistent error focus
Shared form recovery links fields to inline guidance and moves focus to a committed in-context alert after returned or transport failures, including repeated failures.
Touch-visible actions
Relationship actions stay visible on touch and coarse-pointer devices. Fine-pointer hover reveals are paired with focus-within behavior rather than hiding keyboard operations.
Names and descriptions
Application custom fields expose an explicit label association, icon-sized buttons are named, and every inventoried shared dialog caller pairs its title with a workflow-specific description.
Responsive structure
The shell, public navigation, shared registers, dialogs, and reviewed workspace field grids reflow instead of forcing desktop-only widths; narrow public navigation requires no client JavaScript.
Motion preference
A global reduced-motion boundary minimizes nonessential animation and transition duration when the operating system requests reduced motion.
Separate source coverage from human acceptance.
Automated checks catch valuable regressions but cannot establish comprehension, assistive-technology behavior, or conformance by themselves.
Current source and production build
Verified in repositoryStatic contracts inventory labels, dialog descriptions, semantic click targets, named icon controls, hover/touch visibility, focus recovery, reduced motion, responsive grids, and public landmarks.
Public automated browser checks
Historical candidate onlyA previous locally servable candidate passed serious/critical Axe, keyboard, and responsive checks in desktop/mobile Chromium and WebKit. New public pages have no fresh rendered pass on this host.
Authenticated keyboard and mobile journeys
Not executedThe approved synthetic personas and reproducible data environment required for authenticated acceptance have not been provisioned.
Screen-reader acceptance
Not completedNo recorded VoiceOver plus Safari or NVDA plus Firefox/Chrome journey has been accepted for the current candidate.
Zoom, reflow, contrast, and real-device review
Not completedThere is no current accepted 200–400% zoom/reflow, manual contrast, forced-colors, speech-input, switch-control, or representative real-device report.
Independent audit and conformance documentation
Not publishedNo independent accessibility audit, remediation acceptance, conformance report, VPAT, or legal accessibility statement is published.
What has to happen before a conformance statement
The next evidence must be attached to one immutable release candidate and cover the same authenticated workflows buyers will actually use.
- 1
Approve the exact authenticated personas, synthetic records, devices, browsers, and assistive technologies for each Gate A journey.
- 2
Record full keyboard order, visible focus, focus containment/return, error recovery, and no-pointer operation on the exact candidate.
- 3
Complete VoiceOver plus Safari and NVDA plus Firefox or Chrome reviews with issue severity, owner, fix evidence, and retest.
- 4
Test 200% and 400% zoom/reflow, text spacing, orientation, target size, forced colors, manual contrast, and long localized-looking values.
- 5
Review data tables/cards, relationship controls, command search, the process map/register alternative, dialogs, notifications, and time-sensitive states.
- 6
Commission an independent audit and publish only the accepted conformance scope, exceptions, review date, and accountable contact path.
What this accessibility status does not claim
It does not claim that Fluid conforms to WCAG, is accessible to every person, supports every assistive technology, meets a procurement or legal requirement, has no accessibility defects, or has completed independent review. It also does not turn historical public automation into evidence for the current authenticated product.