Accessibility assessment
Standard: WCAG 2.1 level AA | Date: 7 November 2026 | Scope: all 54 pages of this website
This page reports the results of an accessibility audit of the “Countering Holocaust distortion on social media” website against the Web Content Accessibility Guidelines (WCAG) 2.1, level AA. WCAG 2.1 AA is the technical basis of the European standard EN 301 549 and of the Italian accessibility law (Legge Stanca).
Summary
The site has a good base: it has a skip link, a visible keyboard focus is not removed by the style sheets, the viewport allows zooming, every page has a title and the body text has a high contrast (11.4:1). All three critical problems and all seven major problems found were fixed on 7 November 2026. The only open item is the mobile menu (#18), which, together with the focus indicator (#12), needs manual testing in a browser and with a screen reader.
Method and limits
- Automated static analysis of the HTML of all 54 pages (images, links, headings, landmarks, forms, language, ids, frames) and computation of colour contrast from the site’s style sheets.
- Automated checks find only about 30% of accessibility problems. Not yet done: keyboard-only navigation in a browser, testing with a screen reader (VoiceOver, NVDA), zoom to 200%, the behaviour of the dropdown menu and of the form error messages, and the accessibility of PDF documents and embedded media.
- Findings marked “to verify” must be confirmed with these manual tests. This page is not a formal conformance statement.
Findings
Perceivable
| # | Issue | WCAG | Severity | Recommendation |
|---|---|---|---|---|
| 1 | All 139 images that are the only content of a link (logo, event and post thumbnails) have alt="", so the link has no accessible name. Present on all 54 pages. | 1.1.1, 2.4.4, 4.1.2 | Critical – fixed 7 Nov 2026 | Give each linked image a descriptive alt (e.g. “Home page”, the event title) or an aria-label on the link. Done: logo and thumbnail links now have alt text; duplicate thumbnails next to a title link are hidden from screen readers. |
| 2 | Team and partner photos use the image file name as alt text (e.g. “1157488_10201769780386435_13117050_n”, “Martin_Rehm2”): 21 images on 7 pages. | 1.1.1 | Major – fixed 7 Nov 2026 | Use the person’s name or an empty alt if the name is already in the adjacent text. Done: all team, advisory board and partner images have descriptive alt text. |
| 3 | Footer text is white on #3A8BB6: contrast 3.78:1 at 12 px, and the footer headings (#CCEDE8 on #3A8BB6, 15 px) reach only 3.04:1. Both fail the 4.5:1 requirement for normal text. | 1.4.3 | Major – fixed 7 Nov 2026 | Darken the footer background (≈ #2B6D93 gives ≥ 5.5:1 with white) or use darker link colours. Done: footer background is now #276588 (white 6.36:1, headings 5.10:1) and buttons #2A6A8F (5.90:1). |
| 4 | Brand blue #3A8BB6 on white is 3.78:1. It passes for large text and graphics (3:1) but fails when used for small body text or links. | 1.4.3, 1.4.11 | Minor – fixed 7 Nov 2026 | Use it only for headings ≥ 24 px or bold ≥ 18.5 px, or use a darker blue for text. Done: the brand blue is now #2A6A8F everywhere (5.90:1 on white, 4.6:1 on light green). |
| 5 | The page language is always declared as it-IT, but most pages are in English and 5 are in German. Screen readers will pronounce the text with the wrong voice. | 3.1.1, 3.1.2 | Major – fixed 7 Nov 2026 | Set lang="en" on English pages and lang="de" on the German ones (Italian pages are already correct). Done: 46 pages en, 5 de, 5 it-IT. |
| 6 | Heading text is partly set by the theme with visual line breaks (about<br>the project, 15 headings), which screen readers can read as one run-together word. | 1.3.1 | Minor – fixed 7 Nov 2026 | Replace <br> with a space and control wrapping with CSS. Done: a space was added before each line break, so the accessible name reads “about the project”. |
Operable
| # | Issue | WCAG | Severity | Recommendation |
|---|---|---|---|---|
| 7 | Menu entries “People” and others use href="#" and are announced as links to nowhere. 108 occurrences. | 2.1.1, 4.1.2 | Major – fixed 7 Nov 2026 | Use a <button> with aria-expanded for submenu toggles. Done: the toggles now expose role="button", aria-haspopup and aria-expanded. |
| 8 | 216 footer and logo links point to /?page_id=N (WordPress ids) instead of the real page paths. They all land on the home page, including “privacy policy” and “Cookie Policy”. | 2.4.4, 3.2.4 | Critical – fixed 7 Nov 2026 | Replace them with the real paths (/privacy-policy/, /cookie-policy-2/…). This is also a functional bug. Done: all links now use the real paths. |
| 9 | Button links all read “Learn More” (39 on the home page and listings) with no context for screen reader link lists. | 2.4.4 | Minor – fixed 7 Nov 2026 | Add a visually hidden suffix: “Learn more about the project”. Done: every “Learn More” / “Read More” link now has a hidden suffix with the page title or the site name. |
| 10 | 509 links open in a new tab (target="_blank") without telling the user. | 3.2.5 (AAA), good practice | Minor – fixed 7 Nov 2026 | Add “(opens in a new tab)” as hidden text or an icon with a text alternative. Done: hidden text in the page language and rel="noopener noreferrer" on all external links. |
| 11 | A “Skip to content” link exists (#content) on all pages. This is good, but 18 pages (all single posts and listings) have no <main> element for it to land on. | 2.4.1, 1.3.1 | Major – fixed 7 Nov 2026 | Make sure every template outputs <main id="content">. Done: all pages now have it. |
| 12 | The CSS does not remove focus outlines (no outline:none found) and defines 50 :focus rules: no failure detected statically. It must still be confirmed in the browser. | 2.4.7 | Pass (to verify) | Test with Tab on a real browser. |
Understandable
| # | Issue | WCAG | Severity | Recommendation |
|---|---|---|---|---|
| 13 | The contact form fields (name, e-mail, message) have only a placeholder and no <label>. The placeholder disappears when typing. | 3.3.2, 1.3.1, 4.1.2 | Critical – fixed 7 Nov 2026 | Add visible labels linked with for/id. Done: labels were added, then the contact form was removed altogether; contact details are shown as text on the page. |
| 14 | Two fields on the contact page share the id form-field-email (contact form and newsletter form in the footer), so labels and scripts can attach to the wrong field. | 4.1.1 (obsolete in 2.2, still an id-uniqueness issue) | Major – fixed 7 Nov 2026 | Give each form unique ids. Done; both forms have since been removed from the site. |
| 15 | No form error messages were detectable in the static HTML (they are produced by JavaScript). The site no longer has any form, so there are no error messages to test. | 3.3.1 | Not applicable | No forms left on the site. |
Robust
| # | Issue | WCAG | Severity | Recommendation |
|---|---|---|---|---|
| 16 | The site title “Countering Holocaust distortion on social media” is an <h2> that comes before the page <h1> on all 54 pages, and the footer jumps to <h5>. The heading outline is not logical. | 1.3.1, 2.4.6 | Major – fixed 7 Nov 2026 | Make the site title a <p>, keep one <h1> per page and use footer text instead of headings. Done: site title and footer lines are paragraphs, heading levels never skip. |
| 17 | 5 listing pages (home, blog pages 2–5) have more than one <h1>; the contact page has none. | 1.3.1, 2.4.6 | Minor – fixed 7 Nov 2026 | One <h1> per page. Done. |
| 18 | The main menu is exposed twice (desktop and mobile copy). The mobile copy is correctly aria-hidden but contains links with tabindex="-1"; verify that it cannot be reached by keyboard when open. | 4.1.2, 2.1.1 | Minor | Test keyboard and screen reader on a narrow viewport. |
| 19 | Social icon links (Facebook, Twitter, YouTube) have hidden text, but it is the icon name (“Facebook-f”). | 4.1.2, 2.4.4 | Minor – fixed 7 Nov 2026 | Use “Facebook page of the project”. Done: the four social icons now have descriptive names. |
Colour contrast
| Element | Foreground | Background | Ratio | Required | Pass? |
|---|---|---|---|---|---|
| Body text | #3A3A3A | #FFFFFF | 11.37:1 | 4.5:1 | ✅ Pass |
| Header sub-title (20 px) | #737373 | #FFFFFF | 4.74:1 | 4.5:1 | ✅ Pass |
| Primary buttons (before: #3A8BB6, 3.78:1) | #FFFFFF | #2A6A8F | 5.90:1 | 4.5:1 | ✅ Pass (fixed) |
| Footer text, 12 px (before: 3.78:1) | #FFFFFF | #276588 | 6.36:1 | 4.5:1 | ✅ Pass (fixed) |
| Footer headings, 15 px (before: 3.04:1) | #CCEDE8 | #276588 | 5.10:1 | 4.5:1 | ✅ Pass (fixed) |
| Brand blue text/links on white (before: #3A8BB6, 3.78:1) | #2A6A8F | #FFFFFF | 5.90:1 | 4.5:1 | ✅ Pass (fixed) |
| Grey #737373 on light green | #737373 | #CCEDE8 | 3.80:1 | 4.5:1 | ❌ Fail if used |
Keyboard navigation
Static analysis only. To be confirmed manually.
| Element | Expected | Result of the static check |
|---|---|---|
| Skip link | First Tab stop, jumps to the content | Present on all pages; target <main> missing on 18 pages |
| Main menu | Tab, Enter/Space to open submenu, Escape to close | Submenu toggles are href="#" links: no button semantics |
| Focus indicator | Always visible | No outline removal found in the style sheets |
Screen reader
| Element | Announced as | Problem |
|---|---|---|
| Logo link | “link” (no name) | No alternative text |
| Event thumbnails | “link” (no name) | Image is the only link content and has an empty alt |
| Team photos | “Martin underscore Rehm2, image” | File name used as alt |
| English pages | Read with an Italian voice | Wrong lang |
| Page structure | Heading level 2 (site title) before the level 1 title | Illogical outline |
Priority fixes
- Done on 7 Nov 2026: linked images (#1), team photo alt text (#2), footer and button contrast (#3), page language (#5), menu toggles (#7),
/?page_id=links (#8),<main>(#11), contact form (#13, #14), heading structure (#16, #17). - Also done on 7 Nov 2026: link text and new-tab notices (#9, #10), brand blue for small text (#4), line breaks in headings (#6), social icon names (#19).
- Manual tests still needed: keyboard-only navigation and menu behaviour (#18, #12), screen reader (VoiceOver/NVDA), zoom to 200%.
Feedback
If you find an accessibility barrier on this website, please tell us through the contact page.