Developer briefs
Some problems belong in your theme, not in a runtime fix. For any issue, “Explain this to my developer” produces a short brief in plain English with the corrected snippet, ready to paste into a ticket.
- One brief per issue, on request
- Corrected snippet included
- Ten a month on Free
Why it matters
For the fixes that belong in your theme.
The corrected snippet, not a lecture
The brief shows the code as it should be, with the value that is wrong and the value it needs. No criterion numbers to look up.
One brief per issue
Any finding can produce its own brief, so you can hand over three specific tasks instead of a 40-page audit nobody reads.
Says why, briefly
Two lines of context: what the rule requires and what the current value measures. Enough for a developer to agree or push back.
Written to be forwarded
Paste it into a ticket or an email. It assumes a developer reading it, not an accessibility specialist.
Still plain about the problem
The problem statement stays in the same plain language as the rest of the dashboard, so you and your developer are reading the same sentence.
For what we will not touch
Some fixes need a structural change, and those are exactly the ones we refuse to apply automatically. A brief is the honest handoff.
How it works
Three steps, no vocabulary to learn.
Pick an issue the runtime fix should not handle
A heading order, a component that needs restructuring, a pattern repeated across a template.
Ask for the brief
You get what is wrong, why it matters to a real user, and the corrected code for that element. Written for the developer, readable by you.
Hand it over
Paste it into a ticket or an email. When the change ships, the next scan and verification record the improvement.
Turn a finding into a ticket.
Run the free check first — you may find most of it needs no developer at all.
When a fix needs a person.
Most findings can be fixed from the dashboard. The ones that cannot are where a brief earns its place.
The snippet, and the number that is wrong.
A contrast failure becomes a measured ratio and a corrected colour. A missing name becomes the attribute to add. It is short on purpose.
- Corrected code, ready to paste
- The measured value and the required one
- One brief per finding
Most things never reach your developer.
Attributes and CSS are handled in the dashboard, approved by you. A brief is generated for the remainder, which is a much shorter list than people expect.
- Approve routine fixes yourself
- Briefs only for what needs code
- Attributes and CSS only, either way
You and your developer read the same sentence.
The dashboard does not translate a problem into jargon before passing it on. The brief adds the code; the description of what is wrong stays identical.
- No criterion numbers to decode
- One description, two audiences
- Nothing lost in the handoff
Frequently asked questions
About developer briefs. The product-wide questions are on the features page.
Is the code in a brief tested?
It is a corrected snippet for the element the scan found, generated with the page’s context. Your developer applies it and the next scan verifies the result on the live page.
Do I need a developer at all?
Not for most findings; those are handled by one-click fixes. Briefs are for the minority that belong in code.
Start fixing your site today. Free.
Five pages, every problem ranked by risk, in plain English — before a lawsuit-hunting scan finds them first.
- Free 5-page check
- No credit card
- 14-day money-back guarantee