Help completing your task
Mounds View Draft Help should be understandable when you want to read about a service, check a location, or ask for an estimate. If something on the site makes that difficult, explain the task you were trying to complete and where you became stuck.
This page provides a way to ask for help and describe a barrier. It does not claim formal accessibility certification, full compatibility with every device, or compliance with a particular legal standard. A useful report can identify a problem that a general visual review may miss.
Report the page and the problem
Use the contact page and begin your notes with “Accessibility.” Include the page title or URL, what you tried to do, and what happened instead. A short description in your own words is enough to begin.
For example, explain whether a menu would not open, text covered a button, or a form field was hard to identify. Tell us the part that blocked you instead of feeling that you need to diagnose the code. You may also describe what would make the information easier for you to use.
When the form itself is the barrier
If you cannot complete the contact or estimate form, use a Call Now button to explain the problem and ask about another way to continue the conversation. The button is labeled with words rather than displaying the phone number on the page.
A call depends on the calling features available on your device. If that option does not work for you either, a trusted person may help you make a request, with your permission. Share only the information needed to describe the task and your preferred way to receive a response.
Reading and navigating the content
The pages use headings to divide topics and links to related service information. You should not need to read every paragraph to find the estimate route. If heading labels, link wording, or navigation order makes the page confusing, identify the section in your report.
People use different ways to move through a website. A problem may appear while using a keyboard, touch controls, voice input, or a screen reader. Describe what you were using if it helps explain the issue. You do not need to switch to a method that is uncomfortable or unavailable to you.
Text size, contrast, and narrow screens
You may use the text size, zoom, or display settings that suit you. If larger text causes overlapping content or hides an action, mention the affected page and the setting if you know it. A description such as “the estimate button disappeared when I enlarged the text” is useful.
If colors make words or controls hard to distinguish, identify the element involved. On a smaller screen, tell us whether the page requires awkward sideways movement or cuts off part of a form. Do not feel required to provide a screenshot to make a valid report.
Understanding the request form
The current form labels the name, phone, email, service address, contact preference, notes, and optional upload fields. Required fields are marked. The contact choices are text, call, or email, and the notes explain the property concern.
If a label is unclear, an error is difficult to locate, or a selection cannot be changed using your preferred input method, name that field in your report. Do not submit invented information just to get past a required field. Ask for help if the form's required information does not fit the question you need to ask.
Images and optional attachments
Website illustrations provide context, while service descriptions and actions appear as text. AI-generated imagery does not document actual staff or customer projects. If an image conveys something that is not explained in nearby text, describe which image caused confusion.
You do not have to upload a photograph with a property request. A written description can start the conversation. If you choose to share an image of a website problem, remove private information first. The privacy policy explains the limits of optional website file storage.
Technical details are helpful but optional
If you know your browser, device, or assistive technology, include it when it relates to the barrier. You might mention a phone browser, a keyboard, magnification, or a screen reader. Approximate information is useful; a report does not need exact version numbers to describe a problem.
You do not need to send medical information, proof of a disability, passwords, or account access. Do not turn off security protections simply to make a report. Explain the task in the environment you normally use, including any setting that seems connected to the issue.
What happens after a report
A report may lead to a question about the affected page or the steps that caused the problem. It can also help distinguish a website issue from a limitation on an external page. If more detail is requested, share only what you are comfortable providing.
This page does not promise a fixed repair time or that every request has the same technical solution. If you follow up, refer to the earlier report and describe any change. A corrected page can still have a different barrier, so explain the result of any new attempt clearly.
Standards and outside resources
The W3C overview of Web Content Accessibility Guidelines explains widely used accessibility guidance. Linking to that guidance does not mean this website has passed every criterion or received an independent audit.
W3C also offers advice on reporting inaccessible websites. Its suggestions can help you organize a message. External resources have their own layouts and contact routes. Report a barrier on this site through the available contact options, and identify any outside page separately.
Frequently asked questions
Does this page claim the website is fully compliant?
No. It does not claim formal certification, a completed independent audit, or full compliance with a particular standard. It explains how to request help and report a specific barrier encountered on the website.
How do I report an accessibility barrier?
Use the contact page and begin with “Accessibility.” Name the affected page, describe the task, and explain what prevented it. Your own words are enough; you do not need to diagnose the technical cause.
What if I cannot use the contact form?
Use a Call Now button if calling works for you, and explain the barrier. Ask about another way to continue. A trusted person can help with your permission if the available contact options are difficult.
Do I need to provide a disability diagnosis?
No. Describe the website task and the barrier. You do not need to submit medical records, proof of a disability, or other sensitive information to explain that a page or control is difficult to use.
Should I include my browser and device?
Include them if you know them and they help explain the problem. Exact version numbers are optional. A simple description such as phone browser, keyboard navigation, or screen reader can still be useful.
Can I use larger text or browser zoom?
Use the settings that suit you. If text overlaps, content disappears, or a control becomes hard to reach when you enlarge the page, report the affected area and the setting if you know it.
Is a photo required to request an estimate?
No. The upload field is optional. You can describe the property concern in the notes. If the upload control creates a barrier, leave it blank and explain the issue through an available contact option.
How do I report an unclear form label?
Name the field and describe what you expected to enter or select. If an error message was unclear, mention its wording. Do not enter invented details just to move past a required field.
Is there a guaranteed accessibility repair date?
This page does not promise a fixed repair time. A report may need clarification before its cause is understood. When following up, refer to the earlier message and explain whether the problem has changed.
Why does the page link to W3C guidance?
W3C provides public information about accessibility standards and describing barriers. The links help explain those topics. They do not certify this website or replace a review of how its actual pages work.