Skip to content
DashboardContact us

Today

Accessibility

A comprehensive review of WCAG 2.2 AA compliance via automated insights and manual verification.

97 out of 100

Accessibility

Automated Checks

32/33 Checks passed • Last tested 12 Nov 2026

Understanding Severity Levels

Automated tests catch some accessibility problems, not all of them, so a clean run doesn’t prove a page is accessible.

Severity is how badly a problem stops someone with a disability finishing a task. Here, each check’s level comes from the weight Lighthouse gives it in the score.

Critical

They can’t finish the task, and there’s no way around it. For example, a Pay button a keyboard or screen reader can’t reach.

Serious

The task is very hard to finish. There may be a workaround, but many people will give up. For example, a menu that keyboard focus skips, or an infographic with no alt text.

Moderate

It’s annoying, or it breaks a WCAG rule, but people can still finish the task. For example, a decorative icon with no empty alt, so a screen reader reads out its file name.

33 checks

Filter by category

Filter by user impact

Automated checks: 33 shown
CheckStatus

A button or link is too small to tap easily

Tiny or tightly packed buttons and links are hard to hit, so people tap the wrong thing or give up.

View Card: A button or link is too small to tap easily

Best practices · Serious

Fail

An ARIA attribute is used where it isn't allowed

Each role allows only certain ARIA attributes, and screen readers ignore any other — so people miss what it was meant to say.

View Card: An ARIA attribute is used where it isn't allowed

ARIA · Critical

Pass

The whole page is hidden from screen readers

With aria-hidden="true" on the body, screen readers find nothing on the page, so blind visitors can't read or use any of it.

View Card: The whole page is hidden from screen readers

ARIA · Critical

Pass

A role is missing an ARIA attribute it needs

Some roles need a state, like checked or expanded. Without it, screen reader users can't tell whether a control is on, off, open or closed.

View Card: A role is missing an ARIA attribute it needs

ARIA · Critical

Pass

A list-type role is missing the items it needs inside

When a list, menu, tab list or table role has no proper items inside, screen readers can't count or describe them, so people lose their place.

View Card: A list-type role is missing the items it needs inside

ARIA · Critical

Pass

A role attribute uses a value that doesn't exist

When role is misspelt, made up or abstract, screen readers ignore it — so people can't tell what the element is or how to use it.

View Card: A role attribute uses a value that doesn't exist

ARIA · Critical

Pass

An ARIA attribute has a value that isn't allowed

When an ARIA attribute holds a wrong or misspelled value, screen readers ignore it or guess — so people miss whether something is open, checked or current.

View Card: An ARIA attribute has a value that isn't allowed

ARIA · Critical

Pass

An ARIA attribute name is misspelled or made up

Screen readers ignore any ARIA attribute with a wrong name, so a label, hint or hidden setting silently never reaches the person.

View Card: An ARIA attribute name is misspelled or made up

ARIA · Critical

Pass

A button has no name a screen reader can say

A screen reader announces just "button", so people can't tell what it does — close, search, delete or buy.

View Card: A button has no name a screen reader can say

Names · Critical

Pass

An image has no text alternative

Screen readers can't describe an image with no text alternative, so people miss what it shows, or hear a meaningless file name instead.

View Card: An image has no text alternative

Names · Critical

Pass

A form field has no label

Screen readers can't say what a field is for, so people don't know what to type or choose.

View Card: A form field has no label

Names · Critical

Pass

The page stops people from zooming in

The page's settings block pinch-zoom on phones, so people who need bigger text can't make it bigger and may not be able to read it.

View Card: The page stops people from zooming in

Best practices · Critical

Pass

An ARIA attribute breaks the rules for this element

Some ARIA attributes only work in certain situations, and when misused, screen readers announce the wrong state or nothing at all.

View Card: An ARIA attribute breaks the rules for this element

ARIA · Serious

Pass

Hidden content can still receive keyboard focus

Something is hidden from screen readers but can still be reached with Tab, so focus lands on a control that says nothing at all.

View Card: Hidden content can still receive keyboard focus

ARIA · Serious

Pass

An ARIA label is on an element that can't have one

Some elements aren't allowed a hidden label, so screen readers may skip it — and people miss the words you meant them to hear.

