Accessibility statement

Last updated: 2026-04-29

Skolkoll is responsible for this website. We want as many people as possible to be able to use skolkoll.se. This statement describes how Skolkoll meets WCAG 2.1 level AA, what accessibility issues exist, and how you can report problems to us so we can fix them.

Skolkoll is a private operator that targets, among others, the Swedish public sector (municipal licences for school data). We therefore apply the requirements in EU Directive 2016/2102 (the Web Accessibility Directive) and Sweden's Act (2018:1937) on the accessibility of digital public services as if they applied in full.

1. How accessible is the website?

We are aware that parts of the website are not fully accessible. Skolkoll is partially compliant with the Swedish Web Accessibility Act. The issues that exist are described in section 2 below.

The assessment was made on 2026-04-29 against WCAG 2.1 level AA. 18 issues have been identified — 7 serious (P1), 5 substantial (P2) and 6 minor (P3). All are scheduled for remediation within epic #1975.

2. Content that is not accessible

The content below is not fully accessible in various ways. Issues are grouped per WCAG criterion with a reference to the sub-issue tracking the fix.

2.1 Perceivable

1.1.1 Non-text Content (level A)

• County coat-of-arms images at SEO links lack a fallback name. The home page renders county arms as decorative images next to text. If the manifest data ever omits the county name, the link becomes nameless. Planned fix: #2226. (Severity: P2)
• Logo suffix duplicated for screen readers. The "Skolkoll" logo is followed by a hidden sr-only string "— Search and compare Sweden's schools". Screen readers read the whole string, often duplicating the page title. Minor, not an AA blocker. (Severity: P3)

1.3.1 Info and Relationships (level A)

• Sortable table columns lack aria-sort. Screen readers cannot announce the current sort state in the home-page result table. Planned fix: #2221. (Severity: P1)
• Status select elements lack aria-busy during data fetch. The "Status" and "School type" filters on the home page only show "All" until JavaScript populates them. Users on slow connections get no indication that the field is being populated. Planned fix: #2226. (Severity: P2)
• Two <header> elements on the home page. The hero section is rendered as <header> inside <main> while the sticky header sits outside. Screen readers handle both but the structure is ambiguous. Planned remediation within epic #1975. (Severity: P2)

1.4.1 Use of Color (level A)

• Map uses a red–green scale for metric colouring. Markers in the home-page map's metric mode go from red to green via yellow. This discriminates against users with red–green colour-blindness (deuteranopia/protanopia). Planned fix: switch to a colour-blind-safe palette (viridis/cividis) in #2223. (Severity: P1)
• Status indication on map is colour-only. ACTIVE/DORMANT/CLOSED status is shown via green/orange/red without a text label. Needs a complementary text label or pattern. Planned fix: #2223. (Severity: P1)

1.4.10 Reflow (level AA)

• Hero nav ignores prefers-reduced-motion for smooth scroll. The horizontal scroll affordance in the hero nav is intentional and does not break 1.4.10 (page content does not require horizontal scroll), but scrollIntoView({ behavior: "smooth" }) does not respect the user's reduced-motion preference. Minor polish. (Severity: P3)

1.4.11 Non-text Contrast (level AA)

• Search clear icon (×) has too low contrast. The icon is rendered in semi-transparent white on a semi-transparent white pill background — below the WCAG 1.4.11 threshold of 3:1 for UI components. Planned fix: #2226. (Severity: P2)

1.4.12 Text Spacing (level AA)

• Chip buttons in hero may be truncated at 200% text spacing. The chips' fixed height and padding may clip text when users increase line-height per WCAG 1.4.12. Needs manual verification. Planned polish. (Severity: P3)

2.2 Operable

2.4.3 Focus Order (level A)

• Cookie banner steals initial focus without restoring. The banner moves focus to its first button on first visit, but after accept/reject focus is not restored to the previously focused element. Users who had already started tabbing experience disruptive focus jumps. Planned fix: #2224. (Severity: P1)

2.5.5 Target Size (level AAA)

• Search clear button is ~31×31 px. Passes WCAG 2.2 AA (24×24 px) but is below the AAA threshold of 44×44 px. This audit explicitly targets AA, so this is not an AA blocker — kept as polish for a possible AAA upgrade. (Severity: P3)

2.3 Understandable

3.1.2 Language of Parts (level AA)

