Clear paths, keyboard access, and honest limits.

The site has a structured path through its content

Public pages include a skip link to main content, page landmarks, headings, navigation labels, visible keyboard focus, form labels, and status or alert regions. Buttons and links use native controls. Meaningful work images have descriptive text alternatives, while decorative images use empty alternatives or are hidden from assistive technology.

Responsive styles adapt the layout for smaller screens. Reduced-motion styles and scripts check the browser's prefers-reduced-motion setting, limit nonessential effects, restore visible content, and use ordinary scrolling where motion reduction applies. These are implementation features, not evidence that every color, zoom level, viewport, browser, or reading order has passed a formal audit.

Keyboard

Skip navigation, visible focus, native controls, Escape handling, and focus restoration in interactive drawers.

Motion

Reduced-motion behavior for nonessential animation and scripted scrolling.

Structure

Headings, landmarks, labels, status regions, and descriptive control names.

Responsive layout

Layouts adapt between desktop and mobile views without relying on hover alone.

Interactive tools expose status and keyboard controls

Design Bot and Website Draft Bot provide labeled controls, close actions, live status messages, error messages, and keyboard navigation. Design Bot traps focus when presented as a mobile modal and ignores controls inside hidden panels when finding focusable elements. It supports Escape to close and restores focus to the opening control.

Website Draft Bot uses labeled tab and tabpanel relationships for Questions and Draft views. It announces progress and errors, supports keyboard tab switching, and provides a visible Clear Saved Draft control. Generated previews appear in a titled sandboxed frame. Server sanitization removes forms, scripts, frames, working navigation, and other unsafe technical behavior before display.

Current checks do not establish complete conformance

This statement does not claim that the site conforms to a named WCAG version or level. It does not claim certification. No complete public record identifies an audit date, sampled pages, tester, browser set, screen-reader set, magnification setup, speech-input setup, high-contrast setup, or results for every interactive state.

Automated tests, source review, keyboard checks, and visual review can find many problems, but they do not cover every assistive-technology path. Emails, provider error screens, generated concepts, linked websites, and future integrations can behave differently from the reviewed pages. The absence of a formal claim is intentional and should not be read as proof of either full accessibility or full inaccessibility.

AI-generated drafts need human accessibility review

Website Draft Bot output varies with visitor answers and model output. Sanitization can block unsafe code, but it cannot prove that a generated color palette has readable contrast or that headings, alternative text, link wording, reading order, line length, and labels make sense. Generated business copy can also be inaccurate or confusing.

Treat every generated page as a rough visual and content direction. Before production use, a person should check the facts and complete keyboard, focus, zoom, contrast, reduced-motion, screen-reader, form, error, responsive, and content review appropriate to the final site. PixelForged does not describe the rough preview as accessibility tested or ready to publish.

Linked sites and service providers have separate behavior

Portfolio links open independent websites. Their current owners and deployments control those destinations. Google Fonts, hosting, AI responses, and email delivery also depend on outside services. PixelForged controls its own page structure and integration code but cannot make a complete accessibility claim for another website or provider interface.

The quote page includes a direct email link as an alternative when the form does not send. Bot use is optional, and visitors can use the standard site navigation without opening a bot. No postal address, phone-based accessibility service, alternate-format service, or provider-specific accommodation is promised because those options have not been confirmed.

Tell PixelForged what stopped you

Email admin@pixelforged.com with the page address, the task you were trying to complete, and what happened. Include a screenshot, browser, device, or assistive-technology name only if you want to and it helps show the problem. Do not send medical records or other sensitive personal information.

This contact route does not include a guaranteed acknowledgement time, repair schedule, escalation route, or regulator process. It gives visitors a direct way to report a barrier while those operational details remain unconfirmed. Accessibility can change when pages, bot states, forms, images, animation, provider behavior, or generated-output rules change, so each material release needs fresh review.