View Card: An ARIA label is on an element that can't have one

ARIA · Serious

Pass

Text colour is too close to its background colour

When text and background are too similar, many people can't read the words — especially in sunlight, on cheap screens, or with ageing or low vision.

View Card: Text colour is too close to its background colour

Contrast · Serious

Pass

The page has no title

Without a page title, people can't tell which page or tab they're on, and screen readers announce only the web address or nothing useful.

View Card: The page has no title

Names · Serious

Pass

The page doesn't say what language it's in

Without a language set on the page, screen readers may read the words with the wrong accent and rules, making them hard or impossible to understand.

View Card: The page doesn't say what language it's in

Language · Serious

Pass

The page's language code is not a real language

The page says it's written in a language that doesn't exist, so screen readers guess the voice and accent — and often read the words wrongly.

View Card: The page's language code is not a real language

Language · Serious

Pass

A list contains something other than list items

When a list holds items that aren't marked as list items, screen readers may miscount it or skip things — so people lose track of what's in it.

View Card: A list contains something other than list items

Tables · Serious

Pass

A list item sits outside a list

When an <li> isn't inside a <ul> or <ol>, screen readers may not announce it as a list, so people lose the count and grouping.

View Card: A list item sits outside a list

Tables · Serious

Pass

An element has a tabindex greater than zero

A positive tabindex forces that element to the front of the Tab order, so keyboard users jump around the page in a confusing order.

View Card: An element has a tabindex greater than zero

Navigation · Serious

Pass

A definition list contains the wrong elements

When a <dl> holds stray elements or terms in the wrong order, screen readers may miss which description belongs to which term.

View Card: A definition list contains the wrong elements

Tables · Serious

Pass

Term and description items sit outside a description list

When <dt> or <dd> items aren't inside a <dl>, screen readers can't tell which description belongs to which term, or how many pairs there are.

View Card: Term and description items sit outside a description list

Tables · Serious

Pass

A table cell's headers attribute points to the wrong cells

When a cell's headers list names cells that aren't headers in the same table, screen reader users don't hear which row or column the data belongs to.

View Card: A table cell's headers attribute points to the wrong cells

Tables · Serious

Pass

Heading levels skip a step, like jumping from h2 to h4

When heading levels skip, screen reader users may think they missed a section, and the page outline stops making sense.

View Card: Heading levels skip a step, like jumping from h2 to h4

Navigation · Moderate

Pass

The page has no main content area marked up

Screen reader users can't jump straight to the page's main content, so they must wade through the header and menus on every page.

View Card: The page has no main content area marked up

Best practices · Moderate

Pass

An outdated ARIA role is used

The page uses a role that has been retired from ARIA, so screen readers may ignore it or handle it differently, and people can't tell what the content is.

View Card: An outdated ARIA role is used

ARIA · Moderate

Pass

A form field's autocomplete value is misspelt or not recognised

When a field's autocomplete value is wrong, the browser can't fill in someone's details for them, so they must type everything by hand.

View Card: A form field's autocomplete value is misspelt or not recognised

Best practices · Moderate

Pass

An element marked to be ignored is still announced

Something marked as decoration still gets announced or takes keyboard focus. Screen reader users then hear clutter that was meant to stay silent.

View Card: An element marked to be ignored is still announced

Best practices · Moderate

Pass

An SVG marked as an image has no text alternative

The SVG is announced as an image, but with no name, so screen reader users hear "image" and never learn what it shows.

View Card: An SVG marked as an image has no text alternative

Best practices · Moderate

Pass

0 out of 100

Accessibility

Manual Checks

0/29 Checks completed • Not tested yet

Understanding Manual Checks

Lighthouse can’t test everything. Some checks need a person: using the page with only a keyboard, listening to it with a screen reader, following the focus order, and reading the words for clarity.

Each check is tested by hand against the WCAG 2.2 criteria in its Coverage column, and has one of four statuses:

  • Not started: nobody has tested it here yet, so it counts as failed.
  • Pass: a person tested it and it meets the criteria.
  • Fail: a person tested it and found a problem.
  • Not applicable: the site has nothing this check covers, so it’s left out of the score.

The score is the share of checks that passed, so it climbs as they’re tested.

