Skip to main content
KungoraKungora

Accessibility Statement

Version 1.1.0, in force from 8 October 2026

This is an earlier version and no longer in force. Read the version in force

1. About this statement

Puraderi AB is behind Kungora. We want as many people as possible to be able to use the service. This statement describes how Kungora meets accessibility requirements, which known shortcomings there are and how you can report problems so that we can fix them.

The statement applies to

  1. the public website kungora.com with the news portal, subject and region pages and the pages with terms;
  2. newsrooms, on our domain, on subdomains we provide and on organisations’ own domains;
  3. widgets and feeds that organisations embed on their websites;
  4. the sign-in and the account for organisations and journalists; and
  5. email sent through the service.

2. How accessible is the service?

We aim for the service to meet level AA of the Web Content Accessibility Guidelines (WCAG) 2.2 and the EN 301 549 standard. We consider the service partially compliant, because of the shortcomings described in clause 3. The assessment is based on our own review, described in clause 8. No external audit has been carried out.

3. Content that is not accessible

3.1 Content published by organisations

The content of the newsrooms is published by the organisations themselves. We require alternative text for images, but we cannot check that the text describes the image well. Documents uploaded by organisations, for example PDF files, may lack the structure that makes them readable with screen readers. Video and audio embedded by organisations may lack captions, audio description or a text version.

3.2 Embedded players

Video and audio players are fetched from YouTube, Vimeo, Dailymotion and SoundCloud only when you play them. Until then we show a panel with a play button and a note saying where the player is fetched from. Without JavaScript the panel is a link that opens the player’s own page at the provider. Once the player has been fetched, its accessibility is controlled by the providers. On the media page of a video we also show a link to the provider’s own page next to the player.

3.3 Known shortcomings in the service

These are the shortcomings we know of, each with its WCAG 2.2 criterion. The list is updated when we find or fix a shortcoming.

  1. The data processing agreement as PDF (dpa.pdf) is not tagged for screen readers (WCAG 1.3.1; EN 301 549 chapter 10). The same text is available as a web page in the legal documents.

4. Organisations covered by legal requirements

Public sector bodies that use a newsroom in Kungora are covered by the Swedish Act (2018:1937) on the accessibility of digital public services and are responsible for their newsroom and content meeting the requirements, and for publishing their own accessibility statement. The service helps them do so: alternative text is required for images, and headings, lists and tables get the right structure.

5. If you cannot access content

If you need content from Kungora that is not accessible to you but is covered by the service, you can email hello@kungora.com. If it concerns an organisation’s publication, we pass your request on to the organisation. We answer within five working days.

6. Reporting shortcomings

We are always working to improve accessibility. If you find problems not described here, or you think we do not meet the requirements, email hello@kungora.com so that we know the problem exists.

7. Supervision

The Swedish Agency for Digital Government (Myndigheten för digital förvaltning, Digg) supervises the Act on the accessibility of digital public services. The Act applies to public sector bodies. If you think that a public sector body’s newsroom in our service does not meet the requirements of the Act, or you are not satisfied with how a public sector body has handled your comments, you can report it to Digg.

8. How we tested the service

  1. Automated accessibility tests (axe) run before a new version of the service is deployed and every week, in Swedish and English, for pages in their initial state, after invalid input and at a screen width of 320 pixels. A version that causes errors is not deployed.
  2. The automated tests also check that focus lands correctly and that buttons and links can be reached with the keyboard.
  3. Every week the public pages are also crawled with the pa11y tool.
  4. Email is tested automatically in Swedish and English.

9. Date of this statement

The assessment was last made on 8 October 2026. This statement was last updated on 8 October 2026.

Every version stays published. The newest comes first.

  1. Version 1.2.0 · in force

    The statement now fits a service open to organisations in the EU and EEA: it names the EU accessibility rules (the Web Accessibility Directive and the European Accessibility Act) next to WCAG 2.2 and EN 301 549 (2), says that public sector bodies in other countries are covered by their own country’s law (4) and says where to turn outside Sweden (7). It still describes only the review we actually do; no external audit has been carried out. It also says that the automated tests run on the Swedish and English pages and that the Danish, Finnish and Norwegian pages, which use the same templates, are not tested separately (8). Approved by Puraderi AB.

    Show the changes from version 1.1.0 to 1.2.0

  2. Version 1.1.0 · in force from 8 October 2026

    The statement describes only the review we actually do (automated tests with axe and pa11y, also at 320 pixels, before each deployment and every week) and now has dates; the external audit and the regular screen-reader testing it mentioned have not been done and are no longer listed. Approved by Puraderi AB.

    Show the changes from version 1.0.0 to 1.1.0

  3. Version 1.0.0 · in force from 8 October 2026

    First approved version. Puraderi AB approved the text. It is the same as draft 0.3.1, without the draft notice.

SHA-256 of the text: 464500b56885f7a3ab9e9cd297228ea9b0eadb7688c0268c2805a7ef24b3b8d1

Version 1.1.0 as JSON