Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction4 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
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.
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
F404 Error PageActionSoft 404 detectedFIX
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.
DPrint StylesheetActionNo print stylesFIX
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
CColor Contrast (Screenshot)Action20 text elements analyzed, 20 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 GST Reconciliation S… | 1.48:1 | 3.0:1 | #000000 | #082E40 | Fail |
| h2 Invoices a VLOOKUP W… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 Powerful Features fo… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 How It Works | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 Why Choose GST Recon… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 Your GST Data | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 GST Reconciliation G… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 Get In Touch | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h2 Free till 31 January | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 No template required… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 GSTR-2A and GSTR-2B | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Rule-Based Matching,… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Smart Invoice Normal… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Financial Year Handl… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Date & Tax Tolerance | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Multi-File & Credit … | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Columns Found Automa… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Wrong-Month Check | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Saved Mappings per C… | 1.66:1 | 3.0:1 | #000000 | #0A3749 | Fail |
| h3 Drop Your Files | 1.66:1 | 3.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 Hierarchy38 headingsPASS
- 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 QualityAll 38 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityNo imagesPASS
A+Form AccessibilityNo form controlsPASS
ALink & Button Quality44 links, 7 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://wa.me/918197615451?text=Hi, I ha… | Chat on WhatsApp | new tab | Add '(opens in new tab)' to text |
| http://falgunsoft.com/ | Falgunsoft Technologies | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://wa.me/918197615451?text=Hi, I have a question about GST Recon; http://falgunsoft.com/
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-PatternsNo explicit tabindex attributes foundPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 179 visible text node(s) render at >= 12 CSS pixelsPASS
AFavicon & Branding12 icon(s) detectedPASS
A+Web ManifestPWA-readyPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
ALighthouse Accessibility AuditsScore 92/100 — 2 failing, 24 passedPASS
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.
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.
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.