Accessibility is a representation contract, not a voice-provider dependency

Use the accessibility technology already on your device.

FoldSense keeps visible text, semantic HTML, ARIA output and machine-readable state available whether browser speech, a sponsor, WebGL, or haptics are present or not.

01 / THIS DEVICE

Capability check

No test run yet.

02 / NATIVE ASSISTIVE TECH
03 / RELEASE EVALUATION STACK

Automated checks plus real assistive-technology checks.

Automated

  • Static semantic/landmark validator in the repository.
  • axe-core browser scan on desktop and mobile viewports.
  • Keyboard focus order and visible-focus checks.
  • Zoom/reflow, reduced motion and forced-colors checks.
  • Console/runtime error check for core pages.

Manual

  • macOS/iOS: VoiceOver.
  • Windows: Narrator.
  • Android: TalkBack.
  • Keyboard-only navigation at desktop and narrow widths.
  • Verify no required information is audio-only, color-only, motion-only, or haptic-only.

Automated scans can catch many common WCAG failures, but they do not establish complete conformance or third-party certification.

04 / TEST MATRIX
EnvironmentPrimary screen readerSpeech input/output strategyHaptics
macOS Safari/ChromeVoiceOverPre-rendered local audio or browser speech; text/ARIA alwaysVisual/text fallback; gamepad if available
Windows Edge/ChromeNarratorBrowser/native speech; text/ARIA alwaysGamepad when exposed
iPhone/iPad SafariVoiceOverVoiceOver/native speech; text/ARIA alwaysStandard web vibration may be unavailable
Android ChromeTalkBackTalkBack/browser speech; text/ARIA alwaysVibration API where supported