MinuteFolio

Accessibility

The interface is designed to keep inputs, errors and results understandable.

Using the controls

Fields have visible labels, and buttons describe their actions. Paid and Unpaid remain text labels rather than color-only distinctions. Errors identify the relevant field and preserve its value so it can be corrected. Where a modal is used, keyboard focus should remain within its active controls and return to the triggering control when it closes.

Reading the record

Times and totals use aligned numerals. Mobile layouts stack controls instead of shrinking a desktop table. Both color themes retain text, boundary and focus contrast. Content tables include headings, and print output removes application controls while retaining necessary record information.

Motion and feedback

Routine feedback should not depend on an animated counter. Reduced-motion preferences should remove nonessential motion. Saving and exporting need clear status messages; a storage error should remain available long enough to act on it. A color change alone is not sufficient feedback.

Verification and known limits

These are product design and implementation requirements, not a claim of certification. Actual keyboard, focus, screen-reader, zoom, contrast and mobile checks must be verified in the released build. Font and script support must be assessed for any future language; English testing does not establish support for every writing system.

Help

Docs provides field and workflow instructions. To report an accessibility barrier, email support@minutefolio.site with the affected page, browser, assistive technology if relevant, and the step that caused difficulty. Share only the details needed to reproduce the issue. No formal accessibility certification is claimed.

Keep going