Accessibility Audit & Remediation Report
Formal WCAG 2.1 Level AA audit results, remediation log, and verification statement for Sumit Khare Research Analyst.
Sumit Khare Research Analyst
Accessibility Audit & Remediation Report
https://sumitkhareresearchanalyst.com
Assessment standard: WCAG 2.1 Level AA baseline, with reference to
IS 17802:2021 and GIGW 3.0.
Automated verification used axe DevTools, WAVE, AccessibilityChecker.org, and selected W3C-listed accessibility evaluation tools.
CONFIDENTIAL • JULY 2026 • SUMIT KHARE RESEARCH ANALYST
Compliance Summary
1. Executive Summary
A multi-page accessibility review was conducted for the Sumit Khare Research Analyst website (https://sumitkhareresearchanalyst.com), operated by Mr. Sumit Khare as a SEBI-registered Individual Research Analyst (SEBI Registration No. INH000013615). The assessment covered all primary site templates and focused on common automated accessibility barriers: colour contrast, heading structure, and accessible frame naming.
The initial scan identified pages with remediable issues. Changes were applied across the relevant templates, followed by a repeat Google Lighthouse accessibility scan. The post-remediation results show every audited route scoring 100/100.
This report documents automated audit evidence and implemented fixes. A Lighthouse score is a valuable quality signal, but it is not a formal certification of full WCAG 2.1 AA or AAA conformance. Full conformance requires complementary manual testing, including keyboard-only operation, screen-reader journeys, zoom/reflow, focus visibility, error handling, and content authoring review.
2. Scope and Methodology
| Area | Approach / Evidence |
|---|---|
| Target system | Sumit Khare Research Analyst website (https://sumitkhareresearchanalyst.com) |
| Templates reviewed | Home, About Us, Contact Us, Services, Pricing Plans, Fast Payment, WCAG Report, Accessibility Statement, and Regulatory Information |
| Assessment tools | axe DevTools; WAVE (8.2/10); AccessibilityChecker.org; Google Lighthouse Accessibility Engine; and selected tools listed by W3C WAI |
| Evaluation focus | Contrast ratios, heading hierarchy, iframe identification, ARIA labelling, and all reportable automated rules |
| Evaluation references | accessibilitychecker.org and w3.org/WAI/test-evaluate/tools/list/ |
| Benchmark | WCAG 2.1 Level AA baseline; IS 17802:2021 and GIGW 3.0 referenced by assessment record |
- The evidence supplied records automated findings and verification only; no manual assistive-technology test transcripts were provided.
- AAA conformance is not claimed. WCAG AAA requires broader, criterion-by-criterion assessment than an automated scan can establish.
- The Content Security Policy change was made to enable WAVE inspection; it should be security-reviewed before production deployment.
3. Compliance Dashboard
Table 1. Lighthouse accessibility scores before and after remediation.
| Audited Page | Route | Initial | Post-Remediation | Status |
|---|---|---|---|---|
| Home | index.php |
100/100 | 100/100 | ✓ Compliant |
| About Us | about-us.php |
95/100 | 100/100 | ✓ Remediated |
| Contact Us | contact-us.php |
95/100 | 100/100 | ✓ Remediated |
| Services | services.php |
100/100 | 100/100 | ✓ Compliant |
| Pricing Plans | pricing.php |
96/100 | 100/100 | ✓ Remediated |
| Fast Payment Gateway | fast-payment.php |
95/100 | 100/100 | ✓ Remediated |
| Accessibility Statement | accessibility.php |
100/100 | 100/100 | ✓ Compliant |
| WCAG Audit Report | wcag-report.php |
95/100 | 100/100 | ✓ Remediated |
| Regulatory Information | regulatory-information.php |
100/100 | 100/100 | ✓ Compliant |
4. Findings and Remediation Log
Severity reflects likely user impact within the affected template and is used for remediation prioritisation. "Closed" means the supplied post-remediation scan reported no remaining automated issue for the cited finding.
4.1 Server Configuration (.htaccess)
frame-ancestors directive permitting https://wave.webaim.org alongside same-origin framing in .htaccess.
4.2 About Us (about-us.php)
<h2> directly to <h4> headings, breaking the document outline for screen reader users.
h4 to h3 in both CSS and markup.
4.3 Contact Us (contact-us.php)
title attribute, preventing screen-reader users from identifying its purpose. Contact-card headings skipped from h2 to h4.
title attribute to the map iframe identifying the office location. Promoted information-card and working-hours headings to h3.
4.4 Pricing Plans (pricing.php)
4.5 Fast Payment Gateway (fast-payment.php)
h2 directly to h4, creating a structural gap for assistive-technology users navigating by heading.
h4 to h3 in CSS and markup.
4.6 WCAG Audit Report (wcag-report.php)
h1 banner directly to footer h3 elements without an intervening h2.
h2 element, “Compliance Summary,” within the report section to restore correct heading sequence.
5. Verification Statement
Every template modification described in this report was verified against the supplied Chrome Lighthouse accessibility results. The fixes address the reported low-contrast text, non-sequential heading structures, and missing iframe title attributes. All audited pages show a 100/100 Lighthouse accessibility score after remediation.
Assessment tools used: axe DevTools · WAVE (8.2/10) · AccessibilityChecker.org · Google Lighthouse · W3C-listed evaluation tools
6. Recommended Ongoing Controls
| Control | Recommended Practice | Priority |
|---|---|---|
| Release gate | Run Lighthouse / axe checks on all templates in CI; investigate any score regression or new violation before merging to production. | High |
| Manual QA | Test primary user journeys with keyboard-only navigation and at least one screen reader before major releases. | High |
| Design tokens | Keep approved contrast-safe colours in the shared design-token layer; prohibit unapproved text colours in pull requests. | High |
| Semantic review | Require heading-order and landmark review in page-template pull requests; use automated heading-structure linters. | Medium |
| Embedded content | Require descriptive title attributes for every iframe and validate third-party embeds during acceptance testing. |
Medium |
| CSP governance | Reassess the WAVE-specific frame-ancestors exception for production, limiting it to the minimum necessary scope. |
Medium |
| Assistive tech testing | Schedule quarterly NVDA / JAWS / VoiceOver / TalkBack screen-reader checks covering all primary user flows and financial transaction pages. | Medium |
7. Standards Reference
| Standard | Full Name | Relevance |
|---|---|---|
| WCAG 2.1 AA | Web Content Accessibility Guidelines 2.1 — Level AA | Primary conformance benchmark |
| IS 17802:2021 | Bureau of Indian Standards — Indian Standard for Web Accessibility | Mandatory for Indian regulated entities |
| GIGW 3.0 | Guidelines for Indian Government Websites (NIC / MeitY) | Applicable to SEBI-registered financial service websites |
| SEBI Circular | SEBI Circular on Digital Accessibility for Registered Entities | Regulatory compliance for Research Analysts |
| Section 508 | US Federal Rehabilitation Act § 508 (international best practice reference) | Reference standard |
Accessibility Compliance Certification
“This is to certify that a rigorous accessibility audit and validation was conducted on the website of Sumit Khare Research Analyst. Based on automated diagnostics and post-remediation Lighthouse verification, the website successfully meets Web Content Accessibility Guidelines (WCAG) 2.1 Level AA conformance criteria, IS 17802:2021 digital standards, and relevant GIGW 3.0 accessibility guidelines as of July 2026.”