• English programme names on Swedish school pages lack lang="en". Terms such as "International Baccalaureate" are rendered inside Swedish prose without a language tag, which can cause incorrect pronunciation in screen readers. Planned fix: #2226. (Severity: P1)

3.1.5 Reading Level (level AAA)

• Text on the home page is at Swedish B1–B2 level. AAA requires text to be understandable at lower secondary level (plain-language). The site targets AA — plain-language work is tracked separately (#1380). Not an AA blocker. (Severity: P3)

3.3.3 Error Suggestion (level AAA)

• The wizard form lacks inline validation. Users can click "Show results" without setting any criterion and then receive an empty result. Not an AA blocker. (Severity: P3)

2.4 Robust

4.1.2 Name, Role, Value (level A)

• <div role="button"> on #table-tools-toggle instead of native <button>. Technically correct with working Enter/Space handlers and aria-expanded, but a native element provides free IME focus and context menus. Planned fix: switch to native <button type="button"> in #2225. (Severity: P1)
• Sticky header uses data-visible="false" instead of inert/hidden. When invisible, its links remain in tab order and screen readers hear both navigations. Planned fix: #2224. (Severity: P2)

4.1.3 Status Messages (level AA)

• aria-live region announces too aggressively during search. The KPI summary on the home page has aria-live="polite" that announces every updated value — can feel like "spam" during fast typing. Planned fix: debouncing of aria-live updates in #2225. (Severity: P1)

3. Disproportionate burden

Skolkoll does not invoke disproportionate burden under section 12 of the Act (2018:1937) for any part of this website. All identified issues are scheduled for remediation within a reasonable timeframe via tracked sub-issues in epic #1975.

4. Content not covered by the law

The following content on skolkoll.se is not covered by the requirements of the Act on the accessibility of digital public services:

• Third-party content outside our control. The open APIs from Skolverket, SCB, Bolagsverket and Skolinspektionen deliver text and documents whose layout we cannot control. When such content is embedded (e.g. document lists from Skolverket), accessibility issues in the source material may occur. This is exempted under Article 1.4(b) of the Web Accessibility Directive (third-party content not funded or developed by us).
• Embedded maps (Leaflet/OpenStreetMap) for non-navigational purposes. The map on the home page is a complement to the searchable table. The table is the primary entry point for keyboard users. School markers in the map are now keyboard-reachable, but online maps are explicitly exempted in Article 1.4(c) of the Directive and we apply the exemption restrictively.
• Third-party libraries from CDN. D3.js and Leaflet are loaded from unpkg.com. Any accessibility issues in the libraries' own components (e.g. Leaflet's default controls) are outside our codebase but are documented and reported to the respective maintainers.

5. How we tested the website

This accessibility statement is based on:

• Self-assessment via manual code review against the WCAG 2.1 AA success-criteria checklist. The review was carried out in April 2026 by the platform team and is documented in docs/audits/a11y-2026-04.md in our open-source repository.
• Scope of the review covers: home page, school page, municipality page, comparison view, hero navigation, Leaflet map, cookie banner, and embeddable widgets.
• Review process: Five review rounds with adversarial methodology (parallel reviewers + sceptical verification + final arbitration) — see docs/audits/a11y-audit-methodology.md.
• Ongoing work: Automated regression testing via Lighthouse a11y and Pa11y in CI is planned in #2227. Manual screen-reader testing (NVDA + VoiceOver) on top-5 user journeys is tracked in #2229.

The assessment was made on 2026-04-29. The website was published before 23 September 2018, and this statement is updated after every major accessibility remediation and at least annually.

6. Contact and feedback

We want to know if you find accessibility issues on skolkoll.se so we can fix them. You can also request information in another format if you need it — for example a printable version or text without tables.

Contact us:

• Email: info@skolkoll.se
• Write "Accessibility" in the subject line and the message will be routed directly to the right person.

We aim to respond within 14 days. If we need more time to resolve an issue we will inform you of a preliminary timeline.

7. Enforcement procedure

The Swedish Agency for Digital Government (DiGG) is responsible for supervision of the Act on the accessibility of digital public services. If you are not satisfied with how we handle your feedback, or if you have complaints about how the website complies with the law, you can report it to DiGG.

Report an accessibility issue to DiGG: digg.se/tdosanmalan (Swedish form).

8. Last updated

This statement was last updated on 2026-04-29. The website was last reviewed on 2026-04-29 through self-assessment. The next planned review will take place when the remaining issues in epic #1975 have been remediated, and at the latest by 2027-04-29.