User Impact is who gets stopped if a check fails, in the same levels as Severity on the automated checks. Effort is roughly how long it takes to test: Low is 1 to 5 minutes, Medium is 5 to 15, and High is over 15 minutes or needs something set up first, like a phone or a screen reader. Start with the quick wins near the top of the list.

29 checks

Manual checks: 29 shown, sorted by User Impact, descending
Check / Coverage / Evaluator Notes
Not started
Desktop screen reader checks: NVDA with Chrome and Firefox, VoiceOver with Safari

Critical · High effort

Manual assistive tech verification across browsers
Not started
Keyboard tabbing reaches all controls with no keyboard traps

Critical · High effort

Not started
Real-device checks in mobile Safari with VoiceOver

Critical · High effort

Manual iOS and VoiceOver verification
Not started
Real-device checks on Android with TalkBack

Critical · High effort

Manual Android and TalkBack verification
Not started
Sign-in, if there is any, needs no memory test or puzzle without an alternative

Serious · Low effort

WCAG 3.3.8
Not started
Videos include captions, and audio/video has a transcript or alternative

Serious · Low effort

Not started
Active filters, errors and tags don't rely on colour alone

Serious · Medium effort

WCAG 1.4.1
Not started
Focus indicators are visible and not obscured

Serious · Medium effort

Not started
Focus outlines, borders and icons reach 3:1 against what's next to them

Serious · Medium effort

WCAG 1.4.11
Not started
Gestures have a single-pointer alternative, and a press can be cancelled

Serious · Medium effort

WCAG 2.5.1, WCAG 2.5.2
Not started
Moving or updating content can be paused, stopped or hidden

Serious · Medium effort

WCAG 2.2.2
Not started
Responsive layouts and touch targets across breakpoints

Serious · Medium effort

Not started
Text stays readable with spacing overridden: line, paragraph, letter and word

Serious · Medium effort

WCAG 1.4.12
Not started
Visible labels are part of each control's accessible name

Serious · Medium effort

WCAG 2.5.3
Not started
Zoom and reflow at 200% without content loss

Serious · Medium effort

Not started
Every interactive element meets the 24 by 24 pixel target size or its spacing exception

Serious · High effort

WCAG 2.5.8
Not started
Images, including older content, have meaningful text alternatives

Serious · High effort

Not started
PDFs and other documents are tagged, navigable, and screen-reader compatible

Serious · High effort

Not started
Real-device checks in mobile Chrome

Serious · High effort

Manual interaction and assistive tech verification
Not started
Forms don't ask again for what a person has already entered

Moderate · Low effort

WCAG 3.3.7
Not started
Maps and interactive embeds provide an accessible text alternative

Moderate · Low effort

Not started
Print stylesheet preserves core content readability

Moderate · Low effort

Print accessibility checks
Not started
Single-key shortcuts can be turned off, remapped or work only on focus

Moderate · Low effort

WCAG 2.1.4
Not started
Skip links appear early and move focus to main content

Moderate · Low effort

Not started
Technical content is written in plain language or offers a simpler summary

Moderate · Medium effort

Not started

About this Report

Status: Draft Accessibility Conformance Report (Work in Progress)

This draft report utilizes the VPAT® 2.5 framework to assess the PANDAUX website against WCAG 2.2 Levels A and AA, as well as two selected Level AAA criteria.

Please note:

  • This document is an unfinalised Working Draft and does not constitute a formal claim of conformance.
  • While official VPAT® guidelines restrict the term “Not Evaluated” exclusively to Level AAA criteria, it is used provisionally throughout this draft across Levels A and AA to indicate items where testing is currently underway. A status of “Not Evaluated” does not indicate failure or non-conformance.

Report Summary

