1. Check the page or design
Mona reviews the page in a browser with automated checks and by hand: color contrast, text alternatives, heading order, keyboard focus, form labels and zoom. Figma designs can be checked before they are built.
Fix accessibility issues
Mona checks your pages and designs for common accessibility problems, such as contrast, alt text, focus and headings, and fixes them in a reviewable pull request or design file.
accessibility
Example brief · Hypothetical workflow
Your brief
Check our new signup form for accessibility problems and fix what you can in the repo. Tell me what needs a decision from design.
MonaAPP
I’ll test the page with automated checks and by hand, fix the clear issues and list the ones that need a design decision.
See example output ↓How Mona handles it.
Starts: When you ask for a review of a page, design or release, or before a launch.
2. Fix what is clear
Clear fixes, such as missing alt text, low-contrast text or unlabeled buttons, go into a draft pull request prepared with connected Claude Code or Codex and GitHub, with focused checks, or, with Figma edit access, into the Figma file. Changes that alter the design are proposed with options.
3. Report what remains
You get a list of issues found, fixed and still open, each with where it appears and the WCAG success criterion it relates to. The review covers what was tested; it is not an accessibility certification or a legal audit.
Fixes you can see and review.
This is a practical review-and-fix pass. Full conformance audits, testing with assistive-technology users and legal sign-off remain separate.
Hypothetical finished result
Example output
Signup form accessibility pass
Hypothetical: a newly launched signup form reviewed at desktop and mobile sizes.
- Fixed
- The email and password fields had placeholder text but no labels, so visible labels were added. Error messages now name the field and are announced to screen readers. The hint text measured 3.1:1 contrast and was darkened to meet 4.5:1. All three changes are in one draft pull request.
- Needs a decision
- The password rules appear only after a failed attempt. Two options are proposed for the designer: show the rules under the field, or check them as the person types.
- Not covered
- Testing with screen-reader users and the email-verification step were outside this pass and are listed as next steps.
The apps this job needs.
Connect the accounts and actions for your workflow. Start in Artie or add your Artisan to Slack; access stays within your account permissions.
Explore apps- Browser
- Mona reviews public pages in a browser. Provide access to any staging or signed-in pages you want included.
- GitHub and Claude Code or Codex
- Connect the website repository and a coding tool, and allow draft pull requests for fixes. Your reviewers merge.
- Figma (optional)
- Share the design files you want checked before they are built. Corrections need edit access through the Figma app or a signed-in browser session; comment access alone only adds notes.
Questions about this workflow
Does this make our site compliant?
No single review can certify compliance. Mona finds and fixes issues within what was tested and lists what was not covered.
Is it automated checks only?
No. Automated tools catch some issues; Mona also checks by hand, including keyboard navigation and reading order.
Who merges the fixes?
Your team. Code changes arrive as draft pull requests for your reviewers.