Quay’s site uses readable text, semantic headings, visible form labels, keyboard controls and always-open FAQ answers. A skip link moves toward the main content. The shared navigation and estimate action are available across the page templates, and tables can be read in a horizontal region where a narrow screen requires it.
Using the forms and tools
The native form separates property information from contact details, validates required fields and provides visible status messages. The planning tools include labels, explain their outputs and do not require contact details for basic results. Do not perform unsafe observations to answer a question; unknown is an acceptable planning input.
Limitations and help
This review contains planned photo slots and unconfigured contact fields. It is not represented as a certified accessibility audit or a guarantee that every assistive technology combination has been tested. Full production review follows assembly of the remaining assets and integrations.
Use the confirmed operator details on the contact page to report a barrier once available. Describe the page, control, device and assistive technology if relevant, without sending passwords or sensitive information. The HTML sitemap provides another route to the site’s content.