Accessibility
Our approach
We aim to make information about basement water problems understandable and usable by as many visitors as possible. Pages are organized with headings, navigation landmarks and descriptive links so a visitor can move from a symptom to a service or guide. The design uses readable text, clear contrast and layouts that adapt to smaller screens. Accessibility work is ongoing and feedback can identify barriers that were missed.
Keyboard and navigation
The main navigation can be operated with a keyboard, and a skip link moves to the main content. Interactive controls should show visible focus. On smaller screens the menu opens from a clearly labelled control. Gallery images can be opened and closed with ordinary controls, including the Escape key supported by the browser dialog. If a component is difficult to use with a keyboard, please tell us which page and control caused the problem.
Text and visual content
Text is presented as live HTML rather than text inside photographs. Images that contribute information have descriptive alternative text; decorative elements should not interrupt reading order. Tables are used for comparisons where row and column relationships matter. You can use browser zoom and device text settings. Some layout changes at narrow widths to keep cards, forms and navigation within the viewport.
Forms
Enquiry forms are provided through WPForms and their exact fields depend on the live form configuration. Labels, required indicators, error messages and file-upload controls should be reviewed when the form is configured or changed. If a form cannot be completed with your device or assistive technology, use the published phone or email to provide the same basic project information. Do not send sensitive documents unless needed.
Alternative contact
The site provides a telephone link and, once configured, an email contact option. You can describe where water appears and when it happens without using the online form. If you need information in another format or need help accessing a guide, identify the page or topic and the format that would be useful when you contact us. We will review feasible ways to provide the information.
Reporting a barrier
Please include the page address, device or browser if known, the control or content involved, and what you were trying to do. You do not need to disclose a disability to report a problem. Feedback helps prioritize fixes to navigation, contrast, reading order and form behavior. A report does not require you to continue using a feature that is inaccessible to you.
Ongoing review
The site may change as services, guides and forms are updated. New content and plugin changes can introduce accessibility issues, so review is part of maintenance. We do not claim a certification or guarantee that every third-party component works perfectly with every assistive technology. We aim to correct barriers that are brought to our attention and to maintain clear alternative contact routes.
Mobile action controls
On small screens a fixed action bar provides Call and Request Assessment routes. The page has extra bottom space so the controls do not cover its final content. If the bar conflicts with browser controls, zoom settings or assistive technology, the main Contact link remains available in navigation and the footer. Reporting the device and viewport setting helps us reproduce a problem.
Documents and external pages
Some guides link to official Town of Milton or Halton Region pages and documents. Those external resources may use different accessibility methods and can change without this site controlling them. If a linked document is difficult to access, tell us which information you need. We can point to the relevant official contact or summarize the part of our own page that relates to the question.
Readable interaction states
Buttons and links should have visible focus and hover states, and form sections should not depend on colour alone to communicate a required action. The mobile menu can be expanded with its labelled button; nested topics can then be opened. Reduced-motion preferences are respected by removing decorative transitions. If a specific state remains unclear, include its label and page in feedback.
Help identifying the problem
When reporting an access issue, the exact link text, form field or page heading can be more useful than a broad description such as “the page is broken.” A screenshot is optional; a written account is enough. We can review keyboard behavior, contrast, zoom, reading order or error feedback as relevant, and explain any alternative contact option while the issue is being addressed.