Our Commitment

We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

What We've Done

• Semantic HTML: We use proper heading hierarchy, landmark elements (<nav>, <main>, <footer>), and ARIA attributes to convey structure to screen readers.
• Keyboard navigation: Core workflows can be completed using keyboard navigation alone.
• Color contrast: Text and interactive elements meet minimum contrast ratios against their backgrounds.
• Focus indicators: Visible focus outlines are preserved on interactive elements.
• Form labels: All form inputs have associated labels and descriptive error messages.
• Responsive design: The application adapts to different screen sizes and supports browser zoom up to 200% without loss of functionality.
• Alternative text: Images that convey information include descriptive alt text.
• Bootstrap 5: Our UI framework includes built-in accessibility features that we build on.

Known Limitations

We are actively working to improve accessibility across all areas of the application. Some areas that we know are not yet fully conformant include:

• Complex charts and graphs (in Reports) — visual data is not yet accompanied by tabular data alternatives. We plan to add data table equivalents in a future release.
• Drag-and-drop interfaces (Job Priority Board, Oven Scheduler) — these currently lack keyboard-accessible equivalents. Workarounds exist via the standard list views.
• PDF exports — generated PDFs (invoices, work orders) are not currently tagged for screen reader accessibility.
• Third-party components — the Stripe payment element and some calendar widgets are third-party and may not fully conform to WCAG 2.1 AA.

Assistive Technology Compatibility

We test the core application with the following assistive technologies:

• NVDA with Firefox (Windows)
• VoiceOver with Safari (macOS and iOS)
• Keyboard-only navigation (Chrome, Edge, Firefox)

Other combinations may work but have not been formally tested.

Need Help?

If you experience any accessibility barriers while using Powder Coating Logix, or if you need content in a different format, please contact us:

We aim to respond to accessibility requests within 2 business days. Please describe the barrier you encountered and what you were trying to do — this helps us prioritize fixes and provide an immediate workaround where possible.

Formal Complaints

If you are not satisfied with our response to your accessibility request, you may contact the relevant supervisory authority in your jurisdiction. In the United States, the Department of Justice Civil Rights Division handles ADA-related complaints.

Ongoing Improvement

Accessibility is not a one-time checkbox — it is an ongoing commitment. We review and improve accessibility with each release. If you notice a regression or have a suggestion, please let us know.