Accessibility at Fulcrum

• Keyboard operation Not yet tested

  Fulcrum's controls are standard links, buttons, tabs, and form fields from the Renkara and Vantalect design libraries. A keyboard-only walkthrough of every screen has not been recorded.

• Screen reader landmarks and labels Partly supported

  axe-core, which checks names, labels, roles, and landmark structure, found no serious or critical violations on the screens we scanned. The app has not been tested with a screen reader.

  Evidence

  • renkara-tools/screenshots/captures/fulcrum-a11y.spec.ts: axe-core 4.14.0 on 12 screens (dashboard, day, records, people, estimates, drafts, cost, projects, predict, users, teams, roles) in light and dark at 375 and 1440 pixels, 48 scans, 0 serious or critical violations (output/fulcrum/a11y.json)
  • fulcrum/frontend/src/__tests__/accessibility.test.tsx: vitest-axe over the rendered app

• Contrast in light and dark Partly supported

  axe-core's color-contrast rule ran on every scanned screen in both themes and found nothing serious or critical. The check covers the seeded data on those screens, not every possible state.

  Evidence

  • The same 48-scan run, color-contrast rule included, in light and dark
  • fulcrum/frontend/e2e/vantalect.spec.ts: axe on every page in both appearances at 2560, 1920, 1280, 375, and 360 pixels

• Reduced motion Partly supported

  The app's stylesheet shortens animation and transition time to almost nothing under prefers-reduced-motion, and the charts draw at full size at once. Other screens have not been checked one by one.

  Evidence

  • fulcrum/frontend/src/global.css: a prefers-reduced-motion block that removes animation and transition time
  • fulcrum-ui/src/components/charts.motion.test.tsx: the bar chart draws at full height under prefers-reduced-motion

• Text resize and zoom Not yet tested

  Resizing text to 200 percent has not been tested in the app.

• Mobile and touch Partly supported

  Every screen was scanned at 375 pixels wide in both themes with no sideways scrolling, and the records list has a phone layout. The same scan found interactive controls smaller than 44 by 44 pixels on every screen, so touch targets are not yet at that size throughout.

  Evidence

  • fulcrum-a11y.spec.ts records each screen's horizontal overflow at 375 pixels (0 on all 48 scans) and counts controls under 24 and 44 pixels
  • fulcrum/frontend/e2e/vantalect.spec.ts: sideways scroll and 44-pixel targets at 375 and 360 pixels

No WCAG conformance level is claimed for Fulcrum or for this website. The checks below are automated scans and layout tests. No one has audited either against WCAG or tested them with assistive technology.

• Structure

  A skip link, labeled landmarks (header, navigation, main, footer), one h1 per page, and headings that do not skip levels.

• Keyboard and focus

  Links and buttons are native elements, so they work from the keyboard. Focus is drawn as a visible ring, and the menu closes with Escape.

• Contrast

  Text meets 4.5 to 1 in both the light and dark themes, checked against the stylesheet by the test suite.

• Motion

  Transitions and animation switch off when your system asks for reduced motion.

• Small screens and zoom

  Layouts hold at 375 pixels wide with no sideways scrolling, text resizes with the browser, and touch targets are at least 44 pixels.

• Automated scan

  Every page is scanned with axe-core at 375 and 1440 pixels in light and dark, and the checks fail on any serious or critical violation. Automated tools find only part of the problems, so this is a floor, not proof.

• Images

  Every product screenshot has a text description and comes in a light and a dark version that follows your theme.

• Your theme choice

  The theme follows your system setting until you pick one with the button in the header.