Our accessibility commitment
Mississauga Eavestroughs & Gutters aims to make its public website and enquiry process usable by people with a wide range of abilities, devices and assistive technologies.
Last reviewed: September 19, 2026. Accessibility is treated as part of content, design, development and ongoing maintenance rather than a one-time statement. The goal is to reduce barriers when visitors compare services, read guidance, navigate menus or submit a property enquiry.
No automated scan or statement can guarantee that every page, third-party tool or assistive-technology combination is barrier-free. This page describes the measures built into the custom theme, known dependencies and the process for reporting a problem. It is not a formal certification of conformance.
Standards used as guidance
The site uses the Web Content Accessibility Guidelines as its technical reference, with WCAG 2.2 Level AA used as the improvement target where practical. WCAG organizes accessibility under four principles: content should be perceivable, operable, understandable and robust. The W3C WCAG overview explains the standard and its success-criteria levels.
Ontario accessibility obligations vary by organization type, size, content and circumstances. The site owner should review the current Ontario guidance for accessible websites and obtain appropriate advice rather than treating this statement as a legal determination.
Accessibility measures built into the theme
| Area | Implemented approach | Why it helps |
|---|---|---|
| Structure | Semantic landmarks, one primary page heading and ordered section headings | Supports orientation and screen-reader navigation |
| Keyboard | Skip link, keyboard-operable links, buttons, menus and visible focus indicators | Allows use without a mouse or touch gesture |
| Visual design | Audited colour contrast, scalable text and layouts that reflow | Improves reading at different zoom levels and screen sizes |
| Images | Context-specific alternative text for meaningful images and empty alternatives for duplicate decoration | Communicates purpose without unnecessary repetition |
| Motion | Reduced-motion preferences disable non-essential transitions | Respects operating-system motion settings |
| Forms | Visible instructions and a dedicated form region around the configured WPForms output | Clarifies the task and contact alternatives |
Keyboard and navigation support
A keyboard user can move to the “Skip to content” link, continue through the logo, menu, page links, forms and footer, and see a visible focus outline. Desktop dropdowns open when focus enters them. On smaller touch layouts, the first activation of a parent service item opens its submenu and a later activation can follow the service-hub link.
Navigation labels are intended to describe the destination instead of relying on colour or position alone. Breadcrumbs identify location within the Residential, Commercial or Guides hierarchy. If keyboard focus becomes trapped, disappears behind the sticky header or opens a menu unexpectedly, please report the page and control involved.
Text, contrast, zoom and responsive reflow
The theme uses high-contrast text and backgrounds, visible link treatment, flexible type sizing and content widths designed for reading. Pages adapt from desktop grids to tablet and single-column mobile layouts. Tables are placed in horizontal scrolling containers on narrow screens so the page itself does not require two-dimensional scrolling.
Visitors should be able to use browser text enlargement and zoom without losing the main content or navigation task. Very long words, browser extensions, translated text and third-party form controls can still create edge cases. A screenshot and the browser zoom level are helpful when reporting a reflow issue.
Images, icons and non-text content
Meaningful property and component images have concise alternative text describing the information relevant to the page. Decorative graphics use an empty text alternative so they do not repeat nearby words. The logo link has an accessible brand label while the separate emblem is decorative beside the live site-name text.
Content should not require a visitor to identify a service from an image alone. Captions and surrounding text explain the component or planning point. Representative images are not presented as proof of a specific customer project.
Forms and enquiry alternatives
The public estimate form is supplied through WPForms and is configured separately from the theme. The site owner should ensure every field has a programmatic label, required fields are identified in text, instructions appear before complex inputs, error messages name the problem and confirmation does not rely on colour alone. Upload limits and accepted file types should be stated beside an upload field.
If the form cannot be completed, use the globally displayed email address or phone number. You may request help identifying the information needed, communicate through a support person or ask for a practical alternative format. Do not include sensitive information that is unrelated to the property request.
Third-party content and known dependencies
WPForms, spam protection, maps, analytics, video, document viewers or other services can introduce controls and content that the theme does not generate. Their accessibility can change when a plugin or provider updates. External websites reached through municipal or manufacturer links are controlled by their respective owners.
The most likely dependency is the configured enquiry form because its fields, validation and confirmation are managed in WordPress after theme installation. The form should be tested with keyboard-only navigation, common screen-reader patterns, browser zoom and a real failed submission before launch and after material form changes.
Requesting information in another format
If website content is not usable in its published format, identify the page or information needed and the format or communication method that would help. Depending on the material and request, a practical response may include plain-text information in an email, a verbal explanation, a simplified list of required enquiry details or assistance completing the service request.
The site does not promise that every format can be produced immediately, but the request will be considered in good faith and unnecessary barriers should not be imposed. If a specific document is supplied by a third party, an accessible alternative may require cooperation from that provider.
How to report an accessibility barrier
Use the phone number or email address displayed throughout the website. To make the report easier to reproduce and fix, include as much of the following information as you are comfortable providing:
- The page address and the link, menu, image, table or form field involved
- What you were trying to do and what happened instead
- Device, browser and assistive technology, if relevant
- Browser zoom or text-size setting, if the issue concerns layout
- The format or communication method that would help you complete the task
Feedback handling and ongoing review
Accessibility feedback should be acknowledged as soon as reasonably possible, reviewed without penalizing the person who reported it and shared only with those needed to investigate or respond. A useful resolution may involve correcting content, changing code, adjusting the form, providing the information another way or documenting a third-party limitation and workaround.
Ongoing review includes keyboard order, focus visibility, menus, headings, link purpose, colour contrast, alternative text, 200% zoom, narrow-screen reflow, reduced motion and form errors. New pages, plugins and media should be checked before launch. This statement will be revised when material features or accessibility practices change.