Accessibility Audit Report

WCAG 2.2 Level AA · 1 page scanned · 18-Aug-2026

Download PDF
92%CHECKS PASSED

8 issues found across 1 page, checked against WCAG 2.2 Level AA.

36 of 39 automated checks passed.

0
Critical
⚠
Immediate attention needed
8
High
!
Should be addressed
0
Medium
−
Consider improvements
0
Low
✓
Minor issues
⚠ Significant barriers found. Nothing blocks users outright, but 8 high-priority issues make these pages materially harder to use, and would be raised in a formal accessibility review.

What this means for your visitors

Around 1 in 5 people has a disability that can affect how they use a website. On the pages we scanned, some of them cannot complete key tasks today — they will leave, and you will never see it in your analytics as anything other than a bounce.

Where the issues are

Number of individual problems found in each area, across every page scanned.

Keyboard Access5Images & Media2Colour & Contrast1

⚡ Priority action plan

Start here. These are the highest-impact fixes across the pages we scanned.

  1. 1There's no visible focus indicator (5 places)High
  2. 2Embedded content has no title (2 places)High
  3. 3Text is hard to read against its backgroundHigh

Fixing these clears 3 of your 3 most serious issue types.

Want these fixed?

Our team can remediate all 8 issues and re-audit to confirm you're compliant.

Book a free consultation

Results by category

Every automated check we ran, grouped by the part of the experience it affects. A category passes only when every check in it passed on every page scanned.

Images & MediaNeeds attention
4 of 5 checks passed

Images, icons, audio and video have text alternatives so they still make sense to someone who can't see or hear them.

  • ✗Frames must have an accessible name (2 places)High4.1.2
  • ✓Documents must have <title> element to aid in navigation
  • ✓Images must have alternative text
  • ✓[role="img"] elements must have alternative text
  • ✓All touch targets must be 24px large, or leave sufficient space
Colour & ContrastNeeds attention
1 of 2 checks passed

Text stands out enough from its background to stay readable in poor light or with reduced vision.

  • ✗Elements must meet minimum color contrast ratio thresholdsHigh1.4.3
  • ✓Links must be distinguishable without relying on color
Forms & InputsPassed
4 of 4 checks passed

Every field is clearly labelled, so people know what to type and screen readers can announce it.

  • ✓autocomplete attribute must be used correctly
  • ✓Form field must not have multiple label elements
  • ✓Form elements must have labels
  • ✓Select element must have an accessible name
Keyboard AccessNeeds attention
3 of 4 checks passed

The whole page can be operated with a keyboard alone, without getting stuck, and the focused item is always visible.

  • ✗No visible focus indicator (outline/box-shadow) on keyboard focus (5 places)High2.4.7
  • ✓Page must have means to bypass repeated blocks
  • ✓Interactive controls must not be nested
  • ✓Scrollable region must have keyboard access
Page StructurePassed
4 of 4 checks passed

Headings, landmarks and lists are used properly, so assistive tech can navigate the page in a sensible order.

  • ✓Inline text spacing must be adjustable with custom stylesheets
  • ✓IDs used in ARIA and labels must be unique
  • ✓<ul> and <ol> must only directly contain <li>, <script> or <template> elements
  • ✓<li> elements must be contained in a <ul> or <ol>
Labels & Screen ReadersPassed
16 of 16 checks passed

Buttons, links and controls have names that describe what they do when read aloud.

  • ✓Elements must only use supported ARIA attributes
  • ✓ARIA commands must have an accessible name
  • ✓ARIA attributes must be used as specified for the element's role
  • ✓Deprecated ARIA roles must not be used
  • ✓aria-hidden="true" must not be present on the document body
  • ✓ARIA hidden element must not be focusable or contain focusable elements
  • ✓Elements must only use permitted ARIA attributes
  • +9 more checks passed
LanguagePassed
3 of 3 checks passed

The page declares its language so screen readers use the right pronunciation.

  • ✓<html> element must have a lang attribute
  • ✓<html> element must have a valid value for the lang attribute
  • ✓lang attribute must have a valid value
Mobile & ZoomPassed
1 of 1 checks passed

Content reflows and stays usable when zoomed in or viewed on a small screen.

  • ✓Zooming and scaling must not be disabled

Full breakdown

Every issue we found, worst first — what it is, who it affects, and what fixes it.

IssueSeverityPagesBusiness ImpactRecommendation
Embedded content has no title
Images & Media · frame-title · WCAG 4.1.2 · 2 places
High1Embedded content (video, map, form) has no title, so screen-reader users hear only "frame" and have no idea whether it is worth entering.Add a title="..." attribute to the <iframe> describing its content, e.g. title="Product demo video".
Text is hard to read against its background
Colour & Contrast · color-contrast · WCAG 1.4.3
High1Text is hard to read for anyone with reduced vision, and for everyone on a phone in daylight. Low-contrast pricing, form labels and calls-to-action measurably reduce conversion.Darken the text color or lighten the background until the contrast ratio reaches 4.5:1 (3:1 is enough for large text — ≥18pt, or ≥14pt bold). Check hover/focus states too, not just the default.
There's no visible focus indicator
Keyboard Access · focus-visible · WCAG 2.4.7 · 5 places
High1There is no visible focus indicator, so keyboard users cannot see where they are on the page. Navigating becomes guesswork.Don't remove the default focus outline (outline:none) without replacing it — add a visible :focus-visible style (outline or box-shadow) with enough contrast against the background.

Pages scanned

  • Headshots Cary NC & Raleigh NC by Photographer Sarah Wilson | Headshots Near Mehttps://sarahannewilsonphotography.com8 issues
15 items need a human check. Some things software genuinely cannot judge — whether text over a photograph is readable, or whether a custom component behaves the way it claims to. These are excluded from the counts above rather than guessed at. A manual review is the only way to settle them.
Report generated on 18-Aug-2026 · Scanned with axe-core against WCAG 2.2 Level AA Based on automated scanning. Guidance to help prioritise remediation, not a legal determination.