Keyboard friendly
Navigation, links, dialogs and controls are designed to remain operable without requiring a mouse.
ACCESSIBILITY
We aim to provide an accessible experience across touch, keyboard, assistive technology, larger text and reduced-motion use, using WCAG 2.2 Level AA as our product target.
See our approachBUILT INTO THE EXPERIENCE
We use semantic structure, visible focus, labeled controls, keyboard operation, readable contrast and responsive layouts rather than relying on a separate accessibility mode.
Navigation, links, dialogs and controls are designed to remain operable without requiring a mouse.
Responsive layouts, useful touch targets and browser zoom support are part of the baseline experience.
Headings, labels, status text and semantic structure carry meaning so color is not the only clue.
Reduced-motion and device accessibility preferences are respected wherever the interface can honor them.
CONTINUOUS WORK
Automated checks are a gate, not a guarantee.We combine automated accessibility checks with manual and device-level review because a clean automated report cannot prove that every experience is accessible.
Touch-first, not touch-only.Mobile interaction remains comfortable while keyboard and assistive-technology paths stay available.
Report barriers directly.Accessibility is a dedicated support-request category so reports can be routed and acted on instead of disappearing into general feedback.
FOUND A BARRIER?
Use Contact CannaTally and choose Accessibility. If possible, include the page or task, device, browser and assistive technology involved. Do not include passwords, sign-in codes or unnecessary sensitive information.
Contact CannaTally