Accessibility Statement

Jpetrous Creative Services LLC (“JpCS”)

Last Updated: October 28, 2026

This statement covers jpetrous.com, the website you are reading now. It does not cover websites JpCS has built for clients, which are addressed separately in Section 5.

‍

1. Our Commitment

A website that cannot be used is not a finished website. We want this site to work for people using screen readers, keyboard navigation, screen magnification, voice control, captions, or any other assistive technology, and for people who simply need larger text or more contrast to read comfortably.

We treat accessibility as part of the build rather than a cleanup pass at the end. We also treat it as ongoing work, because content changes and standards move.

2. The Standard We Work Toward

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We describe this as a target, not a certification. This site has not been audited or certified by an independent accessibility consultant, and we do not claim full conformance. Where we fall short, we would rather say so plainly than publish a compliance badge that does not mean anything.

3. What We Have Done

Work completed on this site includes:

• A single, descriptive page heading on each page, with section headings nested in order rather than chosen for how they look.
• Alternative text on images that carry meaning, and no alternative text on images that are purely decorative, so screen readers skip them instead of reading out a file name.
• Keyboard access to navigation, links, buttons, and accordion controls, with a visible focus indicator.
• Accordion and disclosure controls that announce whether they are open or closed, rather than appearing to a screen reader as unlabeled text.
• Form fields with visible, associated labels rather than placeholder text alone.
• Text and background color combinations checked for contrast against the brand palette.
• Page titles and descriptions that identify each page distinctly in a browser tab, a bookmark list, and a screen reader’s page list.

4. Known Limitations

We would rather list these than pretend they do not exist:

• Third-party embeds. Maps, social feeds, scheduling widgets, and similar embedded content are rendered by the third party and are not fully within our control.
• Older content. Some blog imagery and archived posts predate our current standards. We are working through them rather than all at once.
• Documents. PDFs and downloadable files produced before this statement may not be tagged for screen readers. We will supply an accessible version of any document on request.
• Audio and video. Not every voice over sample or video on this site carries a transcript or captions yet. We will provide a transcript on request while we work through the backlog.
• Motion. Some sections use movement or transitions. We respect the reduced-motion setting in your operating system where we are able to, but coverage is not complete.

5. Accessibility on Client Projects

Websites we build for clients are built with the same practices described in Section 3 as a matter of course. They are not, however, delivered as WCAG-conformant unless conformance is written into the scope of work.

If accessibility conformance matters for your organization — because you are a public body, you receive public funding, you serve a population that depends on it, or you have been advised that you carry a legal obligation — tell us at the quoting stage. Conformance work is a defined scope with its own testing, documentation, and cost, and it is not something we can retroactively certify.

Content you add to your own site after handoff, including images, documents, and embedded media, is yours to keep accessible. We are glad to quote remediation work on an existing site, and we are glad to show your team how to keep new content accessible as they add it.

6. Third-Party Platforms

This site is built on Webflow and uses third-party services for hosting, analytics, forms, and embedded content. Their accessibility is determined by those providers, not by us. Changes a platform makes to its own interface or output can affect accessibility on this site without notice, and we address those as we find them.

7. Reporting a Problem

If something on this site does not work for you, please tell us. You do not need to know why it is broken or what the fix would be — a description of what you were trying to do is enough.

It helps if you can include the page address, what you were trying to do, what happened instead, and the browser, device, or assistive technology you were using. None of that is required.

We aim to respond within five business days. Where a fix will take longer than that, we will tell you what we are doing and give you the information you were looking for in another format in the meantime — by phone, by email, or however suits you.

8. Alternative Formats

Any information on this site is available another way. If a page, document, or media file is not usable for you, contact us and we will provide the content as plain text, as a transcript, over the phone, or in whatever format works.

9. If Our Response Is Not Enough

If you raise an accessibility problem and are not satisfied with how we handle it, say so directly and it will be looked at again by the owner of the business rather than passed back through the same channel. JpCS is a small firm; there is no queue to get lost in.

10. Changes to This Statement

We update this statement as the site changes and as we work through the limitations listed in Section 4. The “Last Updated” date above reflects the current version.

11. Contact

JpCS operates remotely and does not maintain a public office address. Accessibility questions, problem reports, and requests for alternative formats can be directed to:

‍

Jpetrous Creative Services LLC

Michigan, United States

Phone: (586) 563-6634

Email: contact@jpetrous.com