Documentation
Send issues to your developer
Email the issues in To fix to your developer or web designer – with step-by-step guides and the exact code, and no allyWay account needed on their side.
Updated October 27, 2026
Someone else looks after your website? Send them the issues that need a change there. They get one email with what to change, why and where – including the exact code – and need no allyWay account.
Before you start
- A running free trial or an active plan.
- Your developer's email address.
Send every issue in To fix
Open To fix
In the left menu, click Report, then the To fix tab.
Click Send to developer
At the end of To fix on your website, click Send to developer ›. The window Send to developer says what it sends, for example "We email your developer all 7 issues with step-by-step guides."
Enter the address
Under Developer email, type your developer's address, for example dev@agency.com.
Send the email
Click Send. You see "Sent to dev@agency.com."
To send just one issue, click View next to it, then Send to developer at the bottom of its panel. The window then says "We email your developer this issue with a step-by-step guide."
What your developer receives
One email with the subject "[allyWay] Accessibility fixes for shop.com". It says that you asked for these fixes – naming your account's email address – and that you can check each fix with one click in allyWay once they're done. Replies go to your account's email address.
For each issue, the email shows its title, WCAG criterion and rule, how many places it has, why it matters and the steps under "How to fix". Under "Where" come each place's page, the element's exact code and a short technical note – for text that's hard to read also a suggested text color, and, where allyWay's AI wrote them, steps for exactly that place under "How to fix this one". A place only phones show says "Only on phones: open the page on a phone, or in a browser window about 390 pixels wide."
The email is in English.
What the email leaves out
Places the AI fixes – for example image descriptions and names for screen readers – and places waiting for your OK in To approve (AI fixes you changed back, visible changes allyWay suggests) aren't your developer's job, so they're left out. Places of a visible change you chose not to make with Don’t change are included. Places you hid or that are already fixed aren't sent.
30 issues per email, 10 emails a day
One email carries up to 30 issues. Issues you haven't sent yet go first, in the order To fix lists them – issues with new places first, then the most serious. With more than 30, the window says so: "We email your developer 30 of your 32 issues with step-by-step guides – the others with the next email."
Issues you sent before are left out while others still wait – "We email your developer the 2 issues you haven’t sent yet, with step-by-step guides." Once every issue has been sent, sending again repeats them – with more than 30, the 30 most important.
You can send up to 10 of these emails a day – for your whole account, not per website, and the day counts in UTC. An email uses one of them however many issues it carries. Installation emails have their own limit – see Send the installation code to your developer.
Check that it works
After sending you see "Sent to dev@agency.com." Sending doesn't change anything on your website: the issues stay in To fix, and each one's panel says "You sent this to dev@agency.com." while places are still open.
When your developer is done, click Mark as done next to the issue for a free check of its pages – or wait for the next automatic check. See Mark issues as done.
During the free trial
allyWay fixes nothing during the trial, so every open place goes into the email. You send one issue at a time: click it in All issues, then Send to developer. Enter the address under Developer’s email – What we’ll send shows the issue and its places – and click Send.
Troubleshooting
- "Enter an email address, for example dev@agency.com." or "Enter a valid email address." Check the address for typos.
- "You have sent many emails today. Please try again tomorrow." You reached 10 emails today.
- "Sending fixes to your developer needs an active plan. Choose a plan to continue." Your trial or plan isn't active.
- "These issues aren’t open any more, so there’s nothing to send." They were fixed or hidden in the meantime, or only have places the AI takes care of or that wait for your OK.
- "The email could not be sent. Please try again." Try again in a moment.
Why does the email list only some places of an issue?
Each issue lists up to 10 places, the most widespread first, and says how many there are in total – "10 of 25 places". In very long emails, code is shortened and fewer places are listed. Your developer can fix the rest the same way; the next checks show what's left.
What about issues found after I sent the email?
They appear in To fix with New behind their title. Issues you haven't sent yet go first in your next email.