Legal · Gibson Asphalt
Accessibility Statement
Last reviewed · September 2026
Template content. This page is scaffolding for a website template, not legal advice. Passages in [square brackets] mark decisions only the operating business can make. Have the finished text reviewed by a qualified advisor before publishing.
01
Our commitment
A driveway estimate should not be harder to request because of how someone browses the web. We aim to make this site usable for as many people as possible, including those who navigate by keyboard, use a screen reader or magnifier, prefer reduced motion, or need larger text.
02
Conformance status
This website aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. “Aims to meet” is deliberate: the site has been built and reviewed against those criteria, but it has not been audited or certified by an independent third party, and we do not claim full conformance.
[If you commission a formal audit, record the auditor, the date, and the outcome here, and update this wording to match what the audit actually found.]
03
What has been built in
Every interactive control can be reached and operated with a keyboard alone, in a logical order.
A visible focus indicator marks where you are on the page at all times.
A skip link lets keyboard and screen reader users jump straight past the navigation to the main content.
Form fields have real, programmatically associated labels rather than placeholder text standing in for them.
Form errors are announced, described in words, and linked to the field they concern.
Expandable sections such as the FAQ report their open or closed state to assistive technology.
Headings follow a meaningful order, and landmarks identify the header, navigation, main content, and footer.
Text and interface colours were chosen to meet AA contrast ratios against their backgrounds.
Layouts reflow to narrow screens and to 200% zoom without loss of content or horizontal scrolling.
The site honours the operating system's reduced-motion preference and stills its animations accordingly.
04
Images and media
Photographs of completed projects carry descriptive alternative text explaining what the image shows. Purely decorative graphics are marked so assistive technology skips them rather than announcing noise.
[Any video or audio you add later needs captions, and a transcript where the content is not otherwise available in text.]
05
Known limitations
We would rather name the gaps than imply there are none. At the current revision:
Some service and section images are still labelled placeholders rather than real photography, so their alternative text describes the placeholder rather than a project.
The estimate form is a front-end preview in this build and does not deliver enquiries, so the confirmation it shows does not reflect a real submission.
Third-party embeds added later — maps, video players, review widgets, chat — are outside our direct control and may not meet the same standard.
The site has been checked with keyboard navigation and automated tooling, but not yet in a formal test session with assistive technology users.
06
How this site is tested
Accessibility is checked as part of building each page rather than as a pass at the end: keyboard-only navigation through every interactive element, automated checks for contrast and structure, and review of headings, labels, and alternative text.
[Describe your own ongoing process here — how often you re-test, which tools you use, and who is responsible.]
07
Technical specifications
Accessibility relies on HTML, CSS, and JavaScript, and on ARIA where a native element could not do the job. The site is built to work with current versions of major browsers together with the assistive technology those browsers support.
08
Getting information another way
If any part of this site is a barrier, you do not have to work around it. Call or email and we will give you the same information another way — over the phone, by email, in large print, or in whatever format suits you — and we will take your project details directly rather than asking you to use the form.
09
Tell us what you found
Reports of accessibility problems are genuinely useful, and they are the fastest way for us to fix something. Tell us the page, what you were trying to do, and the browser or assistive technology you were using, and we will respond and explain what we can do.
[Name the person responsible for accessibility, give a direct contact route, and commit to a response time you can actually meet. If your jurisdiction requires a formal complaints or enforcement route, set it out here.]
Questions about this page can go to hello@gibsonasphalt.example or (555) 555-5555, or through the contact page. Both are placeholders in this demonstration build.