Product
PANDAUX website
Evaluation Date
16 November 2026
Evaluator(s)
    Automated testing
    Google Lighthouse 13.6.0 (axe-core 4.14.0)
    Status
    Draft (Not yet evaluated)

    Evaluation Scope & Coverage

    Target Standard
    WCAG 2.1 & 2.2 Level A / AA
    Audit Progress
    0% Complete (0 of 58 criteria evaluated; 58 pending manual/assistive tech review)

    Known gaps

    • This is a draft, not a claim of WCAG conformance. Every criterion is Not Evaluated until the manual checks are done and a Reviewer approves it.

    Criteria Conformance Summary

    58 criteria

    WCAG criteria: 58 listed, sorted by Criterion, ascending
    1.1.1 Non-text ContentA

    Not Evaluated

    1.2.1 Audio-only and Video-only (Prerecorded)A

    Not Evaluated

    1.2.2 Captions (Prerecorded)A

    Not Evaluated

    1.2.3 Audio Description or Media Alternative (Prerecorded)A

    Not Evaluated

    1.2.4 Captions (Live)AA

    Not Evaluated

    1.2.5 Audio Description (Prerecorded)AA

    Not Evaluated

    1.3.1 Info and RelationshipsA

    Not Evaluated

    1.3.2 Meaningful SequenceA

    Not Evaluated

    1.3.3 Sensory CharacteristicsA

    Not Evaluated

    1.3.4 OrientationAA

    Not Evaluated

    1.3.5 Identify Input PurposeAA

    Not Evaluated

    1.4.1 Use of ColorA

    Not Evaluated

    1.4.2 Audio ControlA

    Not Evaluated

    1.4.3 Contrast (Minimum)AA

    Not Evaluated

    1.4.4 Resize TextAA

    Not Evaluated

    1.4.5 Images of TextAA

    Not Evaluated

    1.4.10 ReflowAA

    Not Evaluated

    1.4.11 Non-text ContrastAA

    Not Evaluated

    1.4.12 Text SpacingAA

    Not Evaluated

    1.4.13 Content on Hover or FocusAA

    Not Evaluated

    2.1.1 KeyboardA

    Not Evaluated

    2.1.2 No Keyboard TrapA

    Not Evaluated

    2.1.4 Character Key ShortcutsA

    Not Evaluated

    2.2.1 Timing AdjustableA

    Not Evaluated

    2.2.2 Pause, Stop, HideA

    Not Evaluated

    2.3.1 Three Flashes or Below ThresholdA

    Not Evaluated

    2.4.1 Bypass BlocksA

    Not Evaluated

    2.4.2 Page TitledA

    Not Evaluated

    2.4.3 Focus OrderA

    Not Evaluated

    2.4.4 Link Purpose (In Context)A

    Not Evaluated

    2.4.5 Multiple WaysAA

    Not Evaluated

    2.4.6 Headings and LabelsAA

    Not Evaluated

    2.4.7 Focus VisibleAA

    Not Evaluated

    2.4.11 Focus Not Obscured (Minimum)AA

    Not Evaluated

    2.5.1 Pointer GesturesA

    Not Evaluated

    2.5.2 Pointer CancellationA

    Not Evaluated

    2.5.3 Label in NameA

    Not Evaluated

    2.5.4 Motion ActuationA

    Not Evaluated

    2.5.7 Dragging MovementsAA

    Not Evaluated

    2.5.8 Target Size (Minimum)AA

    Not Evaluated

    3.1.1 Language of PageA

    Not Evaluated

    3.1.2 Language of PartsAA

    Not Evaluated

    3.1.5 Reading LevelAAA

    Not Evaluated

    3.2.1 On FocusA

    Not Evaluated

    3.2.2 On InputA

    Not Evaluated

    3.2.3 Consistent NavigationAA

    Not Evaluated

    3.2.4 Consistent IdentificationAA

    Not Evaluated

    3.2.5 Change on RequestAAA

    Not Evaluated

    3.2.6 Consistent HelpA

    Not Evaluated

    3.3.1 Error IdentificationA

    Not Evaluated

    3.3.2 Labels or InstructionsA

    Not Evaluated

    3.3.3 Error SuggestionAA

    Not Evaluated

    3.3.4 Error Prevention (Legal, Financial, Data)AA

    Not Evaluated

    3.3.7 Redundant EntryA

    Not Evaluated

    3.3.8 Accessible Authentication (Minimum)AA

    Not Evaluated

    4.1.1 ParsingA

    Not Evaluated

    4.1.2 Name, Role, ValueA

    Not Evaluated

    4.1.3 Status MessagesAA

    Not Evaluated

    Powered by

    97 out of 100, full report on automated checks

    Accessibility Scorecard

    Last tested by the Access-o-Meter WCAG accessibility checker on 12 Nov 2026.