Design Practices
We use the following practices where they apply and continue to review them as pages and tools change:
- Semantic Structure: We use standard HTML landmarks such as
<header>,<nav>,<main>,<footer>and<dialog>where appropriate, and aim for a logical heading hierarchy. - Skip Links: Shared page templates include a skip link to the main content. If one is missing or does not move focus as expected, please report it.
- Keyboard Access: We design buttons, inputs, menus, and dialogs for keyboard use, including visible focus and expected keyboard controls. A specific workflow may still have barriers; please report them.
- Visible Focus: We aim to keep keyboard focus indicators visible and avoid hiding outlines without a usable replacement.
- Form Controls: We aim to provide visible labels for inputs and selects, with associated descriptions and field errors where applicable. These details can differ by tool.
- Color and Contrast: We use the design system to target readable contrast for text and controls; individual pages and states still need review.
- Touch Use: We design interactive controls for touch use and review target size as part of responsive checks.
- Reduced Motion: Where non-essential motion is present, we aim to respect
prefers-reduced-motion: reduce. - Alternatives to Dragging: File tools provide a standard picker alongside drag-and-drop. We review keyboard alternatives for reordering controls.
Testing Methodology
Accessibility checks are ongoing and coverage varies as features change. We use automated checks and manual review for selected keyboard, zoom, browser, and assistive-technology flows. We have not verified every route with every browser and screen reader combination; report a specific barrier so we can investigate it.
Reporting Accessibility Barriers
We work to improve the accessibility of FivoTools. If you encounter any barrier, unannounced element, keyboard trap, or contrast difficulty, please tell us:
- Email:[email protected]
- Issue draft:Prepare an accessibility report
Please include the specific tool or page URL, the assistive technology you were using (e.g., NVDA, VoiceOver, keyboard-only), and a brief description of the issue. We review reports and prioritize fixes based on impact and scope.