Oakville Custom Closets aims to make its website usable by people with a wide range of abilities, devices and assistive technologies. Accessibility is treated as an ongoing design, content and maintenance responsibility.
Navigation and page structure
Pages use a consistent header, navigation and footer. A skip link allows keyboard users to move directly to the main content. Headings are intended to follow a meaningful hierarchy so visitors can scan visually or navigate with assistive technology. Menus are designed to work with keyboard focus, and mobile navigation uses a button with an announced expanded state.
Keyboard use
Interactive elements should be reachable without a mouse. Links, menu controls, FAQ buttons, gallery filters, image controls and forms use standard interactive elements. Visible browser focus should remain available. The gallery lightbox can be closed with its close button or the Escape key.
If a visitor encounters a keyboard trap, an unreachable control or an unexpected focus order, the page address, browser and description of the problem will help with investigation.
Text, contrast and responsive layouts
The theme uses scalable text, generous line spacing and colour combinations selected for readability. Content reflows for desktop, tablet and mobile widths without requiring a separate mobile site. Visitors can use browser zoom, operating-system magnification and preferred text settings. Text is not embedded in primary photographs.
Some user-selected colours, browser extensions or high-contrast modes may alter presentation. Core information should remain available as text even when decorative styles are disabled.
Forms
WPForms is used for consultation forms. Form fields should have visible labels, instructions and validation messages. Required fields should not rely on colour alone. The exact accessibility of a form also depends on the form created in WPForms, any anti-spam tool and later configuration changes, so administrators should review each live form after editing it.
If a form cannot be completed, use the public phone or email configured for the website. When reporting a form problem, identify the field and the assistive technology or input method being used if comfortable doing so.
Images and media
Meaningful photographs include alternative text that describes the room or storage feature. Decorative imagery can use empty alternative text where appropriate so it does not create noise for screen-reader users. Image captions describe visible features without making unsupported project claims.
Motion and interaction
The theme avoids heavy animation. Visitors who enable reduced motion at the operating-system level receive shortened transitions. Information is not intended to depend on hover alone, and expandable FAQ controls expose their state programmatically.
Compatibility and limitations
The site is designed around current WordPress output, modern browsers and common assistive technologies. Third-party features, browser behaviour, WPForms changes, embedded content or administrator-added plugins can introduce limitations outside the original theme. No unsupported accessibility certification or perfect conformance claim is made.
Ongoing improvement
Accessibility should be checked when navigation, forms, colours, templates or major content change. Automated checks can identify some missing labels, contrast issues and code errors, but manual keyboard and screen-reader review remain important. Feedback from visitors is a valuable part of that process.
Content editors should preserve descriptive link text, meaningful headings, useful image alternatives and plain-language instructions when adding pages. New colour combinations should be reviewed for contrast. New forms should be tested at narrow widths, at browser zoom and with keyboard-only input. Error messages should identify the affected field and explain how to correct it.
Alternative access to information
If a page, PDF, image, form or interactive feature cannot be used, request the same information in another practical format. Depending on the request, that may include a plain-text explanation, an email response, a telephone conversation or help completing the project request. The goal is to provide access to the underlying information and service, not simply point back to the barrier.
When requesting an alternative, identify the content or task and the format that would be useful. Personal disability or medical details are not required unless the visitor chooses to provide context that is necessary for the accommodation.
Report an accessibility issue
Use the contact page, public email or phone number to report a barrier. Include the page address, what you were trying to do, what happened, the browser or device and the format or accommodation that would help. Do not include sensitive information that is unrelated to the accessibility request.
Requests will be reviewed and reasonable efforts made to provide the information or interaction in another way while the underlying issue is assessed.