Skip to content
http://gst-recon.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
85
GRADE
B
FIX
4
REVIEW
2
PASS
18
INFO
0
Checks
24
18 PASS 2 REVIEW 4 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-048tqt
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #024959 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h1 GST Reconciliation Software
1.48:1
#000000
on
#082E40
needs 3.0:1 (large text)
32px · above the fold
h2 Invoices a VLOOKUP Would Miss
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Powerful Features for GST Professionals
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How It Works
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Choose GST Recon?
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your GST Data
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 GST Reconciliation Guides
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get In Touch
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Free till 31 January
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
24px · bottom of viewport
h3 No template required. Upload your file a…
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 GSTR-2A and GSTR-2B
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Rule-Based Matching, Not AI Guesswork
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Smart Invoice Normalization
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Financial Year Handling
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Date & Tax Tolerance
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Multi-File & Credit Notes
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Columns Found Automatically
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Wrong-Month Check
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Saved Mappings per Client
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Drop Your Files
1.66:1
#000000
on
#0A3749
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 GST Reconciliation S…1.48:13.0:1
#000000
#082E40
Fail
h2 Invoices a VLOOKUP W…1.66:13.0:1
#000000
#0A3749
Fail
h2 Powerful Features fo…1.66:13.0:1
#000000
#0A3749
Fail
h2 How It Works1.66:13.0:1
#000000
#0A3749
Fail
h2 Why Choose GST Recon…1.66:13.0:1
#000000
#0A3749
Fail
h2 Your GST Data1.66:13.0:1
#000000
#0A3749
Fail
h2 GST Reconciliation G…1.66:13.0:1
#000000
#0A3749
Fail
h2 Get In Touch1.66:13.0:1
#000000
#0A3749
Fail
h2 Free till 31 January1.66:13.0:1
#000000
#0A3749
Fail
h3 No template required…1.66:13.0:1
#000000
#0A3749
Fail
h3 GSTR-2A and GSTR-2B1.66:13.0:1
#000000
#0A3749
Fail
h3 Rule-Based Matching,…1.66:13.0:1
#000000
#0A3749
Fail
h3 Smart Invoice Normal…1.66:13.0:1
#000000
#0A3749
Fail
h3 Financial Year Handl…1.66:13.0:1
#000000
#0A3749
Fail
h3 Date & Tax Tolerance1.66:13.0:1
#000000
#0A3749
Fail
h3 Multi-File & Credit …1.66:13.0:1
#000000
#0A3749
Fail
h3 Columns Found Automa…1.66:13.0:1
#000000
#0A3749
Fail
h3 Wrong-Month Check1.66:13.0:1
#000000
#0A3749
Fail
h3 Saved Mappings per C…1.66:13.0:1
#000000
#0A3749
Fail
h3 Drop Your Files1.66:13.0:1
#000000
#0A3749
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
  • H1 GST Reconciliation SoftwareFind Every Rupee of ITC in GSTR-2A, 2B & 3B
  • H2 Invoices a VLOOKUP Would Miss
  • H2 Powerful Features for GST Professionals
  • H3 No template required. Upload your file as it is.
  • H3 GSTR-2A and GSTR-2B
  • H3 Rule-Based Matching, Not AI Guesswork
  • H3 Smart Invoice Normalization
  • H3 Financial Year Handling
  • H3 Date & Tax Tolerance
  • H3 Multi-File & Credit Notes
  • H3 Columns Found Automatically
  • H3 Wrong-Month Check
  • H3 Saved Mappings per Client
  • H2 How It Works
  • H3 Drop Your Files
  • H3 Auto-Match
  • H3 Review
  • H3 Download Report
  • H2 Why Choose GST Recon?
  • H3 99.27% Match Rate
  • H3 Seconds, Not Hours
  • H3 Built for CAs
  • H3 Ready-to-Use Excel Report
  • H2 Your GST Data
  • H3 Deleted within 5 minutes
  • H3 Never sold or shared
  • H3 Your history, your choice
  • H2 GST Reconciliation Guides
  • H2 Get In Touch
  • H3 Phone / WhatsApp
  • H3 FAQ & Support
  • H4 Product
  • H4 Free Checks
  • H4 Guides
  • H4 Resources
  • H4 Free Tools
  • H4 Legal
  • H2 Free till 31 January
A+
Heading Text Quality
All 38 heading(s) have substantive, well-formed text
PASS
All 38 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 179 visible text node(s) render at >= 12 CSS pixels
PASS
All 179 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
Favicon & Branding
12 icon(s) detected
PASS
12 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: GST Recon — GSTR-2A & 2B Reconciliation
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name GST Recon — GSTR-2A & 2B Reconciliation ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name GST Recon — GSTR-2A & 2B Reconciliation Display Mode standalone Theme Color #024959 Background Color #ffffff Icons 8 icon(s)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 24 passed
PASS
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Free till 31 January Register by 22 November Workspace Starter with nothing t… body > div.fixed

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Use the purchase register exactly as your books export it to Excel, from Tally,… div.mx-auto > div.mt-10 > div > p.mt-1

These are opportunities to improve the legibility of your content.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
●`<td>` elements in a large `<table>` have one or more table headers.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback