- role
- textbox
- name
- (none)
- state
- none
"Edit text, blank."
The word Email sits next to the field but is not tied to it, so the field has no name.
Accessibility problems fixed, not just reported
From audit report to working code: colour contrast, form labels, keyboard access, focus order, ARIA and document fixes in your theme or templates, retested after. €95 an hour or a fixed price per batch.
Pick an issue on the left, then switch between Broken and Fixed. The announcement is what a screen reader user hears.
Screen-reader wording is approximate and varies by screen reader and browser. Work happens in WordPress, WooCommerce, Shopify, Magento, OpenCart and custom PHP themes.
A fix backlog, one card per finding
Every audit finding becomes a card with a severity, a criterion and an hour estimate. You see what is open, what it costs and what is already retested. Try it: no dragging needed.
Critical5 h
- Checkout fields have no labels
- Delivery picker traps keyboard focus
Serious4.5 h
- Focus outline removed in the theme
- Colour swatches have no names
- Cart update is not announced
Moderate3.5 h
- Footer link contrast 3.1:1
- Size guide PDF is untagged
- Cookie banner hides focused links
Done0.5 h
- Skip link to main content added
Sample backlog for an example store. Mark cards fixed to see the open effort and cost change.
From report to retest
Your report, whoever wrote it. Work happens on staging or in a branch of your repository, never straight on the live checkout.
- 1
Send the report
Any format: an audit PDF, a spreadsheet, an automated tool export or a list of complaints.
- 2
Reproduce
Each finding checked on the current site, with an hour estimate per card and anything I disagree with flagged.
- 3
Fix in staging
Changes in the theme, templates or components, so one fix repairs every page that uses them.
- 4
Retest
The same method that found it: keyboard, NVDA or VoiceOver, contrast measurement, zoom.
- 5
Hand over
A changelog in plain language and the list of updates for your accessibility statement.
What I fix
The issues audits find most, fixed at the source. Criterion numbers from WCAG 2.2, so your auditor can check the work.
Colour contrast
Text to 4.5:1, controls and icons to 3:1, changed once in the theme's colour tokens rather than page by page. 1.4.3 1.4.11
Form labels and errors
Visible labels tied to fields, the right autocomplete, and error text that names the problem and is announced. 1.3.1 3.3.1 3.3.2
Keyboard access
Menus, filters, modals and sliders usable without a mouse, with no keyboard traps in checkout or cookie banners. 2.1.1 2.1.2
Focus order and visibility
A focus ring you can see, an order that follows the page, and sticky bars that never hide the focused element. 2.4.3 2.4.7 2.4.11
ARIA and names
Wrong ARIA removed before any is added, icon buttons named, status messages announced without moving focus. 4.1.2 4.1.3
Documents
Terms, invoices and guides as tagged PDFs with a reading order, or better, as plain HTML pages. 1.3.1 1.3.2
Have a report already? Send it and get a fixed price for the first batch.
Get a fix quoteWhen I would not recommend fixing
Fixing is the right step most of the time. These are the exceptions I will tell you about before you pay.
- 01The site is being replaced within months. Spend the budget on building the new one accessible, on the websites route, and test it before launch.
- 02The issue lives in a third-party widget or hosted checkout you cannot change. I document it and help you ask the vendor, rather than bill hours for a workaround that breaks on their next update.
- 03You want an overlay script to cover it. I do not install them: an overlay does not change the code that fails, and it can get in the way of the assistive technology people already use.
Hourly or a fixed batch
Prices in euros, excluding VAT 25.5%. Both include the retest and the changelog. You own the code and every account.
Hourly
A handful of issues, or fixes alongside your own developer.
- Hour estimate before work starts
- Billed for hours worked
- Out-of-hours work plus 50%
Fixed batch
A group of cards, such as everything Critical, at one agreed price.
- Built from the card estimates
- Retest of every card in the batch
- Statement update list
If a fix fails the retest, I rework it before the batch is closed, at no extra charge. owner to confirm
Questions about fixes
Can you fix issues from someone else's audit?
Yes. Send the report in any format, from an automated tool export to a full consultancy PDF. I first check that each finding still reproduces on your current site, flag anything I disagree with and why, then quote the batch. You do not need to buy a new audit before the fixes start.
How long do fixes take?
It depends on where the issue lives. A template fix, such as a missing focus style or unlabelled checkout fields, repairs every page that uses the template at once. Content fixes, such as alt text or PDFs, grow with the number of items. Every card in your batch gets an hour estimate before work starts.
Do you retest afterwards?
Yes, always. Each fix is retested with the method that found it: keyboard, a screen reader such as NVDA or VoiceOver, contrast measurement or zoom. You get a short retest note per issue with before and after, plus an updated list for your accessibility statement. Anything still failing stays open.
Get a fix quote
Tell me where the report is, or paste the issues you know about. You get a written estimate and a fixed batch price within one working day.
No report yet? Start with an accessibility audit, or use the contact page for anything else.
Prefer email? Write to [email protected]
Pikselipolku is an independent studio and is not affiliated with WordPress, WooCommerce, Shopify, Magento, OpenCart, NVDA, VoiceOver or any other product named here.