accessibility compliance
The web has rules now. We make sure you pass.
WCAG 2.1 AA audits, fixes and monitoring for businesses in Cyprus and across the EU.
The law
The European Accessibility Act (Directive 2019/882) has applied since 28 June 2025. It requires many businesses' digital products and services to be accessible, and in practice that is generally measured against WCAG 2.1 AA, the same standard we build to.
Whether it applies to you is a different question. It depends on your size, your sector, and how your member state transposed the directive into national law; micro-enterprises may be treated differently, and the detail is not identical across the EU. We will tell you honestly whether it affects you, before you commit to anything.
Please note We are developers, not lawyers, and nothing on this page is legal advice. National transposition of the directive varies, and the only way to be certain of your obligations is to check with a qualified adviser in your jurisdiction. What we can do is tell you where your site stands against the technical standard, and fix it.
What we actually do
-
Audit
A full WCAG 2.1 AA review: automated checks plus manual keyboard, screen-reader and zoom testing, because automation alone catches only a fraction of the issues that actually stop people. You get a prioritised report in plain language, not a tool dump.
-
Remediation
We fix what the audit found: code, content, contrast, focus order, structure. Real fixes in the markup, not a plugin overlay dropped on top of it.
-
Monitoring
Sites change. New pages, new content, a new campaign landing page built in a hurry. Ongoing checks so none of it quietly undoes the work you already paid for.
-
Built in from day one
If we build it, it ships accessible. Semantic structure, keyboard paths and contrast are decided while the thing is being designed, which costs almost nothing and means there is no retrofit project waiting for you a year later.
On overlays
You will be offered a widget: one script tag, a little accessibility icon in the corner, compliance solved by Friday. We do not sell those and we would not put one on your site.
Overlays sit on top of the page and try to guess what the underlying code should have said. The markup underneath is unchanged, so the problems are still there for anyone whose own software reaches the page first. Disabled users and accessibility professionals have been vocal about this for years, and it is worth listening to the people who actually use the thing. We would rather fix the code than paint over it.
proof
Audit this page.
This site is built to WCAG 2.1 AA standards: semantic markup, keyboard operable throughout, visible focus, AA contrast, reduced motion respected. Do not take our word for it: open your dev tools and run axe or Lighthouse on this page right now.
- Semantic HTML, one h1, logical heading order
- Every control reachable and operable by keyboard
- Visible focus on everything focusable
- Text contrast measured, not estimated
- prefers-reduced-motion honoured site-wide
- Real labels on every field, no placeholder-only inputs
- No CAPTCHA, no third-party tracker on our forms
- Works, and stays readable, at 200% zoom
Being straight about it: “built to” is not “certified”. There is no certificate for WCAG, and our own full manual audit (keyboard, screen reader, zoom, end to end) is still in progress. When it is done we will publish what it found, including anything it found wrong.
questions
Straight answers
-
Does this apply to my business?
It may. It depends on what you sell, how big you are, and how your member state transposed the directive. Several categories, including micro-enterprises, can be treated differently, and the detail varies country by country.
We are happy to look at your situation and tell you what we think before you commit to anything. If we think it does not apply to you, we will say so. For a definitive answer you should talk to a qualified adviser.
-
What is WCAG 2.1 AA in plain terms?
It is the technical standard most accessibility rules point at. In practice it means the site works without a mouse, works with a screen reader, has text you can actually read against its background, does not rely on colour alone to make a point, stays usable zoomed in to 200%, and does not move in ways that could make someone ill.
AA is the middle of three levels, and the one regulators generally reference.
-
How long does an audit take?
For a typical small business site (a handful of page templates and one or two forms), about a week from access to report. Larger sites, logged-in areas, checkout flows and web apps take longer, because every state has to be tested by hand rather than crawled.
We scope it properly and give you a fixed figure before we start, so the number does not move once we are in.
-
Will you fix it, or just tell me what's wrong?
Either. The audit stands on its own if you have your own developers, and it is written so they can act on it: issue, where it is, what it breaks, how to fix it.
If you would rather we did the work, we fix it in the code and re-test what we changed. There is no obligation to buy the remediation to get the report.
-
Do I need this if my site is new?
New does not mean accessible. Most modern templates and page builders produce markup with the same handful of problems: unlabelled controls, menus you cannot reach with a keyboard, low-contrast placeholder text, focus you cannot see.
A new site is a good moment to check, because fixing it now is far cheaper than rebuilding around it later. And if we build it, this is included rather than sold separately.
get audited
Find out where you stand.
Send us the URL and we'll tell you what we see, and whether any of this applies to you.
Prefer email? info@a-anchortech.com