GlamOps Accessibility Statement
Contents
Effective date: October 9, 2026 Last reviewed: October 9, 2026
GlamOps LLC ("GlamOps") wants everyone to be able to use GlamOps, including people with disabilities. This statement explains what we aim for, what we know still needs work, and how to get help.
It covers:
- the GlamOps website at glamops.net;
- Booking Sites, intake forms, payment pages, and the "My appointments" Client Portal that GlamOps hosts for Businesses (as those terms are defined in the GlamOps Terms of Service at https://glamops.net/legal/terms); and
- the GlamOps business dashboard and mobile apps.
1. Need help booking right now?
If you have trouble booking an appointment, filling out a form, or paying on a GlamOps Booking Site:
- Contact the business directly. Its phone number and email are at the bottom of its Booking Site and on your confirmation. The business can book for you another way.
- Or contact GlamOps: email admin@glamops.net or call (971) 274-1392. Tell us the website address, what you were trying to do, and the problem. We will help you complete your booking and aim to respond within 5 business days.
2. Our goal
We make commercially reasonable efforts for GlamOps to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. These are internationally recognized guidelines for making websites usable by people with disabilities, including people who use screen readers, keyboard navigation, voice control, or screen magnification, and people with low vision, color blindness, or cognitive disabilities.
3. What we do
- Accessible templates. We design and test the Booking Site, form, payment, and portal templates that GlamOps provides with accessibility in mind, including keyboard navigation, visible focus states, text labels on form fields, sufficient color contrast, error messages that explain what to fix, and support for screen readers and browser zoom.
- Payments. Card entry on GlamOps Booking Sites is provided by Stripe. We choose Stripe payment components that support assistive technology, and report issues we find to Stripe.
- Testing. We test new features with automated accessibility tools and manual checks, including keyboard-only and screen reader testing, before release.
- Reviews. We review GlamOps against WCAG at least once a year and after major design changes.
- No overlays. We do not rely on accessibility "overlay" widgets. We fix issues in the underlying design and code.
- Training. Everyone who builds GlamOps learns accessibility basics.
4. Content added by businesses
Each business controls some content on its own Booking Site, such as photos, colors, service descriptions, and intake forms. Businesses are responsible for making that content accessible. To help, GlamOps:
- requires alt text (a short description) when a business uploads a gallery photo;
- warns a business when its chosen colors do not have enough contrast;
- builds forms with accessible field types, so questions a business writes are labeled correctly; and
- gives businesses tips on writing clear, accessible content.
5. Known limitations
We are still reviewing third-party content, such as business-uploaded photos and documents, and embedded Stripe payment forms.
6. Compatibility
GlamOps is designed to work with recent versions of major browsers (Chrome, Safari, Firefox, and Edge) and with common assistive technologies, including VoiceOver on iOS and macOS, TalkBack on Android, and NVDA and JAWS on Windows.
7. Feedback and reporting issues
We welcome feedback about accessibility. To report a problem or suggest an improvement:
- Email: admin@glamops.net
- Phone: (971) 274-1392
Please tell us the page address, what you were trying to do, and the device, browser, and assistive technology you use, if you know. We aim to acknowledge reports within 5 business days and to fix or provide a workaround for barriers as quickly as we can. If you need information in a different format, we will try to provide it.
8. Updates
We review and update this statement at least once a year. The "Last reviewed" date at the top shows when we last did.

