Accessibility

MarGioM wants the website, forms, request tracking, and client portal experience to be usable, readable, and practical across devices and input methods.

Readable Experience
MarGioM aims to keep content readable across dark and light sections, desktop and mobile screens, and different zoom levels.
  • Text should have strong contrast against the section background.
  • Long paragraphs should use comfortable line height and practical spacing.
  • Gold is used as an accent, not as body text on low-contrast backgrounds.
  • Responsive layouts should avoid clipped text and horizontal overflow.
Keyboard and Form Access
Visitors should be able to navigate important actions and complete forms without relying only on a mouse.
  • Navigation, forms, buttons, and links should expose visible focus states.
  • Form fields should have clear labels, validation messages, and helpful placeholders.
  • Required actions such as quote submission, request tracking, and support tickets should be reachable through keyboard interaction.
  • Disabled, loading, and error states should remain understandable.
Motion and Interaction
Animations should support the experience without becoming required for understanding or causing unnecessary distraction.
  • Animations should be subtle, professional, and avoid rapid flashing or excessive movement.
  • Important content should remain available even when motion is reduced or unsupported.
  • Hover effects should not hide text, reduce contrast, or change layout unexpectedly.
  • Interactive demo previews should remain understandable as static content.
Ongoing Improvement
Accessibility is an ongoing process, especially as MarGioM adds new forms, dashboards, portal features, files, and payment flows.
  • New public pages, admin workflows, and client portal screens should be reviewed before launch.
  • PDFs, DOCX files, proposal downloads, and uploaded documents may depend on their source content and should be improved over time.
  • Known issues should be tracked and prioritized when they affect core actions.
  • Feedback from real users should guide future accessibility improvements.

Accessibility feedback

Report an access issue

If you cannot access content, submit a form, read a page, download a document, or use request tracking/client portal features, send a support ticket with the page URL, device/browser, and a short description of the problem.

Report accessibility issueRead privacy policy

Last updated June 18, 2026. MarGioM aims to align with practical accessibility standards such as WCAG guidance where possible and to improve as the platform grows.