WeBringCode

Web accessibility

Accessibility that holds when someone uses the service, not just when a tool scans it. We review the interface against WCAG and fix what we find, so the service meets the basic requirements.

The problems sit in keyboard navigation, focus order and what a screen reader reads out. None of it shows up in a screenshot, which is why it stays: nobody finds it until someone tries to use the page without a mouse.

What does the law require?

In Sweden, the public sector has been covered since 2019 by the act on accessibility of digital public services. Since 28 June 2025, the Swedish act based on the European Accessibility Act also covers certain services, including e-commerce, consumer banking and parts of passenger transport. There are exemptions, including for microenterprises that provide services. Digital public services are assessed against the European standard EN 301 549, which builds on WCAG level AA. Services under the accessibility act have further requirements specific to the service, and a WCAG review does not cover the whole law. Start by finding out which law applies to your service. Then you also know what you need to be able to report.

What an automated scan misses

  • Whether a form can be completed with a keyboard alone.
  • Whether focus lands in the right place when a dialog opens and closes.
  • Whether the alt text describes the image or just repeats the file name.
  • Whether error messages reach a screen reader, or only turn into red text.

How a review works

  1. An automated scan first, for what it is good at: missing alt attributes, fields without labels, low contrast.
  2. Then we go through the flows that matter by hand, with a keyboard and a screen reader: the purchase, the sign-in, the application.
  3. Fixes in the component library where the problem sits, so every page that uses the component gets the same fix.
  4. A written record of what was reviewed and what was fixed. If you need a formal audit or a legal assessment of which requirements apply, we recommend a specialist.

Fix page by page and the same problem comes back the next time someone builds something new with the same component. Fix the component and the next page gets it right from the start. Content and new components still need reviewing, but the foundation is fixed. If you are building something new, accessibility is part of system development.

The tool measures what can be measured automatically. Then someone has to put the mouse away and try.

Need help with web accessibility?

CONTACT US >

Need help with integrations, code or a broken system?

Fill in the form or email us at hello@webringcode.com, and we’ll get back to you with how we can help.

Or call us directly on +46 10 660 04 20.

We store what you send so we can reply. Read more in our privacy policy.