Accessibility Statement

1. Automated test results

Every page was scanned with axe-core 4.10.2 using the WCAG 2.0, 2.1 and 2.2 Level A and AA rule sets, at a 1440px desktop width and a 390px phone width, with all scroll-triggered content forced into view first so nothing was skipped.

0

Violations

16

Page scans

100%

Pass rate

Automated testing catches roughly a third to a half of accessibility problems. It does not judge whether alt text is accurate, whether a heading describes its section, or whether a keyboard path makes sense. Those were checked by hand, page by page.

Pages covered

• Home, About, Services, Contact
• Privacy Policy, Terms and Conditions, Cookie Policy
• This page

2. Key tests passed

• Colour contrast. Every text and background pair meets 4.5:1, and large text meets 3:1. The muted grey used for captions and footer type was darkened to 5.2:1 on the page background.
• Images. Every image carries alt text, or an empty alt where the image repeats adjacent wording and would only add noise.
• Headings. One h1 per page, no skipped levels, and every section heading describes what follows.
• Landmarks. Header, main, navigation and footer are real landmarks, and every navigation has its own label.
• Forms. Every field has a visible label tied to its input, an appropriate autocomplete value and a 48px target.
• Links and buttons. Every control has an accessible name. Links that open a new tab say so in their name.
• Tables. Price tables use real row and column headers with a caption, and each scrolling table is reachable and scrollable from the keyboard.
• Language. Every page declares its language.
• Zoom and reflow. No horizontal scrolling at 320px, which is the same as 400% zoom on a 1280px screen.
• Text spacing. Increasing line height, letter spacing and word spacing to the WCAG limits clips no content.
• Focus not obscured. Keyboard focus remains visible above the sticky header and the fixed cookie notice.
• Target size. Standalone controls clear the WCAG 2.2 minimum, and phone navigation controls provide at least a 44px target.

3. Why there is no accessibility overlay

Overlay widgets — the toolbars that float a wheelchair icon in the corner and promise instant compliance — are not used here, deliberately.

• They do not fix the underlying markup. They guess at it from the browser, and a guess is not a fix.
• They frequently break assistive technology that already works. Screen reader and browser users report overlays fighting their own settings.
• They do not prevent claims. Businesses running overlays have been sued over the same barriers the overlay was sold to remove.
• Several of them detect and identify screen reader users, which is a privacy problem in its own right.

The alternative is slower and it works: fix the HTML, the contrast and the keyboard paths in the page itself, then test the result. That is what was done here.

4. Accessible features

Keyboard

• A skip link is the first thing you reach on every page, and it jumps straight to the main content.
• Everything interactive can be reached and operated with Tab, Enter and Space. Nothing traps focus.
• Focus is always visible: a 2px accent outline with a 3px offset, never removed.
• The phone menu reports its open or closed state, moves focus to its first link, closes on Escape, and returns focus to the button that opened it.
• Price tables that scroll sideways on a phone are focusable, so they can be scrolled with the arrow keys.

Screen readers

• Semantic HTML throughout — real headings, lists, tables, buttons and links rather than styled divs.
• The logo in the header is marked decorative because the company name sits beside it as text.
• The cookie notice is a labelled region, not a modal, so it never steals focus or blocks the page.

Motion and media

• All motion is transform and opacity only, and every animation stops when your system is set to reduce motion, including when that preference changes while the page is open.
• The button shine and the scrolling marquee are removed outright under reduced motion, not merely slowed.
• The background video is silent, never autoplays with sound, has a keyboard-operable Pause/Play control, and carries a text description of what it shows.
• Nothing flashes, and nothing moves for longer than five seconds without a way to stop it.

Vision and layout

• All type is set in relative units, so browser text sizing works normally.
• The layout reflows to a single column down to 320px with no sideways scrolling.
• Colour is never the only way information is conveyed.
• Standalone controls and navigation targets are at least 44px on a phone; inline links remain part of their surrounding text.
• Forced-colours mode preserves visible control boundaries and focus outlines.

5. Known limits

Stating these is part of the point. We would rather tell you than have you find out.

• Booking. The Book online button opens MoEgo, our third-party booking system. We do not control its code and cannot promise it meets the same standard. If it blocks you, call 480.544.7457 and we will book you over the phone, at the same price.
• Video captions. The looping clip on the home page has no audio track, so there is nothing to caption. It carries a text description instead. Automated scanners flag it for manual review, which is why it is mentioned here rather than hidden.
• Typefaces. Fonts are stored with the site. If a font file does not load, the page falls back to your system typeface with no loss of content.
• Assistive technology testing. Accessible names, roles and states were inspected in the browser accessibility tree. A physical VoiceOver, NVDA or TalkBack session has not yet been completed.

6. Tell us what is broken

If any part of this site keeps you from booking a groom or finding a price, we want to hear about it, and we will fix it rather than explain it away.

• Email: Dirtypawsstg@gmail.com
• Phone: 480.544.7457

Tell us the page, what you were trying to do, and the browser or assistive technology you use. We aim to reply within five working days. If a fix will take longer than that, we will give you another way to get the same thing done in the meantime.

7. Standards

• WCAG 2.2 Level AA — Web Content Accessibility Guidelines, W3C Recommendation.
• Section 508 — which incorporates WCAG 2.0 Level AA by reference.
• ADA Titles II and III — the Department of Justice treats WCAG as the practical benchmark for web accessibility.
• EN 301 549 — the European standard, which incorporates WCAG 2.1 Level AA.
• WAI-ARIA 1.2 — used only where native HTML could not do the job.

How this was tested

• axe-core 4.10.2, automated, all eight pages, at 1440px and 390px, including the WCAG 2.2 AA rule set.
• Manual keyboard traversal of every page, including the phone menu and the cookie notice.
• Reflow checked at 320px, 360px, 375px, 390px and 460px.
• Text spacing checked against the WCAG 1.4.12 limits.
• Contrast ratios calculated from the computed colours rather than estimated by eye.
• Reduced motion verified with the system setting on.
• Forced-colours mode and browser accessibility-tree states verified in Chromium.

← Back to Dirty Paws