Serving Mississauga, Ontario · Residential & Commercial

Website Information

Accessibility Statement

Important information about using this website.

Last reviewed: September 18, 2026

Mississauga Landscaping Pros aims to provide a website that can be used by as many people as reasonably possible, including visitors who use assistive technology, keyboard navigation, screen magnification or alternate input methods.

1. Accessibility goal

The website is designed and maintained with the Accessibility for Ontarians with Disabilities Act and the Web Content Accessibility Guidelines in mind. The continuing development target is WCAG 2.2 Level AA. This target is not a claim that every page, file or third-party component has received formal certification.

Accessibility work is guided by the principles that information and controls should be perceivable, operable, understandable and robust across common devices, browsers and assistive technologies.

2. Measures included in the website

The custom theme and content system support:

  • Semantic headings, landmarks and consistent page structure
  • A skip link that moves keyboard users directly to the main content
  • Keyboard-accessible navigation, links, buttons and disclosure controls
  • Visible focus indicators and controls sized for practical interaction
  • Responsive layouts that reflow on phones, tablets, zoomed views and narrow screens
  • Alternative text for meaningful images and empty alt attributes for decorative branding
  • Colour combinations selected for readable contrast
  • Plain-language labels and consistent navigation patterns
  • Reduced animation when a visitor enables the reduced-motion preference
  • Information that is not intentionally communicated by colour alone

3. Navigation and content

Navigation is structured so major pages can be reached by keyboard as well as pointer input. Headings, lists, tables and link labels are intended to communicate their purpose without relying on visual position alone. Text can be enlarged through browser zoom, and layouts are designed to reorganize instead of forcing desktop-width reading on a small screen.

Meaningful photographs receive descriptive alternative text. Decorative logo treatment is hidden from screen readers where the adjacent business name already provides the same information.

4. Forms and estimate requests

Website forms should provide visible labels, understandable required-field indicators, keyboard access, useful validation and a confirmation after submission. Form behaviour is supplied partly by WPForms and can change when that plugin or its configuration changes.

If a form creates a barrier, use the global email or phone option when available, or ask a support person to submit the request with your permission. Do not include sensitive information that is unnecessary to describe an accessibility problem.

5. Third-party services and known limitations

Some functionality can be provided by third parties, including forms, maps, analytics controls, embedded media, social content or linked municipal and supplier websites. The website cannot control every aspect of those services, but accessible options should be selected and configured where practical.

New plugins, older uploaded documents or external pages may not meet the same standard as the custom theme. A reported barrier will be reviewed so that a correction or useful alternative can be considered.

6. Alternative formats and communication support

You may request website information in a reasonable alternative format or ask for communication support. Available options depend on the material and request and can include plain text, a more accessible document, telephone discussion when a public number is available, or assistance completing a form.

The requester will be consulted about a useful option. If a particular format cannot reasonably be supplied, the limitation will be explained and another practical approach will be considered.

7. Reporting an accessibility barrier

Use the website contact form or global email and include:

  • The page address or page name
  • The information or task you were trying to access
  • A description of the barrier
  • The browser, device or assistive technology involved, if you are comfortable sharing it
  • Your preferred way to receive a response

Begin the message with “Accessibility feedback” so it can be identified. Personal information included with the report will be handled under the Privacy Policy and used to investigate the barrier and respond.

8. Continuing review

Accessibility is reviewed as templates, navigation, content, forms, images and plugins change. Review can include keyboard testing, zoom and responsive checks, colour-contrast checks, automated scanning and manual testing of important journeys.

Automated tools cannot identify every barrier. Feedback from people using different devices and assistive technologies is important and helps prioritize corrections according to their effect on access.

9. Statement updates

This statement will be reviewed after material theme, content, form, plugin or testing changes and when a reported barrier affects the information described here. The latest review date will remain visible at the top of the page.

Accessibility questions

What accessibility standard does the website target?

The continuing development target is WCAG 2.2 Level AA. It is not a claim of formal certification for every page or third-party tool.

How can I report a barrier?

Send the page, task, barrier, device or assistive technology if comfortable, and preferred response method through the contact route.

Can I request an alternative format?

Yes. The request will be reviewed and a useful option discussed. If a specific format cannot reasonably be supplied, another approach will be considered.

Are third-party forms covered by the custom theme?

The theme supports accessible placement, but the form plugin controls part of the markup and behaviour. Report a problem so its configuration or an alternative can be reviewed.

Does the accessibility target mean every page is certified?

No. WCAG 2.2 Level AA is a continuing target, not a certification claim covering every page, document or external service.

Request Estimate