Accessibility audits
These lenses are not a certificate or legal opinion. They describe where automated scans and quick manual checks usually concentrate for e-commerce, government, and small-business sites—so you know what to scan first and which issue guides to open next.
- Pick the lens that matches your site type.
- Scan a few representative URLs (see each card).
- Open matching issue pages and guides from the lens page.
- Fix, deploy, and rescan the same URLs to compare reports.
Run a free scan
Start with any public URL from the cards below, then open the lens that fits your property.
- E-commerce accessibility audit
Stores combine templates, apps, promotions, and checkout flows. Small accessibility mistakes repeat across thousands of URLs—so we prioritize templates, navigation, and money paths first.
Who it is for: E-commerce teams, storefront developers, and anyone responsible for checkout and product templates.
Key risk areas
- Product media and quick-view modals
- Cart drawers and checkout steps
- Sale badges, timers, and low-contrast UI
- Third-party apps injecting buttons or overlays
Example pages to scan first
- Homepage and main navigation
- One high-traffic collection or category page
- A best-selling product detail page
- Cart and first checkout step (public URLs only)
- Government website accessibility audit
Citizens expect to complete tasks without assistance: paying bills, finding office hours, downloading forms, and understanding eligibility. Clarity and robust forms matter as much as visual design.
Who it is for: Public-sector content owners, service designers, and developers shipping citizen-facing flows.
Key risk areas
- Complex navigation and mega-menus
- Long forms and eligibility wizards
- Linked PDFs and downloads
- Emergency or alert banners
Example pages to scan first
- Homepage and top tasks from analytics
- One high-volume service or transaction page
- Site search results page
- Contact or feedback form
- Small business website accessibility audit
Most small businesses run on a handful of templates. Fixing the header, footer, form, and hero components once improves every page that reuses them.
Who it is for: Small teams without a dedicated accessibility specialist—site owners, freelancers, and light-touch dev shops.
Key risk areas
- Contact and lead-capture forms
- Hero images and marketing sections
- Headers with many links and social icons
- Embedded maps, chat widgets, and trackers
Example pages to scan first
- Homepage
- Primary service or pricing page
- Contact or booking form
- Blog or news index (if you publish often)