Accessibility at Slide Practice
We want Slide to be usable by every practitioner, including those who navigate with a keyboard, a screen reader, magnification, or reduced motion. This page is honest about what we do today, the parts still being brought up to standard, and how to reach a person if something gets in your way.
Last reviewed July 4, 2026.
Our goal
Slide Practice aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, both on this marketing site and inside the app. That standard is the target we build and check against. We are a small team, so accessibility is an ongoing practice, not a finished box we tick once. We keep working at it as the product grows.
What we do
These are the things we build in by default, and check when we ship changes:
- Semantic landmarks. Pages use real headings and structural regions such as header, navigation, main, and footer, so assistive technology can map the page and let you jump straight to the content.
- Keyboard operability. You can reach and use links, buttons, menus, and forms with the keyboard alone. A skip link at the top of each page jumps you past the navigation to the main content.
- Visible focus. When you tab through a page, the element you are on shows a clear outline. We do not strip focus styles.
- Sufficient colour contrast. Our forest, paper, and amber palette is chosen so text and meaningful elements meet the AA contrast ratios for the sizes we use them at.
- Reduced motion support. If your device asks for reduced motion, the fade and slide animations are turned off and the page renders plainly. Nothing important depends on movement.
- Descriptive alt text. Images that carry meaning have text descriptions. Images that are purely decorative are hidden from assistive technology so they do not add noise.
- Labelled forms. Every form field has a programmatic label, so a screen reader announces what each field is for.
- Readable text. Text can be resized and reflows without breaking the layout, and we keep line lengths comfortable for reading.
Known limitations
We would rather tell you the truth than claim a clean record. A few areas are still being brought fully up to standard:
- Some longer, legacy long-form pages were written before our current checks and are still being reviewed and updated, so a heading order or a contrast value here and there may not yet be perfect.
- A small number of third-party embeds, such as analytics or any future booking or payment widgets, are not fully under our control, and their accessibility can vary. Where that happens we work to offer a plain alternative.
- New features ship first and get a full accessibility pass shortly after, so the very newest part of the app may briefly be ahead of our review.
If you hit one of these and it blocks you, please tell us. Real reports from real people are the fastest way we find and fix the gaps.
How to give feedback or ask for an accessible alternative
If any part of Slide is hard to use, or you need information in a different format, email support@slidepractice.com. Tell us the page or screen, what you were trying to do, and the device or assistive technology you use, if you can. The more you can share, the faster we can help.
We reply within one business day. If something is blocking you right now, say so in your message and we will treat it as urgent and find you a way through in the meantime.
How we keep checking
We test with a keyboard and a screen reader as we build, run automated checks on the site, and review pages against WCAG 2.2 AA. This statement is reviewed and updated as the product changes. Slide Practice is operated by Vikrant Singh, based in Manila, Philippines, so the people who build the product are the same people who read your feedback.
This statement covers slidepractice.com and the Slide Practice app. Last reviewed July 4, 2026.