Legal

Accessibility Statement

We are committed to making this site usable for everyone.

Need help right now? If you have trouble using any part of this website, please contact us by email at Mindfulsolutionstherapy33@gmail.com or by phone at (725) 290-3009. We will work with you to provide the information, service, or transaction you need through an alternative method — by phone, by email, or in person if appropriate.

Effective date: April 12, 2026  ·  Last reviewed: April 12, 2026  ·  Version: 1.0

1. Our Commitment

Mindful Solutions Therapy LLC is committed to ensuring digital accessibility for people with disabilities. We believe mental-health information and services should be usable by everyone, and we treat accessibility as an ongoing responsibility, not a one-time checklist. We regularly review this site and apply relevant accessibility standards, and we welcome your feedback when something falls short.

2. Standards We Follow

We aim to conform to the following standards:

  • Web Content Accessibility Guidelines (WCAG 2.1) at Level AA — our primary target.
  • Selected WCAG 2.2 additions where we have been able to apply them (see Section 4).
  • Title III of the Americans with Disabilities Act (ADA) — we treat this website as a public accommodation and design it to be usable by people with disabilities.
  • Section 508 of the Rehabilitation Act — referenced as a complementary framework; the site is not a federal property but we align with 508's spirit for consistency.

Conformance level: This website is substantially conformant with WCAG 2.1 Level AA. "Substantially conformant" means that most of the site meets the standard, with some known limitations (see Section 5) and some content we do not fully control (see Section 6).

3. Accessibility Features Built Into This Site

We have built the following accessibility features into this website:

3.1 Structure and navigation
  • Skip-to-main-content link at the top of every page lets keyboard and screen-reader users bypass navigation and jump to the main content.
  • Semantic HTML5 landmarks — every page uses <header>, <nav>, <main>, and <footer> so assistive technology can orient users.
  • Logical heading hierarchy — each page has a single <h1> followed by properly nested <h2> and <h3> sections.
  • Breadcrumb structured data on interior pages.
  • lang="en" on the <html> element so screen readers pronounce content correctly.
3.2 Keyboard, focus, and input
  • Full keyboard navigability — every interactive element (links, buttons, form fields, menu toggles, FAQ accordions, cookie banner, "scroll to top" button) is reachable and operable with a keyboard alone.
  • Visible focus indicators — a clear :focus-visible outline shows which element currently has keyboard focus, meeting WCAG 2.1 SC 2.4.7 and the stricter WCAG 2.2 SC 2.4.11 (Focus Not Obscured, Minimum).
  • Logical tab order that matches the visual reading order.
  • Touch-target sizing — interactive controls on mobile are at least 24×24 CSS pixels, aligning with WCAG 2.2 SC 2.5.8 (Target Size, Minimum), with most meeting the recommended 44×44 pixel comfort size.
3.3 Text, color, and layout
  • Color contrast — body text, links, and meaningful UI elements are designed to meet at least a 4.5:1 contrast ratio against their backgrounds (WCAG AA). Large text meets 3:1.
  • No reliance on color alone — links, errors, required-field markers, and state changes use shape, text, and icons in addition to color.
  • Responsive, zoomable layout — the layout reflows cleanly on small screens and remains usable when text is resized up to 200%. Viewport meta is set to allow user scaling.
  • Print stylesheet so important pages render cleanly when printed.
  • Readable type — minimum 16 pixel body text; ample line-height and paragraph spacing.
3.4 Images, media, and motion
  • Alt text on informative images; decorative images are marked with empty alt (alt="") so they do not clutter screen readers.
  • Reduced-motion support — scroll animations, smooth scrolling, and motion effects are disabled automatically when your system has prefers-reduced-motion: reduce enabled.
  • No auto-playing audio or video.
  • No content that flashes in a way that could trigger photosensitive seizures.
3.5 Forms and dynamic components
  • Explicit form labels — every input on the contact form has an associated <label>.
  • Required-field indicators using both visual markers and the required attribute.
  • Inline error messaging with an ARIA live region so errors are announced by screen readers.
  • ARIA state and role attributes on the nav toggle (aria-expanded, aria-controls), FAQ accordions, cookie consent modal (role="dialog", aria-label), and form status messages (aria-live).
  • Cookie consent modal is keyboard accessible with focus management so focus is trapped inside while open and returned to the triggering element on close. Pressing Escape closes the modal without changing your choice.
  • Autocomplete hints on form fields (autocomplete="given-name", email, tel, etc.) to support users who rely on browser autofill.
3.6 Crisis information
  • Crisis resources (988, 911, Nevada Mobile Crisis Response Team) are visible and clearly labeled across relevant pages, so users in distress can find help without navigating a complex UI.

4. WCAG 2.2 Additions We Have Applied

Where feasible, we have adopted selected new success criteria from WCAG 2.2:

  • 2.4.11 Focus Not Obscured (Minimum) — focused elements are not hidden behind sticky headers or cookie banners.
  • 2.5.8 Target Size (Minimum) — interactive targets are at least 24×24 CSS pixels.
  • 3.3.7 Redundant Entry — the site does not ask you to re-enter information you have already provided in the same form.

5. Known Limitations (Honest Disclosure)

Despite our efforts, some content may not yet be fully accessible. Known limitations include:

  • Embedded Google Maps on the Contact page — the iframe's accessibility depends on Google and is outside our direct control. We provide a plain-text street address and a "Get Directions" link alongside the map as an alternative.
  • PDF documents (including the HIPAA Notice of Privacy Practices) — we make a best effort to tag PDFs for accessibility, but some older documents may not have full semantic structure. If you need the content in a different format (large-print, plain text, or read aloud over the phone), contact us using the details in Section 8 and we will provide it.
  • Third-party blog content syndicated from Substack — accessibility of individual posts depends on how they were authored. We render them through a sanitizer to preserve semantic structure, but cannot retroactively add alt text to images that did not have any.
  • Blog feed loading state — while external content is loading, there is a brief period where only a loading message is announced; we are working to improve this.

If you discover an issue not listed here, please tell us — we rely on user feedback to keep this list honest and current.

6. Third-Party Content We Do Not Fully Control

This site depends on a small number of third-party services (listed in our Privacy Policy). While we do our best to choose vendors that support accessibility, we do not control the internals of:

  • The Google Maps embed on the Contact page.
  • Alma's scheduling interface on helloalma.com (linked from our Schedule button).
  • Substack's article pages (linked from our Blog).

If you encounter a barrier in any of these experiences, please contact us and we will help you get the information or book the session through a different channel.

7. Assessment Approach

The accessibility of this site has been self-assessed using a combination of:

  • Manual keyboard-only testing on the entire site (tab order, focus visibility, Escape key behavior, skip link).
  • Screen-reader spot checks using NVDA on Windows (Firefox and Chrome) and VoiceOver on macOS (Safari) on the main pages, contact form, blog, and cookie banner.
  • Automated evaluation tools including axe DevTools, Lighthouse accessibility audit, and WAVE, run against each public page.
  • Manual contrast checks of foreground/background text-color combinations.
  • Responsive and zoom testing at 200% zoom and common mobile breakpoints.
  • Review against WCAG 2.1 Level AA success criteria with notes kept for any items flagged in Section 5.

We have not yet completed a formal third-party audit. We may commission one in the future.

8. Feedback and Alternative Contact

We welcome your feedback on the accessibility of this website. If you encounter any barrier, need information in an alternative format, or would like to schedule a consultation through a channel other than the website, please reach out — we will help.

Email: Mindfulsolutionstherapy33@gmail.com
Phone (voice): (725) 290-3009
Mail: Mindful Solutions Therapy LLC, Attn: Accessibility, 2620 Regatta Drive, Suite 102, Las Vegas, NV 89128

When you contact us about an accessibility issue, it is helpful (but not required) to include: the page URL where you encountered the barrier, a brief description of the issue, the assistive technology or browser you were using, and the best way to reach you back.

9. Response Commitment

We aim to acknowledge accessibility feedback within 7 business days and to work to resolve reported issues within 30 days, or sooner when feasible. If a fix will take longer — for example, because it depends on a third-party vendor — we will tell you, keep you informed of progress, and offer an alternative way to get the information or service you need in the meantime.

10. Ongoing Improvement

Accessibility is an ongoing effort. We review this statement and the site at least annually and whenever we add significant new features. When we add new pages, components, or embedded content, we design them with accessibility in mind from the start rather than retrofitting afterward.

11. Updates to This Statement

We may update this Accessibility Statement from time to time to reflect new features, new testing, or changes to accessibility standards. When we do, we will revise the "Last reviewed" date and increment the version number at the top of this page.

See also our Privacy Policy and Terms of Use. For clinical privacy, see our HIPAA Notice of Privacy Practices.
📅 Schedule Free Consultation