Keyboard first
Every link, button and disclosure can be reached and operated with a keyboard, and the focus ring is a visible three-pixel outline rather than something removed for looks.
Accessibility
Speech is a tool for people who would rather speak than type, so being hard to use would be a strange way to fail. Here is where we actually are.
On this website
Every item below is verifiable by opening this page, which is the only kind of accessibility claim worth printing.
Every link, button and disclosure can be reached and operated with a keyboard, and the focus ring is a visible three-pixel outline rather than something removed for looks.
The first thing a keyboard reaches on every page is a skip link past the navigation.
Headings are headings, navigation is a nav landmark, the comparison tables are tables with row headers. A screen reader gets the shape of the page, not a wall of text.
If your system asks for reduced motion, the animations and smooth scrolling stop. Nothing on these pages depends on movement to be understood.
Body text and buttons are kept at the usual 4.5:1 minimum against their background. It is why our buttons are not the brighter blue the apps use, which would have failed it.
Every page reflows to a phone without a sideways scroll. Wide tables scroll inside their own frame instead of dragging the page with them.
Where we fall short
We have not had an independent audit, and we do not claim a WCAG conformance level. The apps have had less attention than this website: the Mac app carries VoiceOver labels on its setup flow, but we have not tested the whole app end to end with a screen reader, and we have not tested at all with switch access or voice control. The dictation shortcut is a held modifier, which is hard for anyone who cannot hold two keys, and there is no alternative to it yet.
If any of this stops you using Speech, that is the most useful mail we can get. It moves things up the list.
SupportSpecifics beat a standard. What you were doing, on what, and what happened.