Support

Contact the developer

Email hello@andrewkennedydev.com ↗ for AAAudits Pro support or privacy questions. The developer is Andrew Kennedy.

Include your app version/build, macOS version, Mac model, edition (free demo, Mac App Store or older direct download), the steps you took and what you expected. Share a minimal synthetic example where possible. Do not send passwords, session cookies, authentication tokens or customer data.

Screenshots and reports can contain confidential website content. Review and redact attachments before sending them. Support correspondence is deleted within six months after an enquiry closes, unless needed for an ongoing issue or a legal obligation.

Start with the free demo

Download AAAudits Pro Demo 1.0.0 ↗, open the disk image and drag AAAudits Pro Demo into Applications. The demo allows up to 25 unique pages from one website per audit, shared across desktop and narrow captures. Automated testing, Bug Finder and the interactive Test lab are disabled. These controls being unavailable in the demo is expected.

The full paid Mac App Store edition is currently in review. It supports up to 100 pages per audit and the full testing tools.

AAAudits Pro requires an Apple silicon Mac and macOS 26 or later. Intel Macs are not supported.

Choose Try the local demo on the welcome screen to explore a fictional website with intentional issues. Then create a project, enter a site you are authorised to test, choose a WCAG target and sample, and start the audit.

The Mac App Store edition uses built-in WebKit. The separate direct edition can offer installed-browser integrations; those are not part of the Store edition.

A website will not load or an audit is blocked

Check that the address is correct and the website opens normally. Network restrictions, TLS problems, login requirements, anti-bot challenges and server failures can prevent inspection. A restricted or unverified response is not automatically a broken link.

Try a smaller sample and one project at a time. For an authenticated site, use the supported Test login flow with a dedicated test account and synthetic data. Do not bypass access controls.

Test login does not complete

Enter credentials again after reopening the app: they are held in memory for the app session and are not saved as project/report credentials. Check the same-origin login URL, field selectors, submit selector and a marker that is visible only when signed in.

The supported flow handles compatible same-origin forms. MFA, CAPTCHA, external single sign-on and HTTP Basic login are not automated. Use an authorised disposable test environment; do not share production credentials with support.

The audit takes longer than expected

Performance repeats are additional page loads. A larger page sample, two viewports and several repeats can take substantially longer than the initial crawl. Live counters identify the current work; phase estimates are provisional.

Reduce the sample size or performance repeats, or disable repeat measurement for an initial investigation. Use Cancel if needed. An interrupted audit may offer explicit Resume or Retry from start; recovery is not a restoration of the website’s server state.

Understanding scores and unknown results

The quality score covers implemented rules only. Read it alongside captured scope, unresolved occurrences and manual-review coverage. A high score does not establish full-site accessibility or legal compliance.

Complex contrast or inaccessible content may need review. Narrow browser views check responsive layouts on the Mac, not physical iPhone/Android behaviour. Local timing observations are not field-user performance data and do not include INP.

Replay or video recording is unavailable

The interactive Test lab and automated testing are not available in the free demo. The following guidance applies to editions that include these tools.

Live replay supports a bounded set of browser actions. Unsupported actions and data entry require participation. Use explicit assertions; finishing replay alone does not establish a passing test.

Recording requires macOS Screen & System Audio Recording permission. Check System Settings → Privacy & Security, allow the installed app when prompted, and reopen it if required by macOS. Recording is optional; an ordinary audit does not require screen-video permission.

Exports, missing evidence and data management

Choose a writable destination and check available disk space. Some screenshots and measurements may be unavailable; review the disclosed scope and failure notes. HTML provides a semantic alternative to the PDF report.

Deleting a project in the app removes its associated local records, evidence and recovery data. Exported reports, sent files and independent backups remain separate. Saved test cases and Bug Finder sessions can be removed from their own workspaces.

Updates and edition changes

The Mac App Store edition receives updates through Apple. The free demo is a separate application; download its latest version from this website. Older direct editions have a separate release workflow.

The Store edition has its own application container. Its project library is separate from the direct-download edition. Back up/export important work before changing editions; do not assume automatic project migration.