1. Our Commitment
Apeiron is committed to making the Services — apeironweb.com, python-visuals.com, and every website Apeiron builds and hosts on the Apeiron Network — usable by as many people as possible, including people with disabilities. We believe an accessible web is a better web, and we treat accessibility as part of the craft of building a site, not an afterthought.
2. Target Standard
We aim to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA published by the World Wide Web Consortium. WCAG 2.1 AA is the accessibility standard most commonly referenced in US commercial-site accessibility matters and is the standard we use when building and reviewing sites.
We recognize that WCAG 2.1 AA is an ongoing target rather than a one-time certification. Websites evolve, content changes, and new content must be built and reviewed to the same standard. Our goal is continuous conformance, not a snapshot.
3. What We've Done
Across the Apeiron Network, we have taken the following steps toward WCAG 2.1 AA conformance:
- Semantic HTML. We build sites with structured, semantic HTML (
header,nav,main,footer,article,section,h1–h6) so that screen readers can navigate the page structure reliably. - Keyboard navigation. Core site features are reachable and operable using the keyboard alone, without a mouse.
- Image alt text. Meaningful images carry descriptive alternative text where content is supplied by clients or authored by Apeiron.
- Color contrast. We use color palettes that target WCAG AA contrast ratios for body text and interactive elements on our Gold Standard design system.
- Form labels and error messages. Forms are built with linked labels and accessible error messaging.
- Focus indicators. Interactive elements show visible focus indicators for keyboard users.
- No sensory-only cues. We avoid conveying information by color, sound, or shape alone.
4. What We're Still Working On
We're honest about where we are. Known areas that do not yet fully meet WCAG 2.1 AA across every site on the Apeiron Network include:
- Client-supplied content. Where clients upload their own images, text, or product photos, alternative text and heading structure depend on what the client provides. We work with clients to add accessibility guidance to the content they supply and to improve content-side accessibility over time.
- Third-party embeds. Some client sites embed third-party tools (payment checkout, video players, mapping widgets). These inherit the accessibility posture of the embedded service. Where a third-party embed is inaccessible, we work with the client to substitute an accessible alternative where feasible.
- Legacy pages. Sites built under an earlier version of the Apeiron Network may not yet meet the current standard on every page. We prioritize remediation based on impact and frequency of use.
- Formal audit. Apeiron has not yet commissioned a formal third-party accessibility audit. We intend to do so when the business scale warrants it and when it is financially feasible.
We do not hide these gaps. Naming them is the commitment.
5. Reporting an Accessibility Issue
If you encounter an accessibility barrier on any Apeiron Service or on any site in the Apeiron Network, please tell us. We treat every report seriously and will respond.
How to report: Email [email protected] with the subject line "Accessibility Issue."
What to include: The URL of the page where the issue occurred, a description of the issue, the assistive technology you were using (if applicable), and any additional context that would help us understand the problem.
What to expect: We will acknowledge your report within a commercially reasonable time and will investigate the issue in good faith. Where the issue is within our control and can be fixed, we will prioritize a remediation and communicate the outcome back to you. Where the issue involves client-supplied content or a third-party embed, we will coordinate with the responsible party and keep you informed.
6. Alternative Access
If you are unable to access specific information or a specific feature on a site in the Apeiron Network because of an accessibility barrier, please contact us at [email protected]. We will work with you to provide the information or functionality through an alternative channel — by email, phone, or another accessible format — while the underlying issue is being remediated.
7. Changes to This Statement
Apeiron may update this Accessibility Statement from time to time as our practices evolve, as WCAG guidance is updated, or as new sites are added to the Apeiron Network. Material changes will be posted here with a new "Last Updated" date.
8. Contact
Apeiron (d/b/a of Python-Visuals Web Design)
Email: [email protected]
Web: apeironweb.com