Accessibility on This Website
What we have built in, what we know is imperfect, and how to tell us.
This site is built to be usable with a keyboard, a screen reader, browser zoom or a phone held one handed. We aim at the WCAG 2.1 AA guidelines and we test the parts we can test. It is not a certification and we are not claiming perfection. If something here stops you getting an answer or reaching us, the phone number works and we would rather hear about it.
How the pages are put together
Every page is ordinary HTML with headings in a real order, so a screen reader user can move by heading and land on the section they wanted instead of listening through the whole page. Links say where they go rather than saying click here. Images that carry information have text descriptions, and images that are purely decorative are marked so assistive software skips them rather than reading a filename aloud.
Colors are checked against the contrast ratios in the guidelines rather than approved by eye, which is a deliberate choice: eyeballing contrast is how sites end up with pale gray text that looks refined on a designer's monitor and disappears on a phone in a car park. Text sizes are set in relative units, so if you have turned your browser text size up, the layout follows instead of clipping.
- Headings in a genuine order, one main heading per page
- Every interactive element reachable and operable with a keyboard alone
- A visible focus outline, never removed for the sake of tidiness
- Text alternatives on images that carry meaning
- Contrast ratios measured against the guideline figures
- Layout that survives browser zoom and a narrow phone screen
Forms, menus and the phone number
The contact form labels every field properly, so a screen reader announces what each box is for rather than reading an empty text input. Required fields are marked in text as well as by color. If a submission fails, the message appears in the page where you are rather than only as a color change, and it says what went wrong.
The navigation menu opens and closes from the keyboard and the button reports whether it is open. Nothing on the site depends on hover alone, because hover does not exist on a touch screen and does not exist for a keyboard user either. And the phone number is a real link on every page, at the top and in the footer, so a call is always one action away no matter what else is in your way.
What we know is not perfect
Being straight about this is more useful than a clean claim. Some of our longer pages carry wide tables, and a wide table on a small screen has to scroll sideways inside its own box. We think that is better than squeezing five columns into a phone screen until every cell wraps to four lines, but it is still an awkward pattern and we are looking at it.
The spam protection on the contact form is a third party widget, so its behavior and its own accessibility are not entirely in our hands. If it blocks you, call instead and nothing is lost. Content also gets added over time, and a new page can slip through with a heading level out of order or a description missing on an image. We would rather be told than assume nobody hit it.
- We do not claim a formal audit or a certification
- We do not claim every page has been tested with every screen reader and browser combination
- We cannot control the accessibility of the third party spam check on the form
- We cannot control how another company's site behaves if you follow a link off ours
Telling us something is broken
Call the number on this site, or use the contact form if that works for you. What helps most is which page, what you were trying to do, and what got in the way, plus the browser or assistive software you use if you know it. You do not need technical language. Something along the lines of the phone number on the cost page will not read out with my screen reader is exactly enough to find it.
If a page on this site is what is standing between you and getting a pest problem looked at, do not spend your afternoon on it. Ring the number and tell somebody what you are dealing with, and it gets handled by voice. Booking a visit has never needed the form.
Frequently Asked Questions
What standard does this site work to?
The Web Content Accessibility Guidelines version 2.1 at level AA, which is the level most public bodies and large organizations use as their target. We treat it as the yardstick we build and check against. We are not claiming a completed formal audit against it, and we say so on purpose.
Can I use this site with a screen reader or keyboard only?
That is how it is built. Headings run in a real order, links describe their destination, the menu opens from the keyboard and reports its state, form fields are properly labeled, and the focus outline is left visible. If you hit something that traps focus or reads out wrongly, tell us which page and we will fix it.
Something on the site will not work for me. What now?
Call the number at the top of any page. A booking has never required the form, and nothing about your inquiry is worse for being made by voice. If you have a moment afterwards, tell us what blocked you and roughly what you use, and it goes on the list to fix rather than getting forgotten.
The phone always works
If any part of this site gets in your way, call and speak to somebody. Tell us what you are seeing at home and we will take it from there.
Call (843) 896-1048