A portfolio for an accessibility auditor is a curated set of work samples, credentials, and case write-ups that proves you can identify WCAG issues and document them clearly. The strongest portfolios include redacted audit report samples, a written methodology, evidence of training or certification, and short case studies that show before-and-after remediation outcomes. You do not need a long client list to start. Two or three well-documented audits, paired with a clear explanation of how you evaluate against WCAG 2.1 AA or WCAG 2.2 AA, will carry more weight than a roster of vague engagements.
| Element | What to Include |
|---|---|
| Audit Report Samples | Two to three redacted reports showing issue descriptions, WCAG references, severity, and recommendations |
| Methodology Statement | A short page explaining how you evaluate, tools used, and the hands-on review process |
| Credentials | CPACC, WAS, DHS Trusted Tester, or relevant training completed |
| Case Studies | Brief write-ups of audit scope, issues identified, and remediation outcomes |
| Contact and Services | Clear list of audit types offered (web, mobile app, SaaS, ecommerce) and how to reach you |
Start With Real Audit Samples
The single most valuable item in your portfolio is a real audit report. Clients want to see how you write up issues, how you reference WCAG success criteria, and how clearly you communicate severity and recommended fixes.
If you have not been paid for an audit yet, conduct one on a website you have permission to evaluate. A nonprofit, a local business, or a personal project all work. The goal is to produce a report that mirrors what a paying client would receive.
Redact any identifying information before publishing the sample. Replace the client name, screenshots that reveal the brand, and any internal notes. What remains should show your issue structure, your WCAG references, and your recommendations.
What Should the Audit Report Look Like?
A clear audit report has a consistent row structure. Each row identifies one issue, the page or screen where it appears, the relevant WCAG criterion, a severity rating, a description, and a recommendation for remediation.
Avoid pasting raw scan output. Scans only flag approximately 25% of issues, and a portfolio built around automated output signals that you have not done the hands-on work. Show the analysis a human auditor produces.
Include at least one screenshot per major issue type to demonstrate that you can document visual context clearly. Screenshots also help developers understand what to fix.
Document Your Methodology
A methodology page tells potential clients how you work. It should cover the standard you evaluate against (most commonly WCAG 2.1 AA or WCAG 2.2 AA), the environments you cover (desktop, mobile web, native apps), the assistive technologies you use, and how you structure deliverables.
Name the screen readers you evaluate with. NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android are the standard set. Listing them signals technical fluency.
Explain how scans fit into your process. Scans help surface obvious issues quickly, but the audit itself is a human evaluation against every applicable success criterion.
Show Credentials and Training
Credentials build trust quickly. The most recognized certifications in the field include CPACC and WAS from the IAAP, and DHS Trusted Tester for government-adjacent work. Listing completed training programs, even uncertified ones, adds depth.
If you are early in your career and do not yet hold a certification, list the WCAG criteria you have studied and the resources you have completed. Honest framing of where you are in your development reads better than vague claims.
Add Short Case Studies
Case studies give a portfolio shape. A good case study is two or three paragraphs covering the scope of the audit, the categories of issues identified, and what happened after the report was delivered. If you supported remediation or validation, mention that.
You do not need to name the client. “A regional ecommerce retailer with a 40-page Shopify storefront” tells a prospective client everything they need to assess relevance.
How Should You Present the Portfolio?
A simple website with five or six pages is enough. Home, services, methodology, sample reports, credentials, and contact. Each page should load fast, meet WCAG 2.1 AA itself, and avoid stock imagery that signals templated work.
Your own site is the most-evaluated asset in your portfolio. Prospective clients will run it through a checker before they read a word. An auditor whose own site has obvious issues loses credibility immediately.
PDF versions of audit samples should be tagged and navigable with a screen reader. A poorly tagged PDF in a portfolio about accessibility is a signal that ends conversations.
Connect Audits to Outcomes
The most persuasive portfolios connect audit work to outcomes the client cares about: reduced legal exposure, faster remediation, WCAG conformance documented in an ACR, or a completed VPAT for a procurement cycle.
If your audit fed into a VPAT or an Accessibility Conformance Report, say so. Procurement teams searching for an auditor often need someone who understands both the evaluation and the documentation that follows.
Frequently Asked Questions
How many audit samples do I need to land my first paid client?
Two redacted samples are enough if the writing is clear and the WCAG references are correct. Quality matters more than volume. A single excellent sample paired with a strong methodology page often converts better than five mediocre ones.
Can I include audits I conducted as part of a full-time job?
Only with written permission from the employer. Most employment agreements treat audit work as confidential. Ask before including anything, and redact thoroughly even when you have approval.
Should I show pricing on my portfolio site?
Listing starting prices or a price range can pre-qualify leads and reduce wasted calls. Auditors who prefer custom quoting often list scope factors instead: number of pages, environments, and the standard being evaluated against.
Do I need a portfolio if I plan to subcontract to larger firms?
Yes. Agencies and consultancies vet subcontractors with the same scrutiny direct clients use. A clean portfolio with sample reports and credentials shortens the conversation significantly.
What is the most common mistake auditors make with their portfolios?
Treating the portfolio as a resume instead of a work sample collection. Clients are not hiring a person, they are hiring a deliverable. The portfolio needs to show the deliverable.
A portfolio that shows real audit work, clear methodology, and connected outcomes will move you past the auditors who only list skills. Build it the way you would build an audit report: structured, specific, and useful to the person reading it.
Want to be found by clients looking for accessibility auditors? Contact Accessibility Base to list your profile in the directory.