Accessibility Statement for Accessible Webflow websites

We believe in meeting and exceeding WCAG conformance requirements to create an inclusive website that everyone can access equally.

Our conformance target

Graceful Web Studio aims for WCAG 2.2 Level AA conformance on gracefulwebstudio.com. That is the standard we design, build, and test against on every page. It is a target we work toward rather than a guarantee. Websites change constantly, some content comes from third parties we do not control, and no single test catches everything. When we fall short of the target, we fix it.

WCAG stands for the Web Content Accessibility Guidelines, published by the World Wide Web Consortium. Level AA is the conformance level most widely referenced for public websites.

Our commitment to accessibility

We are committed to making our own website accessible, conformant, and usable. Accessibility shapes our work from the first wireframe through launch and every update after it. We follow WCAG 2.2 Level AA and keep testing and improving so people can find, read, and use everything here.

An inclusive website benefits everyone. Clear structure, readable text, visible focus, and predictable behavior make the experience better for every person who visits, on every device, in every situation.

We hold every website we build for clients to the same standard. Many business owners have never been told whether their website is accessible or why it matters. If we find something on a site we touch that excludes people, we fix it. Websites that shut people out bother us, and we work hard to make sure what we ship works for everyone.

Measures we take to support accessibility

Accessibility is included in the scope of every project we take on.
We build with semantic HTML, one logical heading order, and clear page landmarks.
We follow the W3C ARIA Authoring Practices for interactive components.
We check color contrast against WCAG 2.2 Level AA thresholds.
We test keyboard operation and visible focus on every interactive element.
We write meaningful alternative text for images and clear link text.
We honor reduced motion preferences and provide a way to pause movement.
We re-check accessibility after every content update and site change.

Conformance status

This website is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the content meets the standard and some parts may not yet meet every success criterion. We review the site regularly and correct what we find.

How we test this website

We use automated tools and manual testing together. Automated tools catch a portion of issues quickly. Manual testing catches the rest, including the things software cannot judge, such as whether alternative text is actually useful or whether a focus order makes sense to a person.

Automated testing tools

ARC Toolkit
WAVE Web Accessibility Evaluation Tool
Lighthouse accessibility audits
Browser developer tools for code review and accessibility tree inspection

Manual testing

Keyboard only operation of every interactive element, checking focus order and visible focus
Zoom to 400 percent at 1280 pixels wide and reflow at 320 CSS pixels wide
Form label, instruction, and error message review
Heading order and landmark review
Color contrast measured by hand where automated results are uncertain using
- TPGI Colour Contrast Analyzer
Content review for plain language and clear link purpose

Screen readers

NVDA on Windows
VoiceOver on macOS and iOS

Compatibility with browsers and assistive technology

This website is built to work with current versions of Chrome, Firefox, Safari, and Edge, on desktop and mobile. It is tested with NVDA on Windows and VoiceOver on macOS. Older browsers and older versions of assistive technology may not support everything on the site.

Technical specifications

Accessibility on this website relies on the following technologies working with your browser and any assistive technology you use.

HTML
CSS
JavaScript
WAI-ARIA
SVG

This website is built and hosted on Webflow.

Known limitations

Some content on this website still falls short of our target. Below is what we know about right now, what causes it, and what to do if it gets in your way. We update this list as we fix issues and as we find new ones.

Motion and auto-playing content

Some sections of this website include animation that starts on its own. A pause control is provided for that content, and the site honors the prefers-reduced-motion setting in your operating system, so movement is reduced or stopped when you have that setting turned on. If you find motion here that you cannot pause, tell us and we will fix it.

Cal.com booking embed

Our scheduling tool is an embedded booking page from Cal.com. The markup inside the embed is built and served by Cal.com and we cannot change it. Known issues inside the embed:

The embed contains its own main element, so any page carrying the booking tool has two main landmarks. Screen reader users navigating by landmark will find more than one region announced as main.
The embed contains its own heading level 1, so the page has a duplicate H1 and the heading outline is not clean.
Decorative SVG graphics inside the embed are not hidden from assistive technology, so screen reader users may hear them announced even though they carry no information.
The focus outline on links inside the embed does not meet the 3 to 1 contrast requirement against the color behind it. Keyboard users can still see where focus is, but the indicator is harder to see than it should be.

If the booking embed does not work for you, call or email us using the contact details below and we will schedule with you directly.

Google Maps embed

We embed a Google Map to show the Graceful Web Studio location. The map is built and served by Google and we cannot change what is inside it. Known issues:

The embed code Google generates has no title attribute on the iframe, so screen readers announce a generic frame with no stated purpose.
The map graphic conveys location visually only. It is not usable by people who cannot see it.
Focus order inside the map jumps around rather than following a predictable path.
The map and satellite toggle is not in the focus order at all, so keyboard users cannot reach it, and it has no accessible name.
The map cannot be panned with the keyboard. Zoom in and zoom out are the only map controls a keyboard can operate.
Color contrast on place labels and points of interest is low and hard to read for people with low vision.
The Google logo in the corner of the map has no alternative text, so some screen readers announce the image file name instead.

Our full address and phone number are written out in text on the page, so the map is never the only way to get that information.

YouTube video player

Video on this site is embedded with the YouTube player. We provide captions and a full text transcript for our video content. The player controls themselves are built by YouTube and have known issues:

The channel profile image is a link whose accessible name reads as "Photo image of," which does not tell you where the link goes.
The full screen button has no accessible name, so screen readers may announce it only as a button.
The video title text and the elapsed time text fall below the 4.5 to 1 contrast requirement.
The player responds to single key shortcuts, such as pressing k to play and pause. These can collide with the single key commands screen readers use.
The subscriber count is marked up as a heading when it is not one, which adds noise to the heading outline.
NVDA does not reliably announce the Subscribe button until you tab directly to it.
The subscription notification bell does not announce whether it is pressed or not pressed.
When the player is configured without visible controls, it can be hard to tell how to pause the video using a keyboard alone.

The transcript for each video is published on the same page as the video, so you can read the full content without using the player at all.

Yakima Valley Business Times feature (PDF)

We host a PDF of a print feature about Graceful Web Studio published by the Yakima Valley Business Times in May 2026. The Yakima Valley Business Times produced this document, not us, and we cannot confirm that it meets PDF/UA (ISO 14289) requirements for tagged, screen-reader-accessible PDFs. A browser's built-in PDF reader may not expose its structure, reading order, or images to assistive technology.

If you need this feature in an accessible or alternative format, contact the Yakima Valley Business Times directly, or reach out to us using the contact details below and we will help coordinate a request on your behalf.

If any third-party content on this website blocks you, contact us and we will give you the same information or service another way.

Feedback: if you see something, say something

Your input is critical to making this website the best it can be and accessible to everyone equally. If you hit a barrier here, or if something is confusing, hard to read, or does not work with your assistive technology, we want to hear about it. Tell us what page you were on, what you were trying to do, and what happened.

Reach Crystal Scott directly:

Phone: 509-823-6780
Email: crystal@gracefulwebstudio.com

We aim to respond within two business days.

Assessment approach

Graceful Web Studio evaluated this website by self-evaluation. Testing is carried out by Crystal Scott, a Certified Professional in Web Accessibility (CPWA) and Section 508 Trusted Tester, using the automated and manual methods described above.