For teams preparing SEBI digital accessibility submissions, one detail matters:
Table C3 is not the full audit report.
It is the submission table. The initial accessibility audit report should be attached as a consolidated PDF.
What developers and QA teams should know
The table asks for high-level details:
- Auditor or firm
- Audit completion date
- Platforms covered
- Terms of reference
- Scope
- Key findings
- Observations
- Action plan
- Remediation timelines
The attached report should contain the actionable implementation detail.
What should be in the attached report
The report should support remediation.
Useful findings usually include:
- Affected URL, screen, component, journey, or document
- Steps or context to reproduce
- Observed behavior
- Expected accessible behavior
- User impact
- Severity
- WCAG or other standards mapping
- Evidence
- Recommended fix direction
If the report does not provide this, developers may need to rediscover the issue before fixing it.
Scope and exclusions
Scope should be explicit.
If a portal, app, PDF, document library, login journey, form, or third-party flow was not tested, the report should say that. This keeps the C3 submission honest and prevents false confidence.
Preparing for later closure
C3 creates the initial baseline.
If the findings are traceable and the remediation timelines are practical, the later final-status stage is easier. Teams can show what changed, what remains open, and what evidence supports closure.
Final checklist
Before treating a C3 package as ready, check:
- Is the table filled accurately?
- Is the consolidated report attached?
- Is scope clear?
- Are findings reproducible?
- Is evidence included?
- Are standards mapped?
- Are remediation timelines realistic?
Read the original guide on IAAP Audit: https://iaapaudit.com/blog/sebi-table-c3-accessibility-audit-submission-guide
Top comments (0)