Navigation and focus
- Skip links move directly to main content
- Headings follow a logical page hierarchy
- Keyboard focus has a high visibility outline
- Links and buttons use descriptive text
Accessibility statement
DictationFlow aims to make setup, playback and content understandable and operable for a broad range of users. This statement defines current support, limitations and improvement priorities.
What is built in
The practice desk uses native form elements where practical so browsers and assistive technologies can expose expected behaviour.
Keyboard guide
Exact shortcuts can vary by operating system and browser.
| Key | Where | Expected action |
|---|---|---|
| Tab | Across the page | Move to the next interactive control |
| Shift + Tab | Across the page | Move to the previous interactive control |
| Enter or Space | Buttons and menu summary | Activate the focused control |
| ← / → | Target WPM range control | Decrease or increase the native slider value |
| ↑ / ↓ | Select fields | Move through available options |
Browser and screen reader commands may conflict. Set up the session first, then use the labelled player controls that work best with your environment.
Product specific limits
Hiding source text helps shorthand from speech practice, but that option should remain under the user’s control.
Voice availability, pronunciation, rate and reliability depend on the browser and operating system. Some voices may use network processing. People who need consistent screen reader output may prefer their established assistive technology for general reading.
Stenography mode can hide the source during playback. Users can turn that setting off or pause and reveal the passage. The source hiding exercise is optional, not an access requirement.
A countdown and moving cadence are inherent to some exercises. Choose no countdown, pause when needed, or use a lower target WPM. Formal assessment accommodations are controlled by the relevant institution.
OCR can produce incorrect or disordered text, especially with handwriting, columns, tables and low quality scans. Extracted content must be reviewed before it is safe to practise from.
Known improvement areas
Different browser, voice and assistive technology combinations still need broader testing.
Pause, resume and voice loading can behave differently across browsers, especially on mobile devices.
Frequent word by word announcements would interrupt a screen reader. The interface prioritises concise status text, which may not suit every workflow.
Imported multiple column or visually complex pages may not preserve a meaningful order after extraction.
Report a barrier
Use the feedback form and select Accessibility issue. A useful report includes:
Do not include private practice text or sensitive personal information. The feedback form uses an external processor and leaves your device, as explained before submission.
Configuration