Accessibility Audit Report

WCAG 2.2 Level AA · 1 page scanned · 02-Sep-2026

Download PDF
76%CHECKS PASSED

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

22 of 29 automated checks passed.

1
Critical
⚠
Immediate attention needed
28
High
!
Should be addressed
0
Medium
−
Consider improvements
0
Low
✓
Minor issues
⚠ Compliance at risk. We found 1 critical issue that block some people from using these pages at all. In this state the site would likely fail an ADA Title II or Section 508 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.

Images & Media15Colour & Contrast7Keyboard Access6Mobile & Zoom1

⚡ Priority action plan

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

  1. 1Images are missing descriptionsCritical
  2. 2Tap targets are too small or too close together (14 places)High
  3. 3Text is hard to read against its background (5 places)High
  4. 4There's no visible focus indicator (5 places)High

Fixing these clears 4 of your 7 most serious issue types.

Want these fixed?

Our team can remediate all 29 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
1 of 3 checks passed

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

  • ✗Images must have alternative textCritical1.1.1
  • ✗All touch targets must be 24px large, or leave sufficient space (14 places)High2.5.8
  • ✓Documents must have <title> element to aid in navigation
Colour & ContrastNeeds attention
0 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 thresholds (5 places)High1.4.3
  • ✗Links must be distinguishable without relying on color (2 places)High1.4.1
Forms & InputsPassed
2 of 2 checks passed

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

  • ✓Form field must not have multiple label elements
  • ✓Form elements must have labels
Keyboard AccessNeeds attention
1 of 3 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
  • ✗Interactive controls must not be nestedHigh4.1.2
  • ✓Page must have means to bypass repeated blocks
Page StructurePassed
3 of 3 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
  • ✓<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
12 of 12 checks passed

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

  • ✓Elements must only use supported ARIA attributes
  • ✓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
  • ✓Required ARIA attributes must be provided
  • +5 more checks passed
LanguagePassed
2 of 2 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
Mobile & ZoomNeeds attention
1 of 2 checks passed

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

  • ✗Content overflows horizontally at 320px width (WCAG's equivalent of 400% zoom)High1.4.10
  • ✓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
Images are missing descriptions
Images & Media · image-alt · WCAG 1.1.1
Critical1Blind and low-vision customers get no idea what these images show. If they carry product or pricing information, those customers simply cannot access it — and image alt text is the single most-cited issue in ADA web lawsuits.Add a descriptive alt="..." attribute. If the image is purely decorative, use alt="" (empty) rather than omitting the attribute entirely.
Tap targets are too small or too close together
Images & Media · target-size · WCAG 2.5.8 · 14 places
High1Tap targets are too small or too close together, causing mis-taps for anyone with limited dexterity or using a phone one-handed.Make the tappable area at least 24×24px, or leave 24px of clear space around it. Padding on the link/button is usually enough — the visible icon itself doesn't have to grow.
Text is hard to read against its background
Colour & Contrast · color-contrast · WCAG 1.4.3 · 5 places
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.
Links are shown by colour alone
Colour & Contrast · link-in-text-block · WCAG 1.4.1 · 2 places
High1Links are distinguished from surrounding text by colour alone, so colourblind readers cannot tell what is clickable.Underline links inside body text, or otherwise distinguish them by something other than colour alone (weight, icon) so colourblind readers can spot them.
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.
Controls are nested inside each other
Keyboard Access · nested-interactive · WCAG 4.1.2
High1Controls are nested inside one another, so assistive technology announces them unpredictably and activating the right one becomes unreliable.Don't nest one interactive element inside another (e.g. a <button> inside an <a>) — flatten the markup so each control stands alone.
The page scrolls sideways on small screens
Mobile & Zoom · reflow-320 · WCAG 1.4.10
High1The page forces horizontal scrolling on small screens or at high zoom. Customers with low vision have to scroll in two directions to read a sentence, and most give up.Fix the layout so content reflows into a single column at narrow widths instead of requiring horizontal scrolling — look for fixed-width elements (px widths, unwrapped tables, non-responsive images) that don't shrink below their content's natural width.

Pages scanned

  • App Development & Digital Transformation Company USA - Innopplhttps://innoppl.com29 issues
6 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 02-Sep-2026 · Scanned with axe-core against WCAG 2.2 Level AA Based on automated scanning. Guidance to help prioritise remediation, not a legal determination.