Updated September 14, 2026
Usable vendor compliance is the standard
Accessibility is a product requirement across the complete DueFiles workflow. DueFiles uses the Web Content Accessibility Guidelines, WCAG 2.2 Level AA, as the design and evaluation standard for public pages, account flows, organization workspaces, vendor and broker submission, requirement review, remediation, and status.
The goal is direct: coordinators, risk leaders, property operators, vendors, brokers, and job candidates can perceive the information, navigate the interface, understand the task, and complete the action with the tools they use.
Interface practices
The DueFiles interface is built around practices that make operational work easier to perceive and control:
- semantic landmarks, heading order, labels, lists, tables, and native controls;
- keyboard-reachable actions with visible focus treatment;
- status names, icons, and text that do not rely on color alone;
- responsive layouts, readable type, and sufficient interface contrast;
- plain-language instructions, associated validation messages, and live status feedback; and
- reduced visual complexity for dense compliance records and review decisions.
Core workflows covered
Accessibility work covers the tasks that move a vendor file from first request through renewal:
- reviewing public product, solution, pricing, security, privacy, legal, and help content;
- creating an organization account, signing in, navigating the workspace, and signing out;
- adding and importing vendors, assigning requirements, and interpreting status;
- using a vendor or broker submission link, understanding the request, and submitting supported content;
- reviewing extracted fields, requirement results, open gaps, exceptions, and activity history; and
- working renewal and reminder actions across the vendor roster.
Customer-provided documents, imported records, and customer-selected third-party destinations remain under their respective owners' control. DueFiles reviews reports when that content blocks a core DueFiles task and works with the customer on an accessible path.
Accessibility evaluation
Evaluation combines task-based review with checks for keyboard operation, focus visibility and order, accessible names, landmark and heading structure, zoom and reflow, contrast, status communication, form instructions, error handling, and screen-reader output. Review follows complete user journeys because isolated components cannot prove that a coordinator or outside submitter can finish the task.
Enterprise documentation
Enterprise buyers can define accessibility criteria, product scope, evaluation evidence, documentation format, remediation expectations, and accommodation requirements as part of procurement. DueFiles maps the evaluation to the reviewed product release and records contracted commitments in the signed Enterprise agreement. Start that process through the Enterprise contact path.
Report an accessibility barrier
Email accessibility@duefiles.com. Include the page or workflow, the task you were completing, the barrier, the browser, the assistive technology used, and a preferred contact method. Do not include passwords, authentication links, insurance documents, or other sensitive records.
DueFiles reviews the report, confirms the affected workflow, identifies an accessible completion path, and routes the product defect for remediation. Security vulnerabilities belong with the process on the Security page.
Alternative formats and accommodations
Request this statement, the Privacy Notice, or the Terms of Service in an alternative format by emailing accessibility@duefiles.com. Candidates use the same address to request a reasonable accommodation for a published hiring process. DueFiles handles accommodation information only for the request and according to the Privacy Notice.
Accessibility questions
Which standard guides DueFiles? WCAG 2.2 Level AA is the design and evaluation standard for DueFiles-maintained public and product interfaces.
What belongs in a barrier report? Include the page or workflow, the task, what happened, the browser, assistive technology, and a preferred contact method. Screenshots can help when they omit sensitive vendor and account information.
Can legal pages be provided in another format? Yes. Email the accessibility team to request the Privacy Notice, Terms of Service, or this statement in an alternative format.
How do Enterprise buyers evaluate accessibility? The evaluation can define scope, criteria, evidence, documentation, remediation, accommodations, and contractual commitments for the reviewed release.