Accessibility Statement

This statement applies to content and user interfaces that we create and host at creatorzplus.biz and related subpages. It also explains where third-party content may affect accessibility and what actions we take to address those limitations. If you access Creatorz+ services through a client or partner portal, that service may have its own accessibility practices and policies.

Our goal is to provide clear, consistent content and predictable navigation so visitors can complete tasks whether they use a mouse, keyboard, screen reader, or other assistive technologies.

Creatorz+ commits to designing, developing, and maintaining digital experiences that strive to meet relevant accessibility standards. Where feasible we follow the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as a practical reference point, while recognizing that not every part of our site may yet fully conform.

This statement covers the public website, marketing pages, documentation, and web applications we host. It does not cover client-managed content, third-party embeds, or external systems we link to that are outside our control; such items are noted where present.

We maintain measurable goals to guide work and track progress. Current objectives include:

• Readable content: Ensure clear typography, adequate line-length, and resizable text so people can read without strain.
• Consistent navigation: Maintain a predictable, consistent navigation and page layout across the site.
• Keyboard accessibility: Ensure core features are reachable and operable by keyboard alone.
• Color and contrast: Use color combinations that meet contrast thresholds (AA) for text and controls.
• Accessible forms: Provide visible labels, instructions, and clear error messaging for forms.
• Assistive technology support: Ensure semantic HTML and ARIA is used appropriately for screen readers.

We use legible typefaces and a clear typographic scale. Headings use Montserrat and body copy uses Inter to establish a strong visual hierarchy. Recommended practices we follow:

- Base font-size: typically 16px (1rem) with comfortable line-height (1.5–1.8) for body text. Larger headings scale proportionally to provide clear structure.

- Resize support: text can be resized using browser controls without loss of content or functionality. We avoid fixed pixel-only layouts that prevent scaling.

Our site is designed responsively using Tailwind utility breakpoints to adapt layout and hit targets for small screens. On mobile we consider: readable font sizes, touch target sizing (minimum 44x44 CSS pixels where practical), adequate spacing between interactive elements, and avoidance of gestures that are hard for some users to perform.

Responsive images, flexible layouts, and simplified navigation on small screens help ensure content remains usable regardless of device or zoom level.

We use a consistent navigation system and semantic headings to help users understand structure and move through content quickly. Pages are organized with a single H1, followed by H2 and H3 headings to reflect sections and subsections. Landmark roles (header, main, nav, footer) are present to assist screen reader users.

Example heading outline for a typical page:

H1 — Page title
  H2 — Section
    H3 — Subsection
    H3 — Subsection
  H2 — Another section
                    

Buttons and links have descriptive labels that indicate the destination or action (for example, "Download invoice" rather than "Click here"). Focus outlines are visible and maintained for keyboard users. We use primary (#1E3A8A) and secondary (#F97316) brand colors with tested contrast ratios to ensure text and controls meet accessibility thresholds.

Below are example swatches and contrast notes:

Forms include visible labels, helper text where needed, and clear error messages tied to inputs. We prefer native HTML label elements with for/id attributes, and avoid relying only on color to indicate required fields or errors. When additional semantics are needed we use ARIA attributes (aria-describedby, aria-invalid) to support assistive technology.

Example accessible form markup pattern (simplified):

Email address

We'll use this to send receipts.
                    

We ensure that core features are reachable and operable with keyboard alone. Focus order follows visual order, and interactive elements are placed logically in the DOM. Where helpful, we include "skip to content" links to bypass repeated navigation. Semantic HTML and appropriate ARIA roles help screen readers interpret structure and state. If you rely on assistive technology and encounter a problem, let us know—your report helps us prioritize fixes.

Some features use third-party tools, embeds, or widgets (for example payment processors, analytics, or embedded maps). While we choose partners who prioritize accessibility, those tools may have limitations outside our control. When we rely on third parties, we document known issues and work with providers to improve accessibility or provide alternatives when possible.

We use a combination of automated checks (a11y linters, contrast checkers), manual audits, and periodic user testing with assistive technology to find and fix issues. Accessibility tasks are included in our product backlog and prioritized alongside functional work. Typical activities include regression checks before releases and targeted accessibility sprints for larger updates.

• Automated scans run regularly on main pages.
• Manual audits for new features and major redesigns.
• User testing and feedback incorporated when available.

If you find an accessibility issue or need an alternative format, please contact us. We aim to respond to accessibility inquiries within two business days and to provide a timeline for any remedial work.

Email: accessibility@creatorzplus.biz
Phone: +1 (555) 123-4567

You can also use our contact form to report issues: Report an Issue

Please include:

• A description of the problem.
• The web address (URL) where you saw the issue.
• Your preferred way to be contacted and any assistive technology used.

Accessibility is an ongoing effort at Creatorz+. We welcome feedback and take reports seriously. If you experience difficulty using our site, please get in touch using the contact details above so we can assist and improve.