Development history
The chronological development log of auditmysite — finding, fix and verification for each change. The changelog lists the same changes per release.
This page keeps the full development log as it was written during development (translated from the German original): for each change the finding, the fix and how it was verified. The changelog summarizes the same changes per release.
Detailed, chronological development history for auditmysite — each entry documents a finding,
the fix, and how it was verified. Extracted from CLAUDE.md’s former “Current State” section
so CLAUDE.md itself stays focused on working rules and a short current-state summary. Newest
entries first (unchanged order from before the extraction).
-
Unreleased — Link purpose from
a11y-rules0.24.0 (casoon/barrierlab#13, #51):link_purposeandlink_purpose_link_onlyhad been left behind at B5 (#743), although #690 had moved them there. They now run in the shared rule set, both files are deleted, and the old IDs resolve viaLEGACY_RULE_IDS.links/generic-nameuses the previous local list (15 languages, including navigation words such as “Start”) and the context evaluation from #569; with context it is Low instead of a separate IDlink-name-context. New:links/url-name,links/single-character-name,links/new-window-unannounced(checkstarget="_blank"instead ofaria-haspopup, 3.2.5 AAA with its own taxonomy entry and explanation text) andlinks/purpose-link-only(2.4.9). All areREVIEW; generic link texts without context were violations locally. 2.4.9 and 3.2.5 thus count as “notes only”, the AA numbers (30/25) stay. Live inros-lackner.de: 5 ×link-name-context→ 5 ×links/generic-name(Low); detection corpus with Chrome green. -
Unreleased — Report quality after the inros review: An external review of the single and the sitemap report for inros-lackner.de was checked point by point against code and the live site; only confirmed findings were changed, refuted ones remain documented. Measurement errors: Best Practices and Tech Stack reported 100 without any data collection (now a check status), CSS coverage had numerator = denominator (316/316 → 316/5076), the viewport calculation used different module weights than the published ones, Security deducted for context-dependent headers (30 → 40), three WCAG criteria were missing from the coverage list (manual 22 → 25). Batch: link graph starting from the home page, measured sitemap status distribution, sample disclosed, range instead of “clean pages”, topic comparison with the correct unit (
similarity_percent,shared_termsas an alias) from the main content instead of the body, page groups and shared blocking files (5 instead of “100”). Language: findings with “möglicher Rechtsrelevanz” (possible legal relevance) instead of “rechtlich relevant” (legally relevant), heuristic UX/journey statements marked as such, sample messages and schema matrix localized. PDF: finding matrix with full titles, no more empty pages or stranded headings (renderreport 0.6.2), batch PDF no longer failed on PDF/UA.crossin the release workflow pinned to a commit. Evidence: live runs single and batch (20 of 685) before/after, rendered pages inspected. -
Unreleased — Security advisories of October 2026:
rustls0.23.46,rustls-webpki0.103.16 andwebpki-roots1.0.11 in the lockfile (RUSTSEC-2026-0347/0348/0349, -0381, -0382);zip2 → 9 andc2pa0.90 → 0.91 (RUSTSEC-2026-0367/0368/0369, both copies ofzip). The browser installer now recognizes directory entries viaZipFile::is_dir(), new unit test for extraction.cargo audit: no vulnerabilities. -
Unreleased — Review notes, control contrast and tree regions from
a11y-rules0.23.0 (#722, #698, #700, #738; casoon/barrierlab#39, #21, #23, #41): The seven review-note stubspointer_gestures,motion_actuation,no_timing,no_interruptions,re_authenticate,unusual_wordsandhelprun asmanual/*in the shared rule set. StillUNTESTED, once per page, but only with a trigger (gesture widgets, inline script with motion sensors, fields, live regions, login, text). The heuristic part ofhelp(every text field withoutaria-describedbyas a 3.3.5 violation) is dropped.non_text_contrast_cssruns ascontrast/control-insufficient/contrast/control-undetermined(1.4.11) withappearance,border-top-*and its own surface from the DOMSnapshot; if the background is missing,UNTESTEDinstead of a comparison against white. Deleted: eight rule files; the old IDs resolve viaLEGACY_RULE_IDSandLEGACY_WCAG_MAP. The CDP walk now marks shadow roots and slotted content as separate tree regions, IDs apply per region.html-conform0.3.2 no longer treats<legend>after whitespace in the<fieldset>as invalid. Live before → after (2026-10-23, AA, desktop): upscale.casoon.dev/aufgaben/ score 92 → 97 (html-content-modelat the<legend>is dropped); bund.deids/duplicate1 → 0 (#content), sachsen-anhalt.de 2 → 0 (#panel,#card__heading) — IDs from the shadow roots of the muse components, scores unchanged. bundesregierung.de (AAA): one new note each for 2.5.1 (Slick carousel), 2.2.3, 2.2.4, 3.1.3 and 3.3.5; 2.2.5 and 2.5.4 silent without a trigger. Detection corpus (Chrome) green, expectations switched to the new IDs. -
Unreleased — Target size, order, endless animation and pointer-only from
a11y-rules(#698, barrierlab#49):targets/size(2.5.8 AA) andtargets/size-enhanced(2.5.5 AAA, only what 2.5.8 does not already report) replacetarget-size-minimumandtarget-size;order/visual-mismatch(1.3.2) replacescss-order-reading-sequence;motion/infinite-animation(2.2.2) replaces the animation and<marquee>part ofpause-stop-hide;keyboard/pointer-only(2.1.1,cursor: pointeroronclickwithout role, tabindex and a control inside it) is new. Deleted:target_size_minimum,target_size_enhanced,meaningful_sequence,pause_stop_hide. The old IDs keep resolving viaLEGACY_RULE_IDS(rule filter) andLEGACY_WCAG_MAP(taxonomy). The verdict changes: 2.5.8 and 2.5.5 wereFAIL, nowREVIEW; a target that is still growing during measurement staysUNTESTEDas before. 1.3.2 and 2.2.2 were and remain review notes. Intentionally different: no more upper limits (locally 5 findings, 1000 targets, 5 flex containers — which is why the order check did not see the footer of bundesregierung.de and the header of berlin.de);flex-direction: *-reversecounts; every endless animation counts, even short runs (2.2.2 applies to motion that runs for more than five seconds in total; locally only runs over 5 s),prefers-reduced-motionno longer cancels the finding, paused animations do not count (locally they did). No longer checked: the carousel signals ofpause-stop-hide(data-autoplay,data-ride,.swiper-autoplay-running,data-update-interval) — no hits on the six reference pages. Since a11y-rules 0.22.0 every control counts as a target, regardless oftabindex(carousel dots with roving tabindex: bundesregierung.de mobile#slick-slide-control00–03, 10 × 10 px, now reported; plus 2.5.5 atdiv[role=button]bundesregierung.de and#moreNewswetter.com, both real targets). Corpus: new verdictabsent(no finding of any kind), becausepassonly counts violations and never fails forREVIEWrules; new casepointer_only. Live before → after (2026-10-05, desktop and mobile, violations / score): AA gov.uk 3 → 3, bundesregierung.de 18 → 13 (the 5 local 2.5.8 violations, 4 of them skip links at −99999 px, are dropped), wetter.com 137 → 137, n-tv.de 73 → 64 / 36 → 39, spiegel.de 100 → 98 / 24 → 25, berlin.de 31 → 31; AAA gov.uk 45 → 40 / 89 → 91, bundesregierung.de 87 → 74, wetter.com 229 → 223, n-tv.de 390 → 371 / 29 → 34, spiegel.de 347 → 341 / 21 → 22, berlin.de 61 → 53 / 38 → 41. New as review note: endless animations on spiegel.de (9) and bundesregierung.de (1), order on berlin.de (2), bundesregierung.de and spiegel.de, 2.5.5 without an upper limit (gov.uk 82 entries instead of 5 violations). -
Unreleased —
pointer_events_noneandanimating(#698, barrierlab#49):pointer_events_noneis the computedpointer-events: nonefrom the DOMSnapshot.animatingcomes from a pass before the snapshot, likeobscured:document.getAnimations()withplayStaterunningand finiteendTime— which also covers running transitions —, endless animations do not count; an element counts as animated if it itself or an ancestor is in it, main document only. The computedanimation-*values alone are not suitable for this: they remain after an animation has ended. Seen filled (2026-10-05, desktop,Some(true)):pointer_events_nonebundesregierung.de 114, spiegel.de 120, gov.uk 6, berlin.de 2, corpustarget_size_hidden_neighbours1;animatingbundesregierung.de 246, wetter.com 89, spiegel.de 23, corpustarget_size_animation1 (a#slow). -
Unreleased — Layout fields filled, comparison with local heuristics (#698):
RenderedCdpDocument::layoutnow delivers, on every element with a layout object, the fields from the DOMSnapshot (new computed stylesflex-direction,order,min-width,cursor,animation-name/-duration/-iteration-count/-play-state,top,scroll-padding-top):flex_reversed(flex container with*-reverse),order,min_width_px(auto→ 0, pixel values only),cursor_pointer,infinite_animation(pairwise over theanimation-*lists: name, duration > 0,infinite, notpaused) andhides_focus: a fixed or sticky bar in the main document, at least 20 px high, half as wide as the page, lower than the visible area (a consent dialog over everything is not a bar), which starts abovescroll-padding-topand reaches lower — fixed at its position in the visible area, sticky at itstop; only the outermost one.obscuredunchanged (only elements with their own text).focus_visiblestaysNone: no pass of this retrieval moves the focus. The heuristics still run only in the background (not inSHARED_RULES); the local rules remain. Seen filled (2026-10-05, desktop,Some(true)):flex_reversedgov.uk 4, spiegel.de 20;order≠ 0 berlin.de 4, bundesregierung.de 2, spiegel.de 2;min_width_px> 320 bundesregierung.de 6, wetter.com 2, berlin.de 2;cursor_pointeron all six;infinite_animationspiegel.de 9, bundesregierung.de 1;hides_focusspiegel.de 1 (header.sticky), n-tv.de 1;obscuredwetter.com 190, n-tv.de 61, spiegel.de 32. -
Unreleased — Rule filter applies to the shared rules (#698):
[rules] disabled/enabled_onlyand--disable-rulepreviously only worked for the local rules; since contrast is shared,--disable-rule color-contrastno longer switched anything off. Nowwcag::shared::retain_allowedremoves a shared ID if the filter disables it under its own name or under an old ID fromLEGACY_RULE_IDS(color-contrast→contrast/text-*,link-in-text-block,landmark-one-main, …, only completely superseded rules), and records it asdisabled_by_rule_filter; likewise in iframes. -
Unreleased — Contrast over images by sampling again (#698, barrierlab#47/#48):
RenderedCdpDocumentdeliversRendering::sampled_backdrop: a screenshot beyond the visible area (captureBeyondViewport), cropped to the candidates and in CSS pixels (scale = 1/devicePixelRatio), loaded into the page once; per element the WCAG luminances in the box (alpha against white, at most 2500 per element on a grid). Page-wide at most 60 elements, the largest first: own text in the main document, text color known, background not determinable, neither visually hidden nor covered (covered when measuring in the visible area), up to 15000 CSS pixels of depth — deeper staysUNTESTED(memory, time; a canvas is at most 32767 px high). Time limits: the script waits at most 5 s for the screenshot, the whole sampling at most 10 s; after that, or if the screenshot fails, no element gets a background and the audit continues. The shared rule judges on it like the formerly local one (median, 40th percentile):FAIL, passed or review note. The integration teststest_image_contrast_pixel_samplingandtest_opacity_overlay_contrast_pixel_samplingrun unchanged against their old verdicts again. The PDF line “Kontrast X (erforderlich Y)” (contrast X (required Y)) reads the measured values of the shared rule (contrast_ratio,required_ratio, delivered without:1). Seen sampled (2026-10-05, desktop, without--dismiss-consent): berlin.de 14, gov.uk 0, bundesregierung.de 0, wetter.com 5, n-tv.de 39, spiegel.de 0 (the image credits lie deeper than 15000 px). Audit runtime before → after within the noise (−9 s to +1.5 s per page). -
Unreleased — Contrast from
a11y-rules(#698, barrierlab#47):contrast/text-insufficient(1.4.3 AA),contrast/text-undetermined(1.4.3,UNTESTED) andcontrast/text-enhanced(1.4.6 AAA, only with--level aaa; reports only what passes 1.4.3) replacecolor-contrast. Deleted:wcag::rules::contrastincluding the page rule and the pixel comparison with the screenshot,accessibility::styles(extract_text_styles);Colornow lives innon_text_contrast_css(remainswcag::rules::Color). The old ID keeps resolving via the taxonomy (a11y.contrast.weak,axe_id: color-contrast); 1.4.6 has its own AAA entrya11y.contrast_enhanced.weakwith AAA weight (before, AAA failures counted as 1.4.3 with the full deduction). Dark mode and the color-vision-deficiency view count the shared violations over a fresh DOMSnapshot; the light/dark comparison pairs elements via the backend ID. Intentionally different: text under a fixed or sticky element (cookie banner) isUNTESTED(#716 case 7); text underaria-hiddenis measured (#395 excluded it). Comparison shared against local (2026-10-05): corpus (contrast_shadow_and_inline,gradient_text_contrast,low_contrast_text,text_fill_color_contrast) identical, AA and AAA; gov.uk identical; bundesregierung.de AA equal, AAA +4 (meta navigation, skipped locally as hidden: absolutely positioned list in a 0 px widenavwithoverflow: hidden); wetter.com without consent overlay AA equal (15), with overlay the ten navigation itemsUNTESTEDinstead of 2.37:1, AAA additionally the consent dialog (skipped locally as hidden) and teaser captions with their own opaque surface (locally review note); n-tv.de AA no violations in either, AAA 25 local violations under the consent overlay nowUNTESTED; spiegel.de AA +19 real violations (4.04:1, white on #e64415 and vice versa) that the local rule missed (it treated the class nameoverflow-hiddenas hidden), AAA correspondingly more. Corpus expectations switched to the new IDs. Live againstmain(2026-10-05, with sampling), accessibility AA / AAA before → after: gov.uk 93 → 93 / 70 → 89, bundesregierung.de 49 → 49 / 46 → 49, wetter.com 22 → 22 / 18 → 20, n-tv.de 36 → 36 / 23 → 29, spiegel.de 28 → 24 / 20 → 21 (AA violations before → after: 0 → 0, 0 → 0, 15 → 12, 25 → 23, 3 → 22; the decreases are text under the consent overlay, nowUNTESTED). AAA rises because 1.4.6 now counts with AAA weight. Reference page berlin.de 45 → 49, just above the band 15–48: the local rule reported 11 violations on desktop / 12 on mobile, mostly image credits and teaser titles over photos (p.image__copyright,a.title), measured against an ancestor color (2.56:1 and 1.00:1 respectively). With page-wide sampling none isUNTESTEDany more; 1 / 3 violations remain (includinga.title, 4.02:1), the rest passes over the photos. The band needs to be re-evaluated. -
Unreleased — Visually hidden and covered text, background over images (part of #698, host side of barrierlab#47):
RenderedCdpDocumentdeliversRendering::visually_hiddenfrom theDOMSnapshot(new style valuesclip,clip-path,text-indent,position,opacity):opacity: 0on the element or an ancestor,clip: rect(≤ 1px …)on an absolutely positioned box,clip-path: inset(≥ 50 %),text-indentfrom 999 px, a box of at most 1 px withoverflow: hidden|clip(on the element or up to twelve levels above; an absolutely positioned descendant escapes a static one, a fixed one escapes any box) and a frame entirely to the left of or above the document. OfLayoutthe document fills onlyobscured, on elements with their own text in the main document: a script pass before the snapshot useselementFromPointat the center to check whether a foreign fixed or sticky element covers the text; only the hits are mapped to backend IDs viadescribeNode. The effective background color isNoneif a painting sibling of the element or of an ancestor (up to six levels, up to the first opaque surface) overlaps the box and one of the two is absolutely or fixed positioned (#716 case 6: wetter.comh4.newsCarousel__headline, spiegel.defigcaption > p). Seen filled (DoD 4, 2026-10-05,visually_hiddenmeasured / true,obscuredmeasured / true): gov.uk 444/15, 132/0 (includingbutton.gem-c-search__submit); bundesregierung.de 6706/5634 (almost all SVG sprite paths in a 0 px<svg>), 232/0; wetter.com 1897/569 (hover menus withopacity: 0), 577/199 with consent overlay and 0 without; n-tv.de 3832/16, 1097/79; spiegel.de 6793/135, 1027/36. -
Unreleased — Static presentation rules from
a11y-rules0.19.1 (#699): The rules of the presentation convention that only need the markup now come from the shared rule set (barrierlab#22):display/toggle-missing(replaces the local rule of the same name, same text) and the newviz/text-missing,viz/caption-missing,viz/static-missing,viz/table-missing(the last one a review note). The new IDs have their own taxonomy entries (a11y.display_caption.missing,a11y.display_static.missing,a11y.display_table.review;viz/text-missingsharesa11y.display_text_layer.missing), explanations and score ranges; likedisplay/*they count as convention rules, not as a legal note. What only the running page shows stays indisplay_modes:display/init-missing(observer before navigation),display/text-hidden(including computed visibility and the hidden figure, #725),display/text-media-visibleanddisplay/text-not-visible. These last two IDs also exist ina11y-rules, but only as the static part; auditmysite does not adopt them, so that an ID never has two sources. Intentionally different:display/text-not-visiblein text mode now only reports a text layer that has content but does not appear; if it is missing or empty, that isviz/text-missingand applies in every mode, not only in text mode. New corpus fixturedisplay_modes_viz_static, the expectation indisplay_modes_violationsmoves toviz/text-missing. Checked: unit tests, detection corpus; cross-check on geographia.eu (reference implementation, e.g.climate-monitorwith 26 figures): old and new versions report nothing there, no false positive on conforming pages. -
Unreleased — Rendering layer from the DOMSnapshot, three presentation rules from
a11y-rules(part of #698, host side of barrierlab#21 second part;a11y-*0.20.0):RenderedCdpDocumentnow fillsComputedStylecompletely from the sameDOMSnapshot.captureSnapshot: text and effective background color (blended over the ancestors in the flat tree, white at the bottom;Nonefor background image, gradient or unreadable color), font size, weight, style, family,list-style-type,text-decoration-line,border-bottom-style; transparent text fill (background-clip: text, #640) yields no color,display: contents(such as<slot>) takes color and font from the rendered text.bounds()delivers the frame of the layout object,scroll_overflow_px()the scroll overhang fromincludeDOMRects(scrollRects/clientRects, only on axes withoverflow: auto|scroll). The document does not deliver aLayout; the heuristics on it stay unrun. Seen filled (DoD 4, 2026-10-05, elements with layout object / all): gov.uk 444/617, bundesregierung.de 6695/7591, wetter.com 1905/2612, n-tv.de 3636/4789, spiegel.de 6673/8891 — every new field filled on every page. Adopted:redundant-role(<ul>/<ol>) →lists/role-redundant(4.1.2 A),link-in-text-block→color/link-indistinct(1.4.1 A; in addition, font family, bottom edge and background count as a distinction),scrollable-region-focusable→keyboard/scrollable-region-not-focusable(2.1.1 A). Deleted:redundant_role,use_of_color,scrollable_region; the old IDs keep resolving in taxonomy and explanations. The color-vision-deficiency view countscolor/link-indistinctonce instead of per mode (the emulation does not change computed styles). Corpus fulfilled unchanged (redundant_role_list_style,link_in_text_block_context,scrollable_region_focusable,misc_content_checks). The three rules run only in the top-level document like the ones they replace. Contrast stays local:contrast/text-*matchescontraston the corpus (shadow DOM, 4.46:1 unrounded, float container, gradient text undetermined), but live it lacks AAA thresholds, visually hidden text is measured (gov.uk search button,text-indent: -5000px), and text over positioned images (#716 case 6) becomesFAILinstead ofUNTESTED(wetter.comnewsCarousel__headline, spiegel.de image credits). Live againstmain(2026-10-05), accessibility AA / AAA before → after: gov.uk 93 → 93 / 70 → 70, bundesregierung.de 49 → 49 / 46 → 46, wetter.com 22 → 22 / 18 → 18, n-tv.de 36 → 36 / 22 → 22, spiegel.de 26 → 26 / 20 → 20; the three rules ran without findings before and after, the other deviations (color-contrast±1,target-size8 → 10 on AAA) are page changes between the runs in unchanged rules. -
Unreleased — Reduced motion from
a11y-rules0.19.1 (part of #698): Since 0.19.1a11y-rulesresolves theanimationshorthand according to CSS Animations; Chrome’s serialization (2s linear 0s infinite normal none running spin) yields the namespinagain instead ofnone(bug from this PR, fix in barrierlab). With that,prefers-reduced-motion→motion/reduced-motion-ignored(2.3.3 AAA, note instead of violation, one message per page) runs over the stylesheets;reduced_motionis deleted, the old ID keeps resolving in the taxonomy. 2.3.3 counts as a note criterion (AAA). Corpus:media_and_motion,reduced_motion_transformandtarget_size_animationreport the note,reduced_motion_overrideandreduced_motion_colour_onlydo not. Intentionally different: The superseded page rule ran from--level aadespite being AAA (min_level: AA); the shared note appears, like the other AAA IDs, only with--level aaa. Live againstmain(2026-10-04) on AAA the same hits (bundesregierung.de and n-tv.de 1 each, gov.uk, wetter.com, spiegel.de 0); on AA the previous 2.3.3 finding is dropped, accessibility AA / AAA before → after: gov.uk 92 → 93 / 67 → 70, bundesregierung.de 49 → 49 / 35 → 46, wetter.com 21 → 22 / 17 → 18, n-tv.de 22 → 31 / 18 → 22, spiegel.de 25 → 28 / 18 → 20. -
Unreleased — Rules over stylesheets from
a11y-rules(host side of #698, barrierlab#21 first part): auditmysite reads the stylesheets of the page (document.styleSheets, per sheet thecssTextof all rules; foreign sheets without readablecssRulesare missing as before), parses them withstylesheet-parse0.1.0 (new direct dependency) and passes them together with the document of the shared rules toa11y_rules::run_stylesheets_in(accessibility::fetch_stylesheets,wcag::shared::run_shared_rules_with_stylesheets). If reading fails, the rules stayNotRun::CapabilityMissing. Frames get no sheets; the rules judge the page like the ones they replace, which ran only in the top-level document. Adopted:focus-visible-outline-none→focus/outline-removed(2.4.7 AA, high; an outline set again in:focuscounts as a replacement, sueddeutsche.de),css-orientation-lock(stylesheet part) →orientation/content-hidden(1.3.4 AA, note, only selectors with a hit on the page, without pseudo-elements),visual-presentation(justified text, line spacing) →text/justifiedandtext/line-height-tight(1.4.8 AAA, notes, measured on the<p>of the page). Deleted:focus_visible_css; fromorientationthe stylesheet search (the computedtransform: rotateonbody/htmlstays), fromvisual_presentationthe stylesheet search (theUNTESTEDnote on color choice and column width stays). 1.4.8 counts as a note criterion (AAA). Not adopted because of a bug ina11y-rules0.19.0:motion/reduced-motion-ignored– Chrome serializes theanimationshorthand completely (2s linear 0s infinite normal none running spin), and the rule takesnonefromanimation-fill-modeas the animation name, so every animation via the shorthand drops out (corpusmedia_and_motion,target_size_animation).reduced_motiontherefore stays here for now (fixed with 0.19.1, see above). Deviations in the changelog ofa11y-rules0.19.0. Corpus:media_and_motionreportsfocus/outline-removedandorientation/content-hidden,text_and_layoutreportstext/justified(the tight line height there is on a<div>, not on a<p>). Live againstmain(2026-10-04), accessibility AA / AAA before → after, B4–B7 and stylesheets together: gov.uk 92 → 93 / 67 → 70, bundesregierung.de 49 → 49 / 35 → 43, wetter.com 21 → 22 / 17 → 18, n-tv.de 22 → 29 / 18 → 21, spiegel.de 25 → 28 / 18 → 20. Dropped are the false positivescss-orientation-lockon bundesregierung.de and n-tv.de (breakpoint markerbody:before, close button) andvisual-presentationon spiegel.de (selector prefix); new on AAAtext/line-height-tighton gov.uk and bundesregierung.de. -
Unreleased —
<area>and self-starting audio froma11y-rules(#696, addendum): Witha11y-rules0.19.0 the view sees<area>and<audio>withoutcontrolsalso with computed styles (UAdisplay: none; reported from this PR, fix in barrierlab). With that,area-alt→images/area-alt-missing(1.1.1 A;aria-label/aria-labelledbycount) andbackground-audio→media/audio-autoplayrun via the shared rule set;image_input_rulesandbackground_audioare deleted.media/audio-autoplayis a review note under 1.4.2 (A) instead of a violation under 1.4.7 (AAA) and thus already runs on AA; taxonomya11y.audio_control.missing, 1.4.2 counts as a note criterion (it was already in the manual list). Both also run in frames. Corpus:misc_content_checksandmedia_and_visualreport under the new IDs. -
Unreleased — Table, document, language and role rules from
a11y-rulesinstead of own ones (#697, B7): Twelve IDs run via the shared rule set:th-has-data-cells→tables/header-without-data(includingtables/data-undetermined,UNTESTED, for a row supply not yet rendered, #654),td-headers-attr→tables/headers-attr-invalid,html-xml-lang-mismatch→document/lang-mismatch,language-of-parts→language/part-unmarked(newlanguage/part-undeterminedon pages that are neither German nor English),abbreviations→language/abbreviation-unexpanded(note instead of violation),meta-refresh→timing/meta-refresh(0 s is not a deadline),heading-orderfromsection_headings→headings/section-without-heading(note, only articles and named sections),redundant-role→aria/role-redundant,title-only-description→names/title-only(note; text fields are still reported byforms/title-only-label),content-on-hover-focus→patterns/tooltip-unreferenced. Deleted:table_extended,language_extended,language_of_parts,abbreviations,content_on_hover,info_relationships,section_headings, the tree rulesth-has-data-cellsandheading-order. Dropped without replacement:presentation-semantic-children– according to WAI-ARIA 1.2,role="presentation"/"none"removes the semantics only from the element itself, not from the descendants; the rule would have reported the APG menubar pattern (<li role="none">around menu links) (barrierlab: 187 false positives on 48 pages), the table case istables/presentational-with-headers. Fromsection_headings, the outline gaps (headings/skip-level) and “more than 10 paragraphs, fewer than 3 headings” (no evidence) are dropped. Staying in the host: fromredundant_roleonly<ul>/<ol>withrole="list"– whether the role is superfluous depends on the computedlist-style-type(#644), whicha11y-domdoes not yet deliver (barrierlab#21); the corpus caseol#numbered-liststill reports. Fromtiming_adjustablethe page-wideUNTESTEDnotes for script deadlines (2.2.1, now as page rule2.2.1/timing-adjustable) andtimeouts(2.2.6), which barrierlab assigns to the manual checklist. The presentation rules from barrierlab#22 (viz/*, static halves ofdisplay/*) are not adopted:display/text-hidden,display/init-missinganddisplay/toggle-missingcarry the same IDs indisplay_modes, but there also check computed visibility and the timing ofdata-display; splitting the same ID across two sources is a step of its own,display_modesstays unchanged. Taxonomy: newa11y.language_of_parts.unmarked(3.1.2 AA;language-of-partshad no entry); 3.1.2, 2.4.10 and 3.1.4 count as pure note criteria, so 3.1.2 is in the list of criteria to be checked manually (21 → 22,docs/PARITY_CONTRACT.jsonc, README). Table, role, name and tooltip rules as well as abbreviations also run in frames. Checked: detection corpus before/after (renames, notes instead of violations as in the barrierlab changelog,language/part-undeterminedoninvalid_lang_codeandskip_link_language, new section notes on five cases). Check B4–B7 in total againstmain(detection corpus 76 cases on AAA: eleven accessibility scores rise by 1–9 points, none falls; live pages on AA, accessibility before → after: gov.uk 92 → 93, bundesregierung.de 49 → 49, wetter.com 21 → 22, n-tv.de 22 → 25, spiegel.de 25 → 28). New on real pages:names/title-only(spiegel.de 132 notes instead of 5 findings),frames/name-missing(n-tv.de 6 instead of 2, including the three sports-data frames withtitle=""),aria/role-redundant(wetter.com 9 instead of 20 capped, hidden menus no longer count);navigation/location-missingand the other AAA notes do not run on AA. Reference run and score calibration stay in their bands. -
Unreleased — Image and media rules from
a11y-rulesinstead of own ones (#696, B6): The following now run via the shared rule set:input-image-alt→images/input-alt-missing,object-alt→objects/alt-missing,server-side-image-map→images/server-side-map(all 1.1.1 A) andframe-title→frames/name-missing(2.4.1 A, high;a11y-rulesadditionally lists 4.1.2). Deleted:server_side_image_map, fromimage_input_rulesthe checks for<input type="image">and<object>, frommedia_rulesthe frame names and the tree rulevideo-caption(unnamedapplication/img, named decorative element – barrierlab did not adopt it for lack of evidence or because ofsvg/name-missing,images/alt-missingandaria/attribute-prohibited). Intentionally different:aria-labelledbycounts as an alternative,<embed>is no longer checked, only<iframe>(no<frame>), no upper limit per page; the rendered size ≤ 1 px is unknown toframes/name-missingwithout geometry (only width/height as attribute).frames/name-missinghas its own explanation text for the first time (frame-titlefell back to the 2.4.1 text “Fehlende Sprungnavigation” (missing skip navigation)). Staying in the host: the caption checkvideo-caption(loads the<track>file over the network),frame-tested(foreign frames are only known to the browser) andmedia-alt(1.2.8) – barrierlab refers tomanual/media-alternativesfor it, the manual checklist is not yet carried by auditmysite. Not adopted because of a bug ina11y-rules0.18.0:images/area-alt-missingandmedia/audio-autoplaynever report with computed styles, because the view removes everything withdisplay: noneand the UA stylesheet gives that to every<area>and every<audio>withoutcontrols(corpusmisc_content_checks,media_and_visual).area-alt(image_input_rules) andbackground-audiotherefore stay here for now. Image and frame rules now also run in frames. Coverage: 2.4.8 (navigation/location-missing, only a note since B5) no longer counts as an automatically checked AAA criterion. Checked: detection corpus before/after (only the renamed IDs, selector nowtag#id). -
Unreleased — Link and pointer rules from
a11y-rulesinstead of own ones (#695, B5): Witha11y-rules0.18.0 three IDs run via the shared rule set:click-events-have-key-events→keyboard/click-handler-not-focusable(2.1.1 A, high),link-as-button→links/used-as-button(4.1.2 A, low),location→navigation/location-missing(2.4.8 AAA, low). Deleted:click_handlers,fake_navigation_link,locationincluding theirPAGE_RULESentries; the old IDs resolve via the new ones in the taxonomy and the explanation texts. Intentional differences (changelog ofa11y-rules): no upper limit per page any more (previously 10 and 20 respectively),<a onclick>withouthrefis a click handler instead of a fake link,navigation/location-missingis a review note instead of a violation and also sees navigation in the shadow DOM. Ofpointer_cancellation(2.5.2) the static part (onmousedown/ontouchstarton controls) is deleted – barrierlab did not adopt it for lack of evidence –, the page-wideUNTESTEDnote stays in the host: The manual checklist (manual/*, barrierlab#39) has no item for 2.5.2, and auditmysite does not carry it yet. New: Shared IDs above the checked level (--level) are removed and recorded asNotRun::Disabled(above_wcag_level) (wcag::shared::retain_up_to_level), just as the superseded AAA rules ran only with--level aaa. Click handlers and fake links now also run in frames. Checked: detection corpus before/after (only the renamed IDs,locationas a note, additionallylandmark_main_in_shadow_root), exclusion integration tests with the uncapped counts (12 and 22 excluded hits respectively). -
Unreleased — Landmark, keyboard and structure rules from
a11y-rulesinstead of own ones (#694, B4): The landmark checks, keyboard reachability, the page without headings and two pattern checks run via the shared rule set (SHARED_RULESinsrc/wcag/shared.rs). Deleted:region,landmark_granular(withis_landmark) andbypass_blocks; fromkeyboardthe two 2.1.1 checks; frompatterns/the findingsdialog-no-focusable,accordion-no-controls,accordion-trigger-not-buttonandaria-expanded-required– pattern detection and journeys stay,PatternAnalysis.violationsis now always empty.keyboard-trap(2.1.2) stays in the host: the note per modal dialog and the page-wideUNTESTEDnote need real keyboard operation. IDs:landmark-unique→landmarks/not-unique;landmark-banner-is-top-level,landmark-contentinfo-is-top-levelandlandmark-main-is-top-level→landmarks/not-top-level;landmark-no-duplicate-bannerandlandmark-no-duplicate-contentinfo→landmarks/banner-duplicateandlandmarks/contentinfo-duplicate;region→landmarks/content-outside(all 1.3.1 A);bypass(“No headings found”) →headings/none(2.4.1 A, including #709);focusable-no-roleandkeyboard(“appears not keyboard-focusable”) →keyboard/focusable-no-roleandkeyboard/interactive-not-focusable(2.1.1 A);dialog-no-focusable→dialog/focusable-missing(2.4.3 A);accordion-no-controls→patterns/accordion-controls-missing(4.1.2 A). Dropped without replacement, as justified in barrierlab#17:accordion-trigger-not-button(on roles withoutaria-expandedthis is reported byaria/attribute-not-allowed, onlink,tab,treeitemWAI-ARIA allows the state, missing focus iskeyboard/interactive-not-focusable) andaria-expanded-required(guessed a disclosure menu from the word “menu”/“Menü” in the name). Intentional differences (details in the changelog ofa11y-rulesand at the entries inSHARED_RULES):landmarks/not-uniqueandpatterns/accordion-controls-missingare review notes instead of violations; duplicate banner/contentinfo point to the second landmark instead of the first;landmarks/content-outsidereports once per block instead of per text node;keyboard/focusable-no-rolecounts only the tab order and no named scrollable region;keyboard/interactive-not-focusableexcludes disabled fields, native<option>,aria-activedescendantand inert content;dialog/focusable-missingsearches in all descendants and does not check a closed<dialog>;headings/nonealso countsrole="heading". The landmark role comes from the markup instead of Chrome’s role (#639, #727). Exclusions (#726): The shared counting rules (landmarks/not-unique,landmarks/main-duplicate,landmarks/*-duplicate) read, with--exclude-selectoractive, the document without the excluded subtrees (ExclusionScope::without_excluded_dom,wcag::shared::adopt_page_counts); the AX variantwithout_excludedand the parametercountedofcheck_all_excludingare dropped,exclusion.excluded_landmarkscounts as before. In frames,keyboard/focusable-no-roleandkeyboard/interactive-not-focusable(previously the tree rulekeyboard) now run, as do the newdialog/focusable-missingandpatterns/accordion-controls-missing; the landmark rules andheadings/nonestay with the main document. Taxonomy: the IDs point to the entries of the superseded rules, whose legacy IDs keep resolving (headings/noneto that ofbypass); newa11y.landmark_nested.invalidanda11y.accordion_controls.missingincluding explanation texts. Witha11y-rules0.17.0. Checked with unit tests, detection corpus, score calibration, reference run and the integration tests on frames, exclusions and landmarks (Chrome) as well as a before/after run on 14 live pages; reference bands gov.uk (75–95) and bundesregierung.de (35–76) re-evaluated (+1 each: content outside landmarks per block instead of per piece of text, dialog focus target also in deeper descendants). -
Unreleased — False positives from upscale.casoon.dev (#739, #740): The dark-mode module reported a dark-only page (
html.darkset permanently,color-scheme: dark, no light layout) asno_dark_mode_supportwith score 50. New is the signal “dark in default rendering”: effective page background (body, else html, else the canvas according tocolor-scheme) dark and body text light; the colors are read via a canvas pixel so thatoklch()from Tailwind v4 also counts. Such a page counts as supported (detection_methods: “Dark by default (no light view)”), withoutno_dark_mode_supportand without the class hint (#739). The mobile module took as the smallest font also elements without readable text; KaTeX’sspan.vlist-s(a zero-width space at 1 px) produced “Smallest font size is 1.0px”. For the smallest font only elements with their own text of more than whitespace and zero-width characters now count (#740). Live: upscale.casoon.dev dark mode 50 → 85, Pythagoras lesson smallest font 1 px → 11 px (real text); gov.uk (light) still without dark-mode support, casoon.de unchanged. #738 (<legend>after whitespace) lies in html-conform: casoon/barrierlab#41. -
Unreleased — Form rules from
a11y-rulesinstead of own ones (#693, B3): The form, context-change and captcha checks run via the shared rule set (SHARED_RULESinsrc/wcag/shared.rs), the superseded own rules are deleted:form_rules,error_identification,input_purpose,identify_purpose,redundant_entry,label_title_only,on_focus,instructionsandlabels(check_form_control, the last remainder of the file). What the running page needs stays in the host: inon_inputthe lookup of a called function viawindow(violation if only it changes the context) and the name guess (“Language”) without a submit button, both now under the same ID as the shared rule (context/on-input), so that the violation supersedes its review note on the same element; inaccessible_authenticationthe paste test (accessible-auth-paste-blocked). IDs:label“no accessible label” andcontrol-missing-labelon form fields →forms/label-missing(3.3.2 A);label“Placeholder used as only label” →forms/placeholder-as-label;label“Form group has no legend or label” →forms/group-name-missing;label“Required field not clearly indicated” and “may not indicate required status” →forms/required-unmarked;label“may require format instructions” →forms/instructions-missing(all 3.3.2 A);autocomplete-valid→forms/autocomplete-invalid(invalid value) andforms/purpose-missing(missing value, 1.3.5 AA), plusidentify-purpose(1.3.6 AAA) →forms/purpose-missing;input-error-messageandaria-invalid-without-describedby→forms/error-unidentified(3.3.1 A);form-field-group→forms/group-missingandlabel-title-only→forms/title-only-label(1.3.1 A);form-no-submit→forms/no-submit(3.2.2 A, including #728);redundant-entry→forms/redundant-entry(3.3.7 A);input-no-context-change(handler in the markup) →context/on-input(3.2.2 A);focus-no-context-change→context/on-focusandcontext/autofocus(3.2.1 A);accessible-auth-captcha→auth/captcha(3.3.8 AA). Intentional differences (details in the changelog ofa11y-rulesand at the entries inSHARED_RULES): a missing label, a missing error description, an unmarked required field and a missing input purpose appear once instead of twice in the report;forms/purpose-missing,forms/required-unmarked,forms/title-only-label,context/on-focusandcontext/autofocusare review notes instead of violations;forms/autocomplete-invalidchecks the whole autofill grammar and is low instead of medium;context/on-inputalso checks radio buttons;forms/no-submitalso counts fields and buttons assigned via theformattribute; the page-wideUNTESTEDnote on 1.3.6 is dropped. The form rules now also run in frames, including those previously checked only in the main document (autocomplete, submit, repetition, context change, captcha). Taxonomy: all IDs point to the entries of the superseded rules, whose legacy IDs keep resolving; new explanation texts forforms/no-submitandauth/captcha. Witha11y-rules0.16.0, which reports an unnamed ARIA form field (combobox, listbox, textbox, …) like the native field without a label as critical. Checked with unit tests, detection corpus, score calibration and reference run (Chrome) as well as a before/after run on 14 live pages. -
Unreleased — SEO headings from the shared rules, no second HTML validator (#724): The SEO view checked missing and multiple H1s, skipped levels and empty headings a second time. These findings now come from
headings/*(a11y-rules) of the accessibility check, after exclusions and once per finding across both viewports;SeoModule::deriveplaces them ahead of the SEO-specific rule for long headings and recomputes score, content profile and SERP view. The SEO heading list (h1_count,h1_text, lengths) now also reads open shadow roots so that it matches the view of the shared rules (dm.de: the h1 of the Usercentrics banner in the shadow DOM counts; SEO score 75 → 67). The local html5ever check (validate_html_locally) is removed: it counted parse errors of the same serialized live DOM thathtml_conformchecks more thoroughly. The validator status in the SEO part is now calleddelegatedand points to html-conform (--full,--html-conform);ParseErrorsremains only so that stored reports still load. Old-versus-new cross-check with--seo: casoon.de, gov.uk, berlin.de and mit.edu with identical heading findings and identical score. -
Unreleased — CSP via
csp-parse(#723):src/securityused to split the Content-Security-Policy itself (split(';')); it now reads it withcsp-parse0.1.0 from barrierlab (CSP3: policy list, directives, source lists with keywords, nonces, hashes, host wildcards). The assessment (which weakness weighs how heavily) stays here. Intended differences: multipleContent-Security-Policyheaders are all read and joined as a policy list instead of only the first; in a policy list a weakness counts only if every policy has it (the browser enforces all of them); a duplicate directive keeps its first value instead of the last; a nonce and a hash count only with a valid base64 value; the wildcard check across all directives reads only source lists (notreport-uri,sandboxetc.). New unit tests for the three cases; security corpus green; the eight reference sites yield the same CSP findings with the old and the new parser. -
1.7.3, 2026-10-01: ARIA and name rules now come from
a11y-rulesinstead of our own implementations (#691 B1, #692 B2, a11y-rules 0.15.0), with new identifiers following the schemearia/*,names/*,dialog/*,popover/*,inert/*; an unnamed dialog now appears only once in the report. Cross-site iframes are checked because the audit browser starts without site isolation (#720). SPA portals are captured only after the first rendered content (#718). False alarms fixed: text layer in hidden panels (#725), unnamedform/regionas a landmark (#727), landmark count despite exclusion (#726, new JSON fieldexclusion.excluded_landmarks),form-no-submitfor pure toggle forms (#728). Reference run (reference_sites_test) and detection corpus green. Details in the entries below. -
Name rules from
a11y-rulesinstead of our own (#692, B2): The checks for missing and insufficient accessible names run through the shared set (SHARED_RULESinsrc/wcag/shared.rs); the superseded own rules are deleted:aria_naming_rules,dialog_rules,summary_name,status_messages,label_in_nameand fromaccessible_nameeverything exceptdescription-duplicates-name(#713) – that one stays becausea11y_domprovides no accessible description; its switch inwcag::engineis now called that instead ofaria-label. Also removed:aria-dialog-nameinpatterns::modal_dialogand the dialog part of the missing name inmodern_attributes(menu and popover stay there). Identifiers:aria-command-name(without button anda[href]),aria-input-field-name,aria-meter-name,aria-progressbar-name,aria-toggle-field-name,aria-treeitem-nameandaria-label“kein Name” (“no name”) →names/required-missing;aria-label“Icon Only” →names/symbol-only;aria-dialog-nameanddialog-name→dialog/name-missing;dialog-name“Dialog Modal” →dialog/modal-unmarked;summary-name→summary/name-missing;aria-live-region-role→status/live-overridden(4.1.3 AA);label-content-name-mismatch→label-in-name/mismatch(2.5.3 A); all others under 4.1.2 A. Severity as before. Intended differences (details in the changelog ofa11y-rulesand at the entries inSHARED_RULES): an unnamed dialog appears once instead of up to three times in the report, an unnamed widget once instead of twice; unnamedmenu,taband native<option>are no longer a finding (ARIA 1.2 requires no name there);meterandprogressbarare under 4.1.2 instead of 1.1.1; non-focusable unnamed widgets are a violation as before inaria_naming_rules, the additional warning fromaccessible_nameis dropped; the purely symbolic name, the missingaria-modaland a changed but not disabled urgency of a live region (alertwithpolite) are review hints instead of violations;dialog/modal-unmarkedchecks onlyrole="dialog", not a native<dialog>;summary/name-missingreports only the<summary>, not additionally the<details>; an emptyaria-labelledbyandaria-describedbyon a named element are no longer a finding;label-in-name/mismatchchecks all roles with names from content and names fromaria-labelledby, not just buttons witharia-label, without the cap of 50 – and now also runs in frames. New taxonomy entrya11y.dialog_modal.missingwith explanation (previously the missingaria-modalshared identifier and title with the missing dialog name); the other identifiers point to the entries of the superseded rules, whose legacy identifiers continue to resolve. Verified with unit tests, detection corpus and score calibration (Chrome). Witha11y-rules0.15.0. The #527 filter (a violation displaces a hint) now compares the backend node ID where both findings carry one: shared findings have short selectors (button), and a violation on one button swallowed the hint on another. Reference band bundesregierung.de re-rated (35–72): three label-in-name false alarms on text hidden via CSS are gone, the cookie dialog without aria-modal is a hint. -
Frames in other processes (#720): After #715, iframes that Chrome shows in their own renderer because of site isolation remained unchecked (
skipped: cross_origin) — for example the web chat on gov.cy (digital-assistant.gov.cy,gov.cyis a public suffix), in which axe reports an unnamedrole="dialog". chromiumoxide 0.8 does create a session internally for such frames, but offers no commands for them. Instead of a custom CDP client, the audit browser now starts without site isolation (--disable-site-isolation-trials,IsolateOrigins/site-per-processoff): cross-site frames run in the page’s process, and the existing frame pass reaches them including enrichment, selectors and exclusions. The profile is fresh and holds no user data; if a future Chrome ignores the flags, the frame is visibly listed ascross_originin the report again. The Chrome test now expects the cross-site frame to be checked with adialog-namefinding; gov.cy live: frame checked, dialog found. -
SPA portals: capture before the first render (#718): After loading, eesti.ee shows an empty splash screen while the Angular app fetches its first view — around 400 ms without a single DOM mutation.
wait_for_page_stabilitycounted 200 ms of quiet as stable, the AX tree was read before the first heading andbypassreported “No headings found”. Quiet without content (nomain, noh1-h3, no visible text) no longer counts as stable; the provenance records the wait asreason, and a page without content until the budget ends ends asbudget_exhausted. New Chrome test with a splash fixture (fails without the fix); detection corpus green; eesti.ee and latvija.gov.lv without the false finding. -
ARIA rules from
a11y-rulesinstead of our own (#691, B1): The ARIA checks run through the shared set (SHARED_RULESinsrc/wcag/shared.rs, all under 4.1.2 A); the superseded own rules are deleted:aria_allowed_attr,aria_prohibited_attr,aria_valid_attr_value,aria_required_parent,parsing,aria_roles,widget_rules, the popover and dialog parts ofmodern_attributesand the tab message frompatterns::tab_list. Identifiers:aria-roles→aria/role-invalid(new in addition:aria/role-abstract) and, for the required parts,aria/required-children-missing;aria-attr-name-invalid→aria/attribute-unknown;aria-valid-attr-value→aria/attribute-value-invalid(the IDREF half isaria/reference-missing);duplicate-id-aria→aria/owns-conflict;aria-allowed-attr→aria/attribute-not-allowed;aria-prohibited-attr→aria/attribute-prohibited;aria-required-parent→aria/required-parent-missing;aria-tab-selected-stateandtab-no-aria-selected→aria/tab-selected-missing;aria-tablist-tabpanel→aria/tabpanel-missing;aria-combobox-options→aria/combobox-popup-missing; frommodern-attribute-misuse→popover/target-missing,popover/target-invalid,inert/dialog-inert. Intended differences (details in the changelog ofa11y-rulesand at the entries inSHARED_RULES): context and required parts are checked on the DOM –ul[role=tablist] > li > a[role=tab](#715) now reports, like axe, missing required parts on the tablist and missing context on the tab; allowed and prohibited attributes also judge by the implicit role (<div aria-expanded>is a finding); required parts only for containers with an explicit role, the native table with only<caption>is no longer a finding; missing selected tab and missing tab panel are review hints, the tab hint appears once on the tablist instead of per tab; unknown values ofaria-currentandaria-invalidare not a finding; the visiblerole="menu"withinertno longer is one.modern_attributeskeeps the missing name of open dialogs, menus and popovers, the open popover withinertand the focus inside an inert subtree. Chrome’s own role names no longer reach the shared rules (CdpDocument):imagebecomesimg, the capitalized ones (LayoutTable*,DescriptionList,LabelText, …) become “no role” – otherwiserole="img"was left without an attribute judgment and a layout table aborted every context check above it. New taxonomy entrya11y.tab_selected.missing; the other identifiers point to the entries of the superseded rules, whose legacy identifiers continue to resolve. Explanations and detection corpus are updated accordingly. Verified with unit tests and the detection corpus (Chrome), including the #715 case in the iframe. Reference bands bundesregierung.de (35–65), berlin.de (15–48) and dm.de (15–48) re-rated: collapsedaria-controlswithout a target is no longer a finding (dm.de), tab selection only once per tablist (ARIA SHOULD), Swiper lists aslists/invalid-structure(Medium) instead ofaria-roles(High) — a11y-rules 0.14.1 catchesli[role=group]for this again. -
False alarms from barrierlab.eu and geographia.eu (#725-#728):
display/text-hiddenreported the text layer of visualizations in inactive section panels (hiddenon thesection) as withheld; the whole figure including the graphic was hidden, though. A figure that is not rendered now also does not count as a violation withhidden/aria-hidden/inerton the figure or an ancestor (#725; the sr-only assumption in the issue did not hold,checkVisibilityalready let the clip pattern through).landmark-uniqueand the top-level checks countformandregionas a landmark only with an accessible name (#727). The counting landmark rules (landmark-unique, duplicate banner/contentinfo) read a tree without excluded subtrees; the JSON names the removed landmarks asexclusion.excluded_landmarks, and the PDF note does so too (#726).form-no-submitnow reports a form withoutaction, without a text field and without a submit element (only script can submit it, typically a toggle for content) only as a low review hint instead of a 3.2.2 violation (#728). New corpus casesdisplay_modes_hidden_panel,form_toggles_without_submit; detection corpus green; cross-check against both live sites without the false findings. -
1.7.2, 2026-09-30: False-alarm corrections and gaps from the axe cross-check of the barrierlab.eu survey (21 EU portals) and from geographia.eu: target size only for visible targets in the final layout (#705, #706), exclusions also in the screen reader layer and in the cache (#703, #708), display rules without a legal verdict (#704),
mainand skip link behind an open dialog or cookie banner (#709, a11y-* 0.13.5), link color only in body text (#710), motion only with evidence (#712), title-only and duplicate description as best practice (#711, #713). New: contrast in shadow DOM and across float containers (#716), rulescrollable-region-focusable(#717), element-level rules in iframes including frame coverage in the JSON (#715, partial; frames in other processes follow in #720), lower weight forzoom/viewport-missing(#702). Reference run (reference_sites_test) and detection corpus green. Details in the entries below. -
Rules run in iframes (#715): A
role="dialog"without a name in an iframe (gov.cy) went undetected becausegetFullAXTreeand the shared DOM rules saw only the main document; axe checks every frame. New is a frame pass (audit::frames): for every iframe rendered in the page’s process (also nested) it fetches the AX tree viaframeIdand builds its own document from thecontent_documentof the sameDOM.getDocumentcall, then the element-level tree and shared rules run there (names of dialogs, images, links, buttons, form fields; roles including required parents/children; list and table structure; referenced duplicate IDs;aria-hiddenfocus etc.) — via an explicit allowlist. Page-level rules (landmarks,h1, title, viewport, skip link,bypass,region) remain reserved for the main document, as in axe. Findings carry the selector"{iframe} [frame] {element}"and aframe:node identifier, exclusions (#645) apply here as well. Skipped are hidden frames (hidden,aria-hidden,role=none, invisible, at most 1 px, ignored in the AX tree), excluded and out-of-process (cross-origin) frames;execution.framesin the JSON lists checked and skipped frames including the reason (cross_origin,hidden,excluded,ax_tree_failed,document_unavailable) per viewport. The JavaScript scaniframe/same-origin-contentnow checks onlyhtml-has-lang, its other checks are covered by the pass. New detection corpus caseiframe_widget_rulesand a Chrome integration test that also proves that no page rule reports inside the frame. Still open is the tablist made oful/li(magyarorszag.hu): Chrome flattens thelibetween tablist and tab in the AX tree, so the tree-based rules see a valid structure there — also in the main document. Live on gov.cy the dialog sits in an out-of-process frame (digital-assistant.gov.cy,gov.cyis a public suffix): it now appears in the report as skipped withcross_origin; it will be checked only with a dedicated CDP session per out-of-process frame. -
Screen reader exclusions survive the cache (#708): With
--reuse-cachethe screen reader report is rebuilt from the stored AX tree; the nodes excluded in #703 were back in the sidecar and in the PDF afterwards. The excluded node IDs now live in the cache entry (snapshot.json,screen_reader_excluded_node_ids) and are applied again on rebuild. Older entries without the field behave as before. -
Contrast in shadow DOM and across float containers (#716): Two gaps compared with axe. (1) The contrast check ran only over the light DOM; text in web components (cookie banner
p-cookie-banneron verwaltung.bund.de, 3.17:1) was missing. It now goes through open shadow roots, the background is determined across the composed tree (slot, shadow host), text directly under a shadow host takes color and font from its slot (without a slot it is not rendered and not checked),aria-hiddenon the host acts inward, and the selector readshost >>> inner(also in the pixel probe). Overlay detection now also sees positioned siblings that contain an image (hero image as<p-responsive-image>), up to six levels up; the pixel probe reports covered text (banner over the text) as a review hint instead of measuring it against the banner. (2)__amsIsVisuallyHiddenconsidered every ancestor without height hidden; adivthat contains only floats is 0 px high, though, and shows its content. Only a box that clips its overflow hides something without area; what is not rendered is detected bycheckVisibility(). As a result the 4.46:1 link on slovensko.sk is reported (axe: 4.45:1; the comparison against the threshold was already unrounded). The helper is also used by design quality, journey and the media rule. Live: bund.de reports the privacy link and the white hero text over the photo (pixel probe 3.64:1), slovensko.sk the link. New detection corpus casecontrast_shadow_and_inline. -
Scrollable regions without keyboard access (#717): New rule
scrollable-region-focusable(2.1.1, A) →a11y.scrollable_region_focus.missing: a visible element withoverflow: auto|scrollthat overflows by more than 13 px (like axe), contains text and is focusable by keyboard neither itself nor via a descendant. Chrome has made such regions focusable itself since version 130, other browsers have not — so it remains a finding. New detection corpus casescrollable_region_focusable. -
Weight of
zoom/viewport-missing(#702): Desktop browsers ignore the viewport meta tag, zooming by gesture remains possible; the consequence affects only mobile devices. The score deduction drops from 2.5/5 to 1.5/3, report and explanation name the consequence (desktop width, shrunk, horizontal scrolling when zooming in). The finding level (FAIL) and severity still come froma11y-rules; whether it should be a review hint there is a question for barrierlab. -
Color as a link cue only in body text, motion only with evidence (#710, #712):
link-in-text-block(1.4.1) now checks a link only when it sits in body text — like axeisInTextBlock: the section of its block (delimited by<br>/<hr>) must contain more non-link text than link text, and at least two words. Links innavor menus and logo links (image/SVG in the link, logo container) drop out. As a result, navigation, header, footer and logo links no longer report a finding (12 of 21 EU portals, axe confirmed none); the link in a paragraph remains a finding.prefers-reduced-motion(2.3.3, AAA) no longer reports everytransition/animation, but only motion — animations whose@keyframeschange transform/translate/scale/rotate, position or margin, and transitions of such properties (allonly if a:hover/:focusrule sets it) — that no@media (prefers-reduced-motion: reduce)block disables for the same or the universal selector; rules underno-preferencedo not count. Color and opacity transitions never count. The message names the evidence and the AAA level; AAA was already neither a legal signal nor highly BFSG-relevant, a test now secures that. New detection corpus caseslink_in_text_block_context,reduced_motion_colour_only,reduced_motion_transform,reduced_motion_override. Only motion whose selector hits a rendered element of the page is counted (bundesregierung.de: keyframes of a player spinner that is never included). -
title-only and duplicate description as their own best-practice rules (#711, #713): The
titleattribute as the only description of an interactive element was reported asa11y.hover.content_visibilityunder 1.4.13, although the browser tooltip is exempt there; it is nowtitle-only-description→a11y.title_only_description.weak. An element whose name and description are identical was reported asa11y.interactive_name.missing, although it has a name; it is nowdescription-duplicates-name→a11y.description_duplicates_name.redundant. Both arebest-practice, anchored to 4.1.2 (titleis a valid name source per accname, 2.5.3 applies only to a visible label), havebfsg_relevance: lowand never a legal flag —is_convention_rulekeeps a list of best-practice identifiers alongside thedisplay/*rules for this. 1.4.13 now reports only orphanedrole="tooltip"elements,interactive_name.missingonly elements without a meaningful name. New detection corpus casename_description_best_practice,forms_and_miscextended by an orphaned tooltip. -
a11y-rules 0.13.5 (#709): The skip link is now also detected behind the links of a cookie banner when it points to the start of the main content (bund.de, casoon/barrierlab#26). If a modal dialog is open (for example a consent dialog that hides
<main>viaaria-hidden),landmarks/main-missingis a review hint “gemessen hinter einem offenen Dialog” (“measured behind an open dialog”) instead of a violation (#709: five of 21 EU portals), also for a dialog withoutaria-modal(administracion.gob.es). Likewisebypass(“keine Ueberschriften”, i.e. “no headings”) behind an open dialog becomes a review hint. Reference band gov.ie re-rated (80–98): the ten link color findings counted up to 1.7.1 were standalone list links, false alarms after #710. -
Target size measures only visible targets in the final layout (#705, #706):
target-size-minimum(2.5.8) andtarget-size(2.5.5) now count an element as a target only if it is visible and clickable: not hidden percheckVisibility()(withopacityProperty,visibilityProperty; deliberately withoutcontentVisibilityAuto, so that sections outside the viewport remain measured), not in[inert], withoutpointer-events: none— as already with the equivalent link. This applies to the measured target and to the neighbors of the spacing check; links in a closed<details>(Chrome keeps their box, hides it viacontent-visibility: hidden) made three links in the footer and in a list a finding on geographia.eu. WithoutcheckVisibilitythe previous size filter remains. In addition, after the stability check every viewport pass waits for running finite CSS animations and transitions (document.getAnimations(), infinite ones are ignored), bounded by a second--stability-budget-ms; an animation whose remaining time exceeds the budget is not waited for at all. A target that is still animating afterwards, itself or via an ancestor, is reported by the rule as not measured (untested) instead of with its intermediate size: the logo intro on geographia.eu/atmosphere/ appeared as 3×39 px in the report, once finished it measures 147×39 px. New detection corpus casestarget_size_hidden_neighboursandtarget_size_animation; against the state before the fixa#beside-detailsanda#slowfail. Verified withcargo test, Clippy and the detection corpus (Chrome). -
Display rules no longer decide a legal verdict (#704):
display/text-hiddenno longer reports a[data-viz-text]hidden via CSS,hiddenoraria-hiddenas a violation if a rendered, reachable element of the samefigure[data-viz](or the figure itself) references it viaaria-describedby/aria-details: accname 1.2 also computes the description from hidden, directly referenced content (ARIA15 satisfies 1.1.1). Instead, a review hint with low severity (“nur als Beschreibung, visually-hidden empfohlen”, i.e. “only as a description, visually-hidden recommended”).inertremains a violation. Alldisplay/*rules are best practice of the display convention: they setbfsg_relevanceto at mostlowand no longer count aslegal_flags(page and batch verdict,passedin the JSON); a sharedNormalizedFinding::is_legal_flagreplaces the identical filters. Deliberately only fordisplay/*(taxonomy::is_convention_rule), not generically via thebest-practicetag —region,link-as-buttonandredundant-rolekeep their classification.display/toggle-missingnow says “kein mit[data-display-toggle]markierter Umschalter gefunden” (“no toggle marked with[data-display-toggle]found”) instead of claiming that one cannot toggle. Evidenced by the geographia.eu case (detection corpusdisplay_modes_described_text). -
Exclusions also apply to the screen reader layer (#703): Nodes in
--exclude-selector/[data-audit-exclude]subtrees (#645) now also drop out ofscreen_reader.issuesand thus out ofbfsg_complianceand therisk.legal_flagsderived from it (#484). Location is determined via the backend node ID of the AX node, as with the tree rules (ExclusionScope::excludes_ax_node). A finding is dropped only if all its nodes are excluded; otherwise it remains with the other nodes. Findings without nodes (site-wide) always remain. Counted inexclusions.excluded_screen_reader_issues(also in the batch aggregate and in the PDF note); the PDF, which re-derives the findings in the run language, omits the same nodes. Evidenced on barrierlab.eu/tasks/ticket/(detection corpusaudit_exclude_screen_reader, which can checkscreen_reader_bfsg_verdictfor this). -
1.7.1, 2026-09-30: First step of moving the rules to barrierlab (casoon/barrierlab#13): 21 identifiers come from
a11y-rules0.13.2, the superseded own rules are deleted (#690, B0). New findingszoom/viewport-missing(weighting follows in #702) andimages/alt-suspicious; the shared rules no longer check anything hidden via CSS. Reference run (reference_sites_test) and detection corpus green. Details in the entry below. -
Shared identifiers instead of own rules (#690, B0): More findings run through the shared set from
a11y-rules0.13.2 (SHARED_RULESinsrc/wcag/shared.rs); the superseded own rules are deleted, so that no finding appears twice in the report. Identifiers:meta-viewport→zoom/viewport-locked;document-title(missing/empty) →document/title-missing/document/title-empty, the meaningless title remains asdocument-title;aria-valid-attr→aria/reference-missing;aria-required-attr→aria/required-attribute-missing;aria-hidden-focusandfocus-order-semantics→keyboard/hidden-focusable(previously the same case twice, under 4.1.2 and 2.4.3);landmark-one-mainandlandmark-main-present→landmarks/main-missing(previously twice);landmark-no-duplicate-main→landmarks/main-duplicate;landmark-banner-present,landmark-navigation-present,landmark-contentinfo-present→landmarks/*-missing, now as a review hint instead of a violation;svg-img-altandimage-alton<svg>→svg/name-missing;image-alton<img>→images/alt-missing(image-altremains forrole="img"on other elements and the icon heuristic); link and button without a name fromcontrol-missing-label→links/name-missing/buttons/name-missing; the skip link detection frombypass→keyboard/skip-link-missing(review hint, recognizes the skip link by its target instead of by a word list).bypassnow reports only a page with no headings at all; the combined message “neither skip link nor main” is dropped. New:zoom/viewport-missing(no viewport meta tag, 1.4.4) andimages/alt-suspicious(file name, filler word or one or two characters as alt text; review hint). The shared rules now run with computeddisplay/visibilityfrom a DOMSnapshot (run_full_inviaCdpDocument::rendered) and thus no longer check anything hidden via CSS; if the snapshot fails, they run without styles. An element without a counterpart in the AX tree counts as ignored (content of a closed<details>: geographia.eu otherwise got 22links/name-missing).skip-linkfromlandmark_granularis dropped, the case iskeyboard/skip-link-missing. User-agent shadow roots (date fields) no longer enter the shared DOM. Taxonomy, explanations and detection corpus are updated accordingly. Verified with detection corpus (Chrome) and a before/after run against 1.7.0 on eight live sites; every deviation is explained (rename, dropped double report, hidden via CSS, or new and justified), two false alarms found along the way fixed ina11y-rules0.13.2. -
Score calibration:
table_missing_captionis a clean page, 2026-09-30: The fixture sat in the band “exactly one Level-A High”; that finding was the false alarm from #659/#674 (implicit<tbody>under<table><tr>hid the rows from the required-child check). Since #680 the page carries only the caption review hint and, at 95, sits in the band ≥ 95; the tag run of v1.7.0 had failed because of it. -
1.7.0, 2026-09-30: New features: technician mode
--technician(JSON per page plusindex.jsonandfindings.jsonl, path filters--include-path/--exclude-path), display modes--display calm|text|visual|all(#653), exclusion of intentional examples viadata-audit-exclude/--exclude-selector, visible in the report (#645), and fully English PDF reports with--lang en. In addition the false-alarm corrections from #638-#659 and #673/#674 as well as the restructuring (WP0-WP8, output unchanged per golden harness). Crate metadata:documentationpoints to https://casoon.github.io/auditmysite/,homepageto https://auditmysite.casoon.de/. Details in the entries below. -
Refactoring API surface (WP8), 2026-09-29: Pure restructuring without changes to output or public library API. The 199 places that the lint
unreachable_pubreports (158 in the library, 41 in the binary) are narrowed per compiler suggestion topub(super)(140) andpub(crate)(59) respectively — they were invisible to library users anyway; reachablepubitems remain untouched (semver/Studio, 1.7).lib.rsandmain.rsnow set#![warn(unreachable_pub)]. The 100 comparisonsi18n.locale() == "en"now go through the existing helperoutput::localized::is_english; for this,output::localizedis no longer tied to the featurepdf(onlypickremains so). Verified: golden harness identical before/after, Clippy with both feature sets. -
Refactoring
audit/pipeline.rs(WP7), 2026-09-29: Pure move without changes to flow or output.src/audit/pipeline.rsis now the directorysrc/audit/pipeline/:mod.rskeepsPipelineConfig,run_single_audit,audit_pagewith both viewport passes, the rule runs and the artifact persistence;assembly.rstakes the synchronous post-processing (WCAG merging, viewport scores,aggregate_report, module runs, audit quality);throttled.rsthe throttled performance passes includingrecover_after_throttled_failureand the adoption of the LhMobile value. Inaudit_pageonly the verbatim duplications are extracted (the threeprepare_*_collectioncalls per pass, the screenshot match); order of exclusions (#645), display modes (#653) and journeys unchanged, a sharedrun_viewport_passdeliberately not introduced. Public paths (auditmysite::audit::{audit_page, run_single_audit, PipelineConfig}) remain. Verified: golden harness before/after identical,integration_testanddetection_corpus_test(--ignored) against real Chrome. -
Refactoring: module details and page health as directory modules (WP6), 2026-09-29: Pure restructuring without behavior change.
output/builder/single/module_details.rs(2,618 lines) is now a directory module with one file per module, mirroringoutput/pdf/detail_modules/:performance.rs,seo.rs,platform.rs(security, mobile),html_conform.rs,commerce.rs,dark_mode.rs,design_quality.rs,ai_transparency.rs,experience.rs(UX, journey); the orchestration (build_module_details_from_normalized) stays inmodule_details.rs. The inline computations in theSeoPresentationliteral are named functions (heading_summary,social_summary,technical_summary_rows,tracking_summary_rows,build_robots_presentation,build_image_efficiency_presentation,technical_issue_rows).seo/page_health.rs(3,128 lines) keeps types, text functions,analyze_page_healthand the URL analysis; new arepage_health/dom.rs(DOM inspection, local HTML validation),page_health/probes.rs(HTTP probes) andpage_health/issues.rs(collect_issues). All public paths remain (seo::page_health::collect_issuesviapub use). The renamerun_w3c_html_validation→run_local_html_validationwas already done with WP9. Verified with the golden harness (WP0) againstmain:diff -rempty. -
Display modes (
data-displayconvention), 2026-09-29 (#653): New modulesrc/display/and new option--display calm|text|visual|all. Without the option everything stays as before (page default). With a mode, a script injected before navigation (Page.addScriptToEvaluateOnNewDocument) writes the choice tolocalStorage.display;calmandtextadditionally emulateprefers-reduced-motion: reduce(Emulation.setEmulatedMedia), so that pages without the convention also show their reduced variant. BecausesetEmulatedMediareplaces the whole feature list, the dark-mode analysis (print, forced colors, dark contrast) now passes the base features through (analyze_dark_mode_with_base_media) — otherwise it would have cleared the reduced motion for the rest of the audit. JSON:audit_scope.display_mode(site_default|visual|calm|text) and per pagepages[].display_modes(offered modes, rendered mode,set_before_body, toggle, visualizations by kind, reduced motion); PDF: rows “Darstellungsmodus”/“Darstellungsmodi der Seite” (“Display mode”/“Display modes of the page”) in the methodology appendix, in the batch on the cover page.--display allchecks each mode as its own run with its own report (suffix-calm/-text/-visual), never a mixed score;visualonly for pages withfigure[data-viz="3d|interactive"]from thecalmrun, with a doubled page timeout. Findings are not marked as “in all modes” — for that the runs would have to be merged.New rule group
display/*(best practice, no WCAG requirement, anchored to 2.2.2 and 1.1.1 respectively; own taxonomy entries and explanations):display/toggle-missing,display/init-missing(via an observer that records, when<body>is inserted, whetherdata-displaywas already set),display/text-media-visible,display/text-not-visible,display/text-hidden. The text mode checks follow the mode actually rendered. Candidates for moving to barrierlab: the static halves oftoggle-missingandtext-hidden(attribute part =viz/text-hiddenof the draft). Corpus fixturesdisplay_modes_conforming/display_modes_violations, integration testdisplay_text_sets_stored_choice_and_reduced_motion(localStorage andmatchMediabefore the first script and after the audit).Live against geographia.eu:
--sitemap .../sitemap-index.xml --display calm -m 10266 s, 10/10 pages, no pool timeouts (the first 10 URLs are text pages without visualization). Ten pages with visualizations via URL list:calm1151 s, 7/10, 0 pool timeouts, but 3 pages withinteractiverun into the 120 s audit limit;text293 s, 10/10, 0 timeouts. Findings: on all pagesdisplay/toggle-missing(no[data-display-toggle]shipped); incalm/visualdisplay/text-hidden, because.viz-text { display: none }removes the text layer outside oftextfor screen readers as well (confirmed in the browser); intextdisplay/text-not-visibleon pages without[data-viz-text](home page 4, explanation lab 10). -
English report: filler words as topics, misleading validator title, 2026-09-29: Finding from a scan of the English Typst outputs of the golden set (17 pages). (1) The batch report listed the entry “nicht” (“not”) under “Dominant content topics” (“Present on 2 audited pages”). Cause:
seo/topics.rsfilters page title, description, headings and text excerpt againsttopic-stopwordsfrom the FTL files, and these lists contained only some of the function words — “nicht” (“not”) (barrierlab.eu, casoon.de), “weitere” (“further”) (berlin.de), “dein”/“dich” (“your”/“you”) (hornbach.de, otto.de) and “neue” (“new”) (volkswagen.de) slipped through as page topics. Both lists extended by common function words (negation, auxiliary and modal verbs, pronouns, conjunctions, prepositions) with at least four characters; shorter ones the code filters anyway. Real topic words remain. (2) The callout on HTML validation was titled “W3C HTML validator”/“W3C HTML Validator”, although the check runs locally with html5ever and never calls the W3C service. Now “HTML validation (local, html5ever)” and “HTML-Validierung (lokal, html5ever)” respectively; the FTL key is calledpdf-ph-html-validator-title. (3) The German rows of the HTML validation table in the English PDF had already been fixed with #671. (4) The terminal output showed “Certificate: SEHR GUT” (“very good”) with--lang en. The certificate in the JSON deliberately remains the canonical German token (#449: key for badge/color, fixed via enum in the Studio contract schema, checked by report-lint and evaluated by rankinglab); only the display is localized. (5) The validator callout compared the localized status with “Fehlgeschlagen” (“Failed”); in the English PDF (“Failed”) a failed validation was therefore shown as info instead of as a warning. The presentation now carries the canonical status (executed/failed/skipped), and the callout decides on that.certificate_label_localizednow lives inregistryinstead of the PDF cover so that the terminal uses it too: with--lang enit now reads “EXCELLENT”. Likewise the “Certificate” row in the “Audit scope” box of the English batch report showed the German token (“AUSBAUFÄHIG”, i.e. “room for improvement”); it now uses the same function (“INADEQUATE”).Changes the output: page topics (
topic_terms,top_terms, topic overlaps) in the JSON and in both PDF languages, where a page had a function word among its five topics; title of the validator callout in both languages; certificate row in the English terminal and in the English batch “Audit scope” box. The JSON fieldcertificateremains unchanged. Verified with the golden harness againstmain: differences only at these places, German Typst verbatim identical except for validator title and topic list. Unit tests against function words as topics and against umlauts in the English certificate labels. -
document-titledouble-counted, 2026-09-29: A missing or empty page title appeared twice in the report, once from the AX checkcheck_page_titled(nodedocument, without selector) and once from the DOM checkcheck_page_titled_with_page(selectorhead). Authoritative is now the DOM check alone: Chrome fills the name of the root node with the URL when the title is missing, so the AX check could not decide this case itself and already referred to the DOM check before. Everything it reported as a violation (empty, missing, generic title) the DOM check reports as well; the AX check is removed together with its tests (public functionwcag::rules::check_page_titledis dropped).empty_titlepins 1 occurrence, the integration test onparity_gaps.htmldoes too. -
Tables: ignored and not-yet-rendered rows (#654, #659), 2026-09-29: (1)
aria-rolesreported on og-vanilla.casoon.dev (/accessibility,table.keys) “role ‘table’ is missing required child roles: row, rowgroup” for a table withtbody > tr. Chrome marks a plain<tbody>as ignored, the rows hang below it; the check of the required child roles saw only direct children. It now looks through ignored nodes (same pattern as #638). A table without a row (onlycaption) is still reported. (2)th-has-data-cellsreported the header cells of therole="grid"grid in a shadow root (/columns,/accessibility), although every column has data. Reproduced via CDP, the capture came before the data arrived: the grid keeps 40 pool rows withdisplay: nonein the DOM until the worker delivers (around 300-500 ms afterload); Chrome lists them as ignored withnotRendered. The stability wait does not see mutations in shadow roots and reported the page stable after 255 ms. If a table without data cells contains such not-rendered rows at row position (directly under the table, under a rowgroup or an ignored<tbody>), the result now counts as undetermined (incomplete) instead of as a violation. Hidden content inside a header cell does not count; a table with only a header row is still reported.New corpus fixtures
table_required_rows_tbodyandtable_grid_rows_unrendered(shadow DOM grid with waiting and rendered rows respectively, table with only a header row as a violation) and unit tests in both rules. -
Technician mode: single-page JSON to fix things instead of a report to read, 2026-09-29: New for people who work through findings:
--sitemap URL --technician -o DIR/(likewise with--url-file/--crawl) writes the regular single-page report as JSON per page and next to it two flat files.index.jsonlists every attempted URL in input order — file name ornull, statusok/blocked/failedwith reason, overall and accessibility score, number of findings and occurrences,audit_quality. Blocked (bot wall,AccessBlocked) and failed pages appear only there, without a placeholder file; for this,BatchErrornow carriesblocked_reason(not serialised, batch JSON unchanged).findings.jsonlcontains one line per occurrence across all pages (url,sourcewcag/journey/seo/html_conform,rule_id,wcag_criterion,level,severity,selector,location,message,fix_suggestion,viewport_tags), complete — the page file caps its example occurrences per finding at five. Both files are canonically English (#406), schemas indocs/technician-index.schema.jsonanddocs/technician-finding.schema.json. Every run with--per-page-reports -f jsonwrites them.--technicianstands for--per-page-reports -f json --no-screen-reader-report --seo --html-conform: accessibility (incl. keyboard journeys), HTML conformance and SEO, no throttled performance runs, no mobile/security/tech stack. Every page file states this scope inexecution.scope/module_runs. Explicitly set flags win:-freplaces the format,--full/--performance/--mobile/--securityenable their modules as usual. The new flags can also be used on their own:--include-path/--exclude-path(repeatable, glob on the decoded URL path:*/?within a segment,**across segments,/**/also as a single/; takes effect before-m;sample.selectionthen becomespath_filter),--no-screen-reader-report(no*-screen-reader-audit.json, also in single mode) and--html-conform(HTML conformance without--full).Not in
findings.jsonl:accessibility_assessments(hints/manual check items, not violations). The derived indicator modules (UX, Journey, Commerce, Content Visibility, AI Visibility, Source Quality, Dark Mode) keep running because they hang offcheck_seoor are tied toPipelineConfig; switching them off would need newPipelineConfigfields. -
3.2.2 On Input: only real context changes are violations, 2026-09-29 (#657): On og-vanilla.casoon.dev (
/filtering,/sorting,/localization)a11y.on_input.riskreported selects for filter preset, sorting and language as “may trigger navigation”, just because their name contained “filter”/“sort”/“language” and the page has no submit button. But the selects only update the grid next to them — a content change is not a change of context. Now only what the inlineonchangehandler (or the global function it calls directly) visibly does is a violation: navigation (location…), submitting a form (.submit(/.requestSubmit(), a new window (window.open() or a focus shift (.focus(). A handler whose effect cannot be read off, and a name that merely sounds like navigation (language, country, region, navigate, redirect, go to), become a check warning instead of a violation; “sort” and “filter” disappear entirely as a hint. The classification now lives in Rust (evaluate) and is unit-tested. New corpus fixtureon_input_context_change(passes: filter without handler; check: content-changing handler, language select; violation: handler navigates via a called function, handler submits a form). -
1.3.5 Identify Input Purpose: the “name” of a thing is not a person’s name, 2026-09-29 (#658): On og-vanilla.casoon.dev/saved-views,
#view-name(label “Name”, the name of a saved grid view) counted as a field for the user’s name because the label contained “name” as a substring. “name” is now classified word by word (split at punctuation and camelCase): a preceding word that is neither a person nor a technical id prefix (“view name”, “project name”, “company name”), a following “of/for/der/des/für/von” (“Name der Ansicht” (name of the view)) and compounds like “Dateiname”/“Filename” (file name) exclude the field; “Name”, “Your name”, “Full name”, “Vorname” (first name), “Nachname” (last name), “Ihr Name” (your name) remain hits. A thing qualifier inidor thenameattribute excludes a bare “Name” label, unless the other attribute names the person. The detection words are English and German merged (as withmedia_alternative), independent of the output language. New corpus fixtureinput_purpose_name. -
Exempt deliberately broken examples from the audit, visible in the report, 2026-09-29 (#645): Pages that teach accessibility deliberately show faulty examples (barrierlab.eu,
/tasks/ticket/: unlabelled fields, adivas a button). auditmysite reported them as violations of the page itself. New, modelled on axe-core’sexclude:--exclude-selector <CSS>(repeatable),[audit] exclude_selectorsinauditmysite.toml, and the always-honoured attribute[data-audit-exclude]. What is excluded is never a page and never a rule, only findings whose element lies in an excluded subtree — the page itself is checked completely, page-wide findings always remain.Implementation (
src/audit/exclusion.rs): per viewport pass, oneRuntime.evaluatecounts the hits of each selector (invalid selectors are detected); only when there are hits,DOM.getDocument+DOM.querySelectorAllfetch the backend node IDs of all nodes in the hit subtrees (incl. shadow roots, frame and template content). Filtering happens per rule inrun_rules, before its execution note is counted, and before enrichment and element screenshots: findings from the AX tree via the backend ID of their AX node, findings of the shared DOM rules via the newly carried backend ID (Violation::backend_node_id, in memory only; set in the adapterwcag/shared.rs, nothing changes in barrierlab’s rule code), JavaScript page rules, contrast and journey findings via their selector — excluded only if it hits at least one element and every one of them lies in the excluded subtree; an ambiguous or unparseable selector keeps the finding. Pattern findings go through the same filter.Visibility: the JSON carries per page
pages[].exclusions(applied selectors with hit count — also 0 and invalid —, excluded occurrences and confirmed violations in total and per rule, excluded journey findings; per rule the larger value of the two viewports), the batch additionallysummary.exclusionsas a sum. The PDF names selectors and numbers in the methodology section, the batch in the audit frame of the cover page (de/en via Fluent). A default run withoutdata-audit-excludeon the page stays silent in the PDF, the JSON lists the built-in selector with 0 hits. Cache format 19; the selectors go into the audit signature.Caps of the JavaScript rules: many page rules report at most N locations (10 for
click-events-have-key-events, 20 forlink-as-button, 250 for the ARIA rules, 5 for target size, obscured focused elements, language changes, among others). Without a countermeasure, example hits would have used up the cap and let real hits behind them disappear silently — exactly what the feature is meant to rule out. Therefore the exclusion step putswindow.__amsIsExcluded(el)into the page per pass (the hit roots in aWeakSetin the closure, no DOM attribute, no change visible to other rules). The shared building blockCSS_SELECTOR_JS, which every locating rule includes, brings__amsIsExcludedEl,__amsPushand__amsRealwith it: real and excluded hits are capped separately, the loop limit reads only the real ones. Excluded hits still come back and are filtered and counted like all others (per rule at most up to the same cap). Converted:aria_allowed_attr,aria_hidden_focus(whose total no longer counts excluded ones),aria_relationships,aria_roles(2),aria_required_attr,image_input_rules,on_focus,on_input,server_side_image_map,table_extended,widget_rules,click_handlers,content_on_hover,fake_navigation_link,redundant_role,use_of_color,language_of_parts,meaningful_sequence,target_size_minimum/_enhanced(also the candidate lists),focus_not_obscured_minimum/_enhanced(focus candidates, the 60 checked controls, the 5 findings),pause_stop_hide(widgets; the page-wide animation message ignores excluded elements entirely) andaccessible_authentication(cap moved from Rust into the script).identify_purposereports a field name instead of a CSS path — the script marks excluded fields itself (Violation::in_excluded_subtree, in memory only), the cap of 5 applies separately. Contrast: text in excluded subtrees no longer occupies any of the 60 slots for the pixel sample.rule_outcomes[].findingsnow counts what is in the report: the tree rules filter per rule inwcag::check_all_excluding(new;check_all_with_configremains as a wrapper), the page rules, contrast and HTML content model beforepage_rule_outcome; for the shared rules the counter taken over froma11y-rulesis reduced by the dropped findings of the same identifier.Still open: rules whose reported “selector” is not a CSS path and which do not mark their element themselves cannot lose excluded hits (known and fixed:
identify_purpose). Caps that only limit candidates for a page-wide statement (overlay search infocus_not_obscured_*, fields per form inredundant_entry) are unchanged.Tests: unit tests for filter, counting and PDF text (EN without umlauts), new corpus fixture
audit_exclude_specimen(one error per locating path — AX node, JS page rule, shared DOM rule — not reported inside[data-audit-exclude], the same error outside is reported) and an integration test for--exclude-selectorincluding a 0-hit and an invalid selector. In addition corpus fixtureaudit_exclude_cap: 12/22/6 excluded hits before one real one each (caps 10/20/5) — the real one is reported, andexcluded_hits_do_not_spend_a_capped_rules_budgetchecks the same including the exclusion count andrule_outcomes[].findings == 1. Counter-check: with__amsIsExcludedElswitched off, the test fails (div#real-clickis missing). -
4.1.2/3.3.2: expandable treegrid rows and native value fields, 2026-09-29 (#655, #656): (1) The accordion pattern treated every element with
aria-expandedas an accordion trigger and, on og-vanilla.casoon.dev/grouping, reported every group row of therole="treegrid"as “should be a button” (Medium, 12 occurrences).aria-expandedon a row ingrid/treegridand on atreeitemis the state of its own composite widget, whose keyboard contract (arrow keys, Enter) is provided by the grid or the tree; such nodes no longer count as triggers. An expandable row outside a grid is still reported.(2)
aria-required-attrcheckedaria-valuenowvia an AX propertyvaluenowthat CDP does not know — the current value is in the node’svalue, and Chrome invents one (50 for the slider, 0 for the spinbutton) when the author sets none. The check therefore fired on everyslider/spinbutton/meter/focusableseparator, including native<input type=range|number>and the internal day/month/year fields of<input type=date>(Critical; 16 occurrences on /filtering, /columns, /grouping, /theming). For the same reasoncheck_slider_has_value(“Slider is missing accessible value”) reported every slider: the extractor only reads text values, the slider’s number was dropped. Thearia-valuenowrequirement now runs as the DOM rulecheck_value_now_with_page(asaria-checkedalready does): it reads the attribute, traverses open shadow roots, exempts nativerange/numberand<meter>, and does not reach the user-agent fields of date inputs at all. The slider check inwidget_rules.rsis dropped; a customrole="slider"withoutaria-valuenowremains a violation.(3) The 3.3.2 heuristic “may require format instructions” skips nodes inside the Chrome roles
Date/DateTime/InputTime— the browser provides their fields and format. Thespinbuttonrole alone no longer triggers the hint: 3.3.2 requires instructions where the input must follow a format that cannot be inferred; a spinbutton — native<input type=number>as well as a customrole="spinbutton"— holds a number that the widget itself limits and changes stepwise with the arrow keys. Detection via the label (“Date”, “Postal code”) still applies to every role.(4) The AX extractor read
valueonly as a string; Chrome sends the value of slider, spinbutton, progressbar and meter as a number, which was lost as a result. Numbers and booleans are now preserved in text form. No WCAG rule readsAXNode.valueany more (the only one,check_slider_has_value, is dropped above); the only consequence is for the screen reader linearisation (a11y-perception): value elements without a name now carry their value and count as announced content in the announcement-desert measurement, which is what they are when read aloud.Verified live with the release build against og-vanilla.casoon.dev: no more accordion,
aria-valuenow, slider value or spinbutton format findings. New corpus fixturestreegrid_expandable_rows,value_widgets_native(pass),value_widgets_customandvalue_widgets_shadow(violation);aria_and_widgetsnow expects the custom slider underaria-required-attr.Follow-up on the same class of error: the remaining 1.3.5 keywords were also searched as substrings — “Hotel” counted as a phone field because of “tel”, “Sorting” would have contained “ort”. They now apply only as whole words (tel, zip, plz, fax, city, first, last …) or as known compound beginnings or endings (
telefon…,postleit…,birth…,geburts…,…adresse,…address,…strasse); “E-Mail” counts as one word. German fields like “Telefonnummer” (phone number), “Postleitzahl” (postal code), “Straße” (street), “Passwort” (password) are thereby recognised for the first time. Likewise for 3.2.2: the page-wide search for a submit button found “go” in “Google”, “Category” or “Logo” and thereby suppressed the check warning; button names are now checked word by word (submit, send, go, search, absenden, senden, suchen), the decision lives in Rust and is unit-tested. Corpus:#stay(“Hotel”) passes, “Telefonnummer”/“Postleitzahl” are violations; the On Input fixture has Google/Category/Logo buttons, the language select remains a check. -
landmark-uniquecounted twice, 2026-09-29: The rule ran twice, once over the AX tree (check_landmark_unique) and once in the DOM supplement (check_landmarks_with_page). Both reported the same elements with differently built selectors, so nothing was merged: the corpus caselandmark_granularcame to 22 instead of 11 occurrences,parity_gaps.htmlto 4 instead of 2. Only the AX check is authoritative now; it works with Chrome’s computed roles and names and covers every landmark that the DOM approximation sees (plus<section>with a name,form, and correct roles for nestedheader/footer/aside). The same applied tolandmark-main-present: a missingmainlandmark appeared twice in the report (rootanddocument). The DOM supplement had no coverage of its own: if the AX tree fails, the whole audit aborts; for mini pages with at most two AX nodes the AX check is silent on purpose; and a<main>in a shadow root was seen only by Chrome, not byquerySelectorAll, so the DOM check wrongly reported there. The DOM supplement (check_landmarks_with_page, page rule1.3.1/landmark-dom) is therefore removed together with its role derivation. The corpus can now pin the exact count viaoccurrences:landmark_granular11, the new caselandmark_unique_one_per_element4 (1.6.0: 6),landmark_aside_named_duplicate2,missing_main_landmark1 (1.6.0: 2); the new caselandmark_main_in_shadow_rootis a true negative.parity_gaps.htmlchecks the count in the integration test (1 missingmain, 2 duplicate navigations). -
Page Health: HTML validation in the JSON canonically English (#406), 2026-09-29:
seo/page_health.rswrote German text into the canonical JSON:html_validator_detail(“HTML5-Validierung lokal via html5ever” (HTML5 validation locally via html5ever)) as well ascheck/detailof allhtml_issues(“Doppelte IDs” (duplicate IDs), “3 (z.B. …)” (3 (e.g. …)), “HTML5-Parsing-Fehler” (HTML5 parsing error), “+37 weitere” (+37 more), “Leere Ueberschriften” (empty headings) etc.).reconcile_image_alt_countinaudit/pipeline.rseven compared against the German string “Bilder ohne alt-Attribut” (images without alt attribute). Now following the #406 pattern:HtmlValidationIssuecarries akind(HtmlValidationKind) and the raw values insamples(example IDs or the first parser errors);html_validation_check_text/html_validation_detail_text/html_validator_executed_textare the single text source, the analysis calls them withen=true, the PDF builder (builder/single/serp.rs) with the run language. Comparisons run viakind. The privaterun_w3c_html_validationis now calledrun_local_html_validation(it never calls the W3C validator).Changes the JSON output:
html_issues[].check/detailandhtml_validator_detailare English, every entry newly haskind, entries with raw values additionallysamples. The German PDF stays word for word identical; the English PDF now shows English text there instead of the previous German. Cache entries of the same version with old German text are reduced tokind+sampleswhen read in. Verified with the golden harness againstmain: differences only in these fields in the JSON and in the English Typst, German Typst and batch outputs unchanged; guard test against umlauts/German words in the EN output. -
2.5.8/2.5.5 Target Size: “Equivalent” exception for links, 2026-09-29 (#652): Both criteria exempt a target that is too small if the same function is reachable via another control on the same page that meets the size. This was missing: on geographia.eu (
/atmosphere/de/kapitel/hebel/) the 39×10 px small attribution line of the module logo (a.logo-main,href="/de/") counted as a violation, although the footer link “Alle Sphaeren im Ueberblick” (all spheres at a glance) (/de/#modules, 141×161 px) opens the same start page. Now a link that is too small passes if another link with the same target measures at least 24×24 (2.5.5: 44×44), is rendered and visible (checkVisibilityincl.visibility/opacity, not shifted off to the left of/above the page), has pointer events and does not lie in aninertoraria-hidden="true"subtree.The target is the resolved absolute URL. If the link leads to another document, the fragment does not count —
/de/and/de/#modulesopen the same page, the fragment only sets the scroll position. If it leads to the current page, it counts: there, jumping to the location is the whole function,#aand#bare different.href="",href="#"andjavascript:never count — they name no target. A link that is also too small is not an equivalent, even if it passes itself via the spacing exception (deliberately conservative). Buttons are left out, their function is not in the markup. The building blockhasEquivalentLinklives inTARGET_HELPERS_JS, both rules use it. The rule keeps no pass list, so the compensating element is not noted.New corpus fixture
target_size_equivalent(passes: small link with a large equivalent, also with a different fragment into another document; violation: only hidden/inert/invisible/ shifted equivalents, only too-small ones, different fragment into the own page,href="#", without equivalent) and an integration test that calls both rules directly. -
Batch: pool wait time and silently missing pages (#651), 2026-09-29: A batch over geographia.eu (
-c 2 -t 120, WebGL pages) lost 46 of 312 pages with “Browser pool timeout: no page available after 60 seconds”. Reproduced with 1.6.0 on 8 chapter pages: 3 of 8 were missing. Two causes: (1)BrowserPool::acquirecounts the slot before the new page is created; ifnew_pagefailed (Chrome under the WebGL load, CDP request times out), the semaphore permit and the slot were lost permanently — the pool had one page fewer for the rest of the run. Both are now returned, and page creation is limited to--timeout: when reproducing under load,new_pagestood without an answer, which 1.6.0 caught only via the 480 s attempt budget. (2) The wait for a free page was fixed at 60 s, but a page in progress may takemax(timeout, 30) * 4seconds (480 s at-t 120); the waiting page gave up although nothing was wrong with it, and in doing so also used up its retry. The wait now follows--timeout(page creation plus attempt budget plus 15 s for the reset, 615 s at-t 120), lies outside the page’s attempt budget and consumes no attempt. Pages that still get no browser page are retried one by one after the parallel phase, before the report is produced. What still fails stays undererrorsas before; new, the report says how many URLs the scores cover: JSONsummary.attempted_url_count(additive, next tourl_count), PDF a row “Bewertungsbasis” (basis of rating) in the audit frame and a note with the unaudited URLs in the status section (de/en), terminal a scope line. The score calculation is unchanged. Verified with unit tests (derivation of the wait time, only pool timeouts are deferred, report in JSON/PDF/terminal) and the Chrome integration testbatch_retries_pool_timeouts_serially(one slot, two workers, 1 s wait time: all three pages audited, each reported exactly once). Live with the same 8 chapter pages and-c 2 -t 120: 1.6.0 lost 3 (two pool timeouts after the slot loss, one audit timeout after 480 s), the fix audited 8 of 8 — albeit at lower machine load, the error path itself was not touched. -
Skip link and
role="list", 2026-09-29 (#642, #644): (1)region(1.3.1) reported the skip link<a href="#main">Aller au contenu</a>(Skip to content) on all French pages of barrierlab.eu, not on the English, German and Spanish ones. The exception depended on the link text: the check forhref="#…"compared with#, but Chrome delivers the resolved address asurl(https://barrierlab.eu/fr/#main), so only the phrase list applied, and that lacked French. Now behaviour counts, as with axe-core’sisSkipLink: a link to a fragment of the same page (address without fragment equal to the root node’surl) that comes before the first ordinary link. The phrase list is dropped; it also exempted every link with “springen” (jump) in its text. (2)redundant-role(4.1.2) reportedrole="list"on<ul>/<ol>withlist-style: none(1,142 occurrences on barrierlab.eu). WebKit/VoiceOver discards the list semantics for such lists, the role restores them. With computedlist-style-type: noneit now goes unmentioned; all other redundant roles are still reported. Verified with unit tests, two new cases in the detection corpus (skip_link_language,redundant_role_list_style, each with a counter-example that is still reported) and live runs against barrierlab.eu/fr/ and /en/. -
Contrast for gradient text, #640, 2026-09-29:
a11y.contrast.weakreported a violation with 1.00:1 for the logo links on geographia.eu (background-clip: textwith gradient,color: transparent). That was not a measurement: the transparent text colour was computed against the background and yielded the background itself. Style capture now setsforeground-uncertainif the element or an ancestor carriesbackground-clip: text(also-webkit-) orcolor/-webkit-text-fill-coloris (nearly) transparent. Such texts go into the report as a check note (warning) withoutcontrast_ratioevidence and are not resolved by pixel sampling, because that needs the CSS text colour. In addition, a set, opaque-webkit-text-fill-colornow counts as the text colour (contrast calculation and pixel sampling), since browsers paint the glyphs with it, not withcolor(corpus casetext_fill_color_contrast: light fill colour with darkcoloris a violation, the reverse passes). Verified with unit tests and the corpus casegradient_text_contrast(gradient text hint, grey body text still a violation); live run against geographia.eu/atmosphere/de/kapitel/hebel/: both 1.00:1 violations are hints, there were no further contrast findings on the page, neither before nor after (accessibility 75 → 86, overall 74 → 79). -
Heuristic form findings, 2026-09-29 (#643): Two guesswork rules reported correctly built forms on barrierlab.eu. (1) “Input may require format instructions” (3.3.2,
label) accepted an accessible description only if it contained a format word like “Format:” or “z.B.” (e.g.); the date field of the sample form witharia-describedby(“Day of travel”) failed. In addition, the term “pass” (passport) hit, as a substring, the label “Was ist passiert?” (What happened?) of the contact textarea. Now every description counts as an instruction, terms under five characters (pass,tel,date,zip,plz,ssn) count only as a whole word, and the finding is a check note (as_warning) instead of a violation, because the need for a format is only guessed from the label text. (2) “Grouped form controls may be missing a fieldset/legend” (1.3.1,form-field-group) demanded a group for every checkbox as soon as the page had two radio/checkbox elements anywhere — on /tasks/bill/ and /tasks/appointment/ this hit the single checkbox next to a correctly grouped radio toggle. Checkboxes belong together via a sharednamein the same form; the AX tree does not carry that. The check for checkboxes therefore runs as a DOM page rule (check_checkbox_group_with_page): only from two visible checkboxes of the same name is afieldset/role=groupancestor required. Radios stay unchanged in the tree (a radio always needs a group). New corpus casesform_heuristics_cleanandform_heuristics_flagged. -
--per-page-reports: one file per page, 2026-09-29: The file names of the single reports came only from the host (casoon-de-<date>-single-report.json); every page of a website overwrote the previous one, a sitemap with three pages left one file. The name now contains host and path (casoon-de-arbeitsweise-…), with query strings a short stable hash. Applies to all formats; single audits without--per-page-reportskeep their name. -
Two false alarms on geographia.eu (#638, #639), 2026-09-29: On geographia.eu/atmosphere/de/kapitel/hebel/ 1.6.0 reported two violations of 1.3.1 that are none. (1)
th-has-data-cells(8 occurrences, high): Chrome puts<thead>into the AX tree as arowgroup, but marks the plain<tbody>as ignored; rows and cells still hang below it. The rule skipped ignored nodes together with their subtree, thus found not a single data cell and reported every column header. Empty cells andaria-hiddenchildren played no role. Now the search descends through ignored nodes but does not count them itself. (2)landmark-unique(2 occurrences, medium): the DOM supplement to the landmark rules derived the role from the tag and made every<header>abanner, also the chapter<header>in<main>. According to HTML-AAM (and in Chrome’s AX tree),<header>/<footer>insidearticle,aside,main,nav,sectionor the corresponding roles are generic; the DOM supplement now follows this. The same held for<aside>: insidearticle,aside,navorsection(or the rolesarticle,complementary,navigation) it iscomplementaryonly with an accessible name, otherwise generic;role=regiondoes not count there, an unnamed<section>does (that is how Chrome computes it). For this the DOM supplement also takestitleinto account as a name. Confirmed in the live run: both findings gone, the other four unchanged, accessibility score 75 to 85. New corpus casestable_headers_tbody_ignoredandlandmark_header_in_main,landmark_aside_scoping(true negatives) andlandmark_aside_named_duplicate(true positive);table_headers_no_dataandlandmark_granularsecure the existing true positives. -
English PDFs without German table labels, 2026-09-29: With
--lang en, the tables for security headers (“Vorhanden”/“Fehlt” (present/missing)), SSL (“Gueltiges Zertifikat” (valid certificate), “Laeuft ab in … Tage” (expires in … days), “Chain-Laenge” (chain length)), touch targets (“Zu klein” (too small), “Zu eng beieinander” (too close together)) and font (“Kleinste Schrift” (smallest font), “Lesbarer Text” (readable text)) contained German labels, found in an English casoon.de report. The labels now follow the run language; a guard test with the module data of this run checks the English output for German terms. -
Cache round trip and deterministic order, 2026-09-29: While building the golden render harness, two errors were noticed. (1)
GraphEntity.propertieswas omitted withskip_serializing_ifbut carried nodefault: a cachedreport.jsonwith an entity without properties could no longer be read (“missing fieldproperties”), and the CLI silently re-audited. 13 of the 17 frozen cache entries were affected. The same gap existed inBatchReport.errors, the four lists inSitemapDiagnosticsand the three inCrawlDiagnostics; all now carrydefault. New round-trip tests serialise and read a completeAuditReportand aBatchReportwith empty lists. (2) Two runs over the same input could yield different reports because results came fromHashMaps without complete sorting: on ties, the order and (after truncating to 10) the content oftop_recurring_rulescould change; schema conflicts in the batch, the interactive categories including the PDF table “Befunde nach Kategorie” (findings by category), the dominant rule of the summary, the main role in the action plan, template clusters, duplicate content, minification deviations and the sitemap HTTP findings (completion order of the requests) had the same gap; the penalty points of the accessibility score were summed inHashMaporder. Every sort now has a final unique key (rule ID, entity ID, category, selector, URL), the penalty points are summed in rule ID order. Tests pin the order on ties. Verified: three golden render runs over all 17 pages,diff -rempty. -
1.6.0, 2026-09-29: Collective version of the stability and accuracy work since 1.5.1 (blocked pages, comparison with the rankinglab corpus; details in the entries below). Dependencies raised to the versions published in the process:
a11y-rules,a11y-dom,a11y-report,accname0.12.2 (list rules see through<slot>,<ul role=listbox>is not a list) andhtml-conform0.3.1 (brings the vnu-closer checks from 0.3.0:imgwithoutalt, interactive content ina, further parser errors; plusnamenext to RDFapropertyon<meta>). HTML conformance values can therefore drop. -
Findings of the report-lint check across 120 rankinglab reports, 2026-09-29: 8 reports failed. (1) The source quality signal “Bedienelemente benannt” (controls named) counted all raw 4.1.2 and 1.1.1 violations, the lint check all normalised ones;
aria-hidden-focusandaria-prohibited-attrnow carry 4.1.2 only in normalised form, and both counts contradicted each other (5 reports). In substance both were too broad: duplicate IDs or prohibited ARIA attributes are not a missing name.taxonomy::is_missing_name_or_roleis now the one definition for blocker, signal and lint; the signal maps raw violations onto the taxonomy like the normalisation. (2)labels::check_linkalso checked generic link texts in passing (English only, without the context exception from #569) and reported the same links aslink_purposeas a second row of the same taxonomy rule (deutschebahn.com 7 + 5 occurrences,violated_rule_countone too small, 3 reports). The side check is removed. -
Aborts in the rankinglab run, 2026-09-29: Of 122 rankinglab pages, 7 failed; four of them ran without problems with 1.3.1. (1) Single audits with full Chrome on macOS sometimes came to a complete standstill with the CDP focus emulation: www.deutschebahn.com hung in 3 of 6 runs (every CDP command ran into the 30 s timeout, the audit exceeded rankinglab’s 12-minute limit), without the emulation 6 of 6 ran in 103-128 s with the same results. The emulation was intended for hidden tabs of parallel batch pages and now applies only there (
BrowserOptions::focus_emulation, set at--concurrency> 1). (2) If a throttled performance call fails, the page keeps loading under the CPU throttling; the cleanup commands then waited 30 s each. Now the pipeline first releases the CPU throttling, stops loading, each step with 5 s, and skips the remaining profiles if the tab does not respond. (3) The pre-check before browser start aborted on a HEAD timeout: www.regierung-mv.de does not answer HEAD at all (GET in 0.3 s), www.ing.de needs 9-10 s per response with a fixed 10 s wait. Now a GET decides, and the wait is as long as-t. Not errors on our side: www.unito.it and www.douglas.de block (403), www.tu-berlin.de throttled temporarily (429). -
Report accuracy after the comparison with the rankinglab corpus, 2026-09-29: Two report critiques (gov.uk, sachsen-anhalt.de) against 1.3.1 found errors that distorted verdict and numbers; each is verified against the code or the data. (1) The merge of desktop and mobile paired every mobile finding with the first desktop finding of the same selector, even if that one was already taken: 18 empty lists per view became 35 occurrences. Now one to one. (2)
role="status"/alertwithout a name counted as a 4.1.2 violation; ARIA requires no name for these roles. On gov.uk two empty status regions carried the “failed”. (3) The combobox rule looked for the option list only in the subtree;aria-controlsand the closed state now count (APG autocomplete on gov.uk). (4) “Bedienelemente ohne Namen” (controls without names) counted all 4.1.2 findings from medium up, also duplicate IDs and unnamed dialogs; now only missing name/missing role and 2.1.1. The sentence “0 kritische und 0 hohe Befunde, davon 3 …” (0 critical and 0 high findings, of which 3 …) no longer names the blockers as a subset. (5) Security card and module table follow the corrected wording tier also in colour and table; the source quality cards use one scale instead of three; the effort of an action rises with the complexity of the finding (“Geringe Komplexitaet” (low complexity) next to “53 Vorkommen deuten auf ein Template-Problem” (53 occurrences point to a template problem)). (6) No double full stop in the appendix, German area names for touch targets, and the line below the counters separates places for manual checking from the criteria that can only be checked manually. (7) JSON stays canonically English (#406): since #633 the texts of the shared rules were in the run language in the JSON. The rules now run in English; a German run additionally checks in German and stores the texts inWcagResults::localized_texts(not serialised), which the PDF builders (single and batch) insert. (8) The DOM for the shared rules is the flat tree: light DOM nodes assigned via slot hang under their<slot>, unassigned ones do not appear. Previously they hung next to the shadow content, and every<ul><slot>of a web component stood there empty (sachsen-anhalt.de). (9) On exit,BrowserManager::closereported “Failed to close page: Session with given id not found” for the already closed audit page (5 of 15 single audits); that is now a debug message. Follow-up check on newly generated reports: (10) Blockers count elements, not rule hits (three name rules on the same menu element on sachsen-anhalt.de were “3 Bedienelemente” (3 controls)), with singular in the sentence. (11) The checklist “Alle Verstoesse” (all violations) also shows the shared texts in German. (12) Source quality: card colours by the same thresholds as the wording tier (40 instead of 60 for red), and “all signals fine” only if every dimension is good (gov.uk: 80+ overall, substance 70). (13) A landmark action witharia-labelno longer gets the title “Interaktive Elemente (Buttons, Links) verstaendlich benennen” (name interactive elements (buttons, links) clearly). -
Blocked pages are no longer scored, 2026-09-29: During the comparison with the rankinglab corpus it turned out that www.douglas.de has, since at least 1.3.1, been serving automated browsers an Akamai page “Access Denied” with HTTP 403 and about 100 nodes; it was scored 75 and reported as complete. With the headless shell, www.hornbach.de delivered a Fastly “Client Challenge” with CAPTCHA (355 instead of 12,942 nodes, 85 instead of 56). New module
audit::access_block: HTTP 401/403/407/429, unambiguous challenge titles of the providers or challenge resources on a thin page (< 300 elements; Cloudflare also loads/cdn-cgi/challenge-platform/into regular pages) make the audit of the URL fail withAccessBlocked: single audit with exit code 3 and reason, in the batch undererrors, without retry. The check runs directly after the first request; challenge pages often change their document immediately, hence up to three attempts and a second look at the document status later in the pipeline. Verified: douglas.de 3 of 3 blocked, hornbach.de normal with Chrome and blocked with headless-shell, batch over 15 comparison pages without false alarm. -
Batch on macOS with full browser serial against hanging journeys, 2026-09-29: In the reference batch (gov.uk, bundesregierung.de, dm.de, berlin.de,
--full, three workers), with system Chrome 154, journeys ran into the 10 s budget in 4 of 4 runs, twice the browser stopped completely (> 5 and > 10 min respectively). All open pages ran into the timeout in the same second, independent of the journey. A sample of the browser process showed the main thread in AppKit keyboard handling (performKeyEquivalent→SLSObscureCursor, waiting on the WindowServer): even--headless=newruns the event loop on macOS. Counter-tests: serialising only the journeys across pages did not help (1-10 timeouts); without focus emulation no total hang, but tab-walk timeouts again in hidden tabs; one worker: 2 of 2 clean (100-120 s instead of 38 s); single audits 6 of 6 clean;chrome-headless-shell: 5 of 5 clean, but www.hornbach.de delivered it a bot block page (355 instead of 12,942 nodes, scored 85 instead of 56). Change: without--concurrency, batches with journeys on macOS run page by page with the full browser; the run start anddoctorsay so. Afterwards: 2 reference batches without-cin 97-111 s, one clean, in the other a single modal test on dm.de over 10 s (reported aspartial, no hang). Browser selection previously did not find a shell installed viabrowser install --headless-shellat all; it is now the fallback after Chrome for Testing when no system browser is present. Measurements inreports/p65/. -
JSON and PDF show the same findings in the same order, 2026-09-28: Stability check before 1.6.0 on gov.uk, bundesregierung.de, dm.de and casoon.de, two runs each. Scores were stable, the reports were not congruent. (1)
top_actionsand the “5 wichtigsten Massnahmen” (5 most important actions) ranked by two logics; nowaudit::prioritization::action_orderapplies to JSON and PDF: severity, within it BFSG obligation (WCAG A/AA) first, then leverage, occurrences andrule_id. The PDF takes over the order of the normalisation, also in the finding matrix;top_actionscarriesrule_id. (2) The PDF took the title from the explanation, which for rules without their own falls back to the criterion text, and merged equal titles: four 4.1.2 rules became “Fehlende Name/Rolle” (missing name/role) with the summed count. Titles now come from the taxonomy; only the same item from WCAG and SEO is merged, without adding. (3) Ties and the page order in the batch depended on the input or completion order. (4)wcag_criterioncontained the rule identifier foraria-prohibited-attr,aria-hidden-focusandframe-testedinstead of 4.1.2. (5) In the batch, all pages except one were hidden tabs:requestAnimationFramenever fired,document.hasFocus()was false, the tab walk ran into the timeout on 7 of 10 casoon.de pages and focus checks measured differently than in the single audit. Every page now runs with CDP focus emulation, visible and focused (casoon.de batch 84 s -> about 50 s, no timeouts). A separate window per page achieved the same, but made Chrome hang with several heavy pages at once (reference batch 215 s instead of 57 s) and was discarded.run_single_auditcloses its page. (6)report-lintchecked the PDF certificate againstoverall_scoreinstead of against the stored certificate. (7) The batch JSON listed the same rule once per page intop_actions, the batch PDF merged but sorted on its own and named the count of one page in “Wirkung” (impact); both now useaggregate_batch_findings(summed per rule, severity as maximum, derived fields from the total),top_actionscarriesurl_count. New tests: JSON-PDF parity for single and batch report, order independent of the input, visible and focused parallel pages. -
a11y-*0.12: German finding texts,ids/duplicatein the core, 2026-09-28: The shared rules now run in the report’s run language (run_with_semantics_in,--lang deis the default). Since 0.11 theirmessagetexts arrived in English and so showed up in German PDF reports. The WCAG 2.2 filter forids/duplicate(only duplicates referenced via IDREF, 4.1.2) now lives ina11y-rulesitself and therefore also applies to astro-post-audit and LiveAudit;IDREF_ATTRS,referenced_ids,duplicate_id_is_referencedand the recount on the note are gone. The duplicate tests inshared.rskeep checking the same behaviour, and there is a new test for German texts. Verified: 1749 tests green, clippy and fmt clean. -
Structured data from
web-checks0.4, 2026-09-28: Rule tables, JSON-LD normalisation and assessment (schema_rules.rs, the normalisation half ofschema.rs) now live inweb_checks::structured_data, shared with astro-post-audit. What stays here: CDP collection, content comparison (schema_parity), microdata/RDFa and the report texts (feature_label,status_text,manual_review_text). Changes: the breadcrumb name may come fromitem.name(tagesschau.de: three fewer false required-field findings); FAQPage requiresacceptedAnswerper question; NewsArticle recommendspublisher, WebSitepotentialAction(WebSite quality is now computed over 5 instead of 4 properties);RULESET_VERSION2026-09-28. JSON shape:rule_assessments[].manual_reviewnow contains identifiers (merchant_listing_context, …) instead of English sentences (#406 pattern; the PDF derives the texts). Structure messages in the JSON name the block; identifiers (jsonld_*) are unchanged. -
Meta lengths and OpenGraph from
web-checks0.3, 2026-09-28: Title and description length appeared in four places (meta.rs,serp.rs,profile.rstwice) with the same limits 30–60 / 120–160 and counted bytes: every umlaut counted twice, so a German title of 60 characters could be “too long”. Nowweb_checks::meta(characters, whitespace collapsed as in the browser), shared with astro-post-audit. OpenGraph/Twitter: a tag with emptycontentcounts as missing (previously present), a group consisting only of empty tags as not present; completeness viaweb_checks::social. New inmeta_issues: invalidtwitter:cardvalue and relativeog:image(per medium), previously checked only in astro-post-audit. web-checks from 0.1 to 0.3 (robots unchanged). -
accname differential with computed style, a11y-core 0.11.3, 2026-09-28:
accname-diffnow computes the page’s own names withaccname::name_rendered:display/visibilitycome from a CDPDOMSnapshot(fetch_dom_document_with_layout,LayoutStyles,RenderedCdpDocument), as do the whitespace text nodes thatDOM.getDocumentomits. The shared rules continue to run unchanged viafetch_dom_document. Corpus (35 pages): one real divergence pattern instead of six (2 occurrences, text inserted by script on bundesregierung.de) — “EU-Arktis”, “Rechenpower”, “abholen*”, adisplay:nonecase and a<br>case now match Chrome. -
a11y-core 0.11.2, 2026-09-28:
accname,a11y-dom,a11y-report,a11y-rulesfrom 0.11.0 to 0.11.2. 0.11.1 (space between inline elements after a tag) is skipped and yanked: in the accname corpus, name equality fell from 97.7 % to 92.9 % because<span>elements turned into blocks via CSS were glued together. 0.11.2 reverts that and records<dt>(roleterm) as nameless. Corpus with 0.11.2: 97.9 %, 6 real divergences as before. The right solution (separator derived from the computeddisplay) lives in barrierlab. -
Meta-refresh interstitials in the JSON, 2026-09-28: That
navigatefollowed an interstitial (short<meta http-equiv="refresh">) or aborted a real redirect via refresh used to appear only in the log. Nowaccessibility.execution.navigation.meta_refreshcarriesoutcome(interstitial_followed|redirect_not_followed) andhopsper viewport pass; without a refresh the field is absent. -
Empty heading with its own taxonomy entry, 2026-09-28:
headings/emptyfell back toa11y.headings.missing— “Fehlende Ueberschriftenstruktur” (Missing heading structure), severity High, a flat 20 points deducted. An empty heading is a single defect, not a missing outline. Nowa11y.heading_empty.invalid(Medium, 2.5–8 points logarithmic like the other heading rules, area Headings) with its own explanation DE/EN. -
Missing navigation and footer landmarks with their own identifier, 2026-09-27: The two checks in
landmarks.rsdid not assign arule_id, so they fell back to their criterion and ended up in the 1.3.1 catch-all bucketa11y.structure.missing(“Missing semantic structure”, a generic explanation with a table example). Nowlandmark-navigation-presentandlandmark-contentinfo-presentwith their own taxonomy entries (a11y.landmark_navigation.missing,a11y.landmark_contentinfo.missing, area “Landmarks”), explanation DE/EN and corpus expectations (missing_main_landmark,landmarks_and_lists). Detection and severity unchanged. -
Own explanations for the shared identifiers, 2026-09-27: The shared identifiers with their own taxonomy entry (heading level, h1 missing/multiple, four list rules, three table rules, invalid language code, positive tabindex, limited zoom) had no explanation text of their own.
resolve_explanationfell back to the text of their criterion: an empty list read in the PDF and infix_guidancelike “Fehlende semantische Struktur” (Missing semantic structure) with a table example, an invalid language code like a missing language declaration. Now each has a text (German and English, with example code), keyed by the taxonomy identifier. The two texts forlistandmeta-viewport-largewere filed under dead identifiers and were never reachable; they have been merged into the entries fora11y.list_structure.missinganda11y.viewport_zoom.restricted(the list text still talked about empty lists, which now have an entry of their own). A test ensures that no shared identifier with its own entry falls back to the criterion text any more.headings/emptyhas no taxonomy entry of its own and stays with the text for 2.4.6. -
Dead catalogue entries removed, 2026-09-27:
LEGACY_WCAG_MAPstill containedlist,meta-viewport-largeandtable-duplicate-name— identifiers that no rule assigns any more (the first two went to the shared ruleslists/*andzoom/viewport-scale-limited, the third never existed as a check). Likewisea11y.table_structure.invalid, reachable only viatable-duplicate-name, together with its area mapping and explanation. Verified by searching source, tests, explanations and the PDF path. The entriesa11y.list_structure.missinganda11y.viewport_zoom.restrictedstay, since they carry the shared identifiers. -
One check for the grouping of radio buttons and checkboxes:
form-field-group, 2026-09-27: Two separate checks reported the same radio button outside a group:form_rules::check_grouped_controlsunderform-field-multiple-labels(in axe-core that means “field with multiple labels” — a different defect) andinfo_relationshipsunderradio-group. The latter checked only the direct parent and thus reported wrongly as soon as a<label>sat between the radio and the<fieldset>. Now there is one check with its own identifierform-field-group(a11y.form_field_group.missing): a radio button always needs a group as an ancestor, a checkbox only when the page has more than one radio/checkbox field.check_info_relationshipsis thereby empty and deleted; the run identifierdefinition-list/radio-groupis gone,form-field-multiple-labelsis now calledform-field-groupas run and filter identifier (anyone who had disabled it inauditmysite.tomlmust update the name). Taxonomy entrya11y.radio_group.missingremoved, explanation and corpus expectations (forms_and_misc,landmarks_and_lists) switched over. Accessibility score:forms_and_misc71 → 72 (the two radio buttons were counted twice); across all of that day’s taxonomy changes this is the only fixture page that moved, axe comparison Spearman −0.536 unchanged. -
Table and list check deleted from
info_relationships, 2026-09-27: The two sub-checks reported under the run identifierdefinition-listand duplicated the shared rules. Compared: “data table without header cells” (AX roletablewith cells but nocolumnheader/rowheaderamong children and grandchildren) is a subset oftables/header-missing(every<table>orrole=table|gridwithout<th>/header cell role in the whole subtree); “list without list items” (AX rolelist, only foreign children) a subset oflists/invalid-structure+lists/empty. True duplicates, hence removed under theSHARED_RULESprinciple, together with the cell check that only inflated the passed counter. The only gap:<menu>counts as a list for Chrome, but not for the shared rule. With the checks go the taxonomy entrya11y.definition_list.invalidand the explanation that talked about<dl>although a description list was never meant. The radio check keeps running under the run identifierradio-groupfor now. The corpus casemisc_content_checksnow explicitly expectstables/header-missingfor its table without header cells. -
valid-langdeleted: the invalid language code was reported twice, 2026-09-27: The own rulevalid-lang(language_extended.rs) read the same<html lang>as the shareddocument/lang-invalidand reported the same defect a second time. Following theSHARED_RULESprinciple (the own counterpart goes as soon as the shared identifier is adopted), the own check is removed; the shared one covers it (primary tag of 2-3 letters, plus the subtags, and also an emptylang).html-xml-lang-mismatchstays its own. With it go the taxonomy entrya11y.language_valid.invalidand its mappings; the corpus expectationinvalid_lang_codenow expectsdocument/lang-invalid. -
accname differential: name source from Chrome’s detail,
image=img, 2026-09-27: The source axis was blind: the AX extractor lumpsaria-label,altandvaluetogether asAttributeandaria-labelledbylike<label>asRelatedElement, and the differential reported all of these names asunknown. The extractor now additionally reads the winning source fromname.sources(first one with a value; identifier fromattribute/nativeSource), delivers it viaextract_ax_tree_with_name_sourcesalongside the tree, andCdpDocument::with_chrome_name_sourcespasses it on tonames_by_sourceandSemantics::name_source. The coarseNameSourcefroma11y-perception, read bytext_alternatives,accessible_name,svg_rulesandinstructions, stays unchanged (test). Role comparison: Chromeimageagainstaccnameimgcounts as equal. Corpus re-measured (35 pages):unknown56 → 0 (aria-label50,alt3,label2,aria-labelledby1), role divergences 215 → 25. Measurement side only,accnameanda11y-perceptionuntouched. -
Reference set rated: seven live pages with bands, 2026-09-27: Bands from three sources per page — current score, inspection in the browser (skip link, outline, alternative texts, form labels, reflow at 320 px) and the published accessibility statement —, confirmed by the user: gov.uk 75–92, gov.ie 75–92, casoon.de 90–100, mit.edu 70–89, bundesregierung.de 35–60, dm.de 15–40, berlin.de 15–40, basf.com 0–25. berlin.de initially fluctuated (desktop 71 or 27): the 71 came from a bot/load interstitial that the tool rated as the home page — fixed by following a meta refresh to the same URL; the real page sits stably at 27.
-
1.1.1: an icon in a named link is not missing alternative text, 2026-09-27: While checking the reference pages, auditmysite reported 7 “Image is missing alternative text” (High, Level A) on www.mit.edu — all inline
<svg>icons withoutrole="img"inside links with a name of their own (“MIT@twitter”, “open search”, the logo in “Massachusetts Institute of Technology”). The link carries the alternative; the icon is decorative, 1.1.1 is met. axe skips this case (svg-img-altapplies only torole="img"). Because of the new Level A cap, even a single such false positive would have limited the page to 89.text_alternativesnow exempts nameless graphics without aurlproperty (so not<img>) in named links/buttons; an<img>withoutaltremains a violation everywhere (F65). Known blur: an explicitrole="img"looks the same in the tree. mit.edu 68 → 78. -
aria-prohibited-attr names the role instead of the tag, 2026-09-27: For
div/spanwithoutrolethe rule reported “prohibited on role ‘span’”. In this case the rule covers only these two tags, whose implicit role according to HTML-AAM isgeneric— the message now saysgeneric. Found on the 30aria-labelspans on casoon.de/leistungskatalog/. Indocs/accname-differential.md,text_transformis now listed as an expected divergence (decision 2026-09-27:accnamestays with the DOM text). -
Menu buttons only with the menu journey, 2026-09-27: A button with
aria-haspopup="menu"was checked twice — as a menu (MenuOpen) and additionally by the accordion detector as an expandable element (AccordionToggle, i.e. with the disclosure journey). According to the ARIA Authoring Practices this is the “Menu Button” pattern, not “Disclosure”; the disclosure journey judged it by expectations it does not have to meet. The accordion detector no longer offers a trigger that the disclosure/menu detector has already offered; the detection in the report text stays. -
Refresh interstitials (bot/load check) were audited as the page, 2026-09-27: berlin.de serves some of the fresh browser sessions, instead of the home page, a 453-byte interstitial (“Einen Augenblick bitte / Just a moment please”, Varnish,
<meta http-equiv="refresh" content="2; url=/~~delay/">,<dialog open>) that leads back to the real page after 2 s. HTTP 200,readyStatecomplete, no mutations — done as far asnavigateand the stability check are concerned. The desktop pass audited this interstitial in 8 of 12 runs (5 AX nodes, accessibility 71 instead of 27, findings for a missing main/banner landmark, bypass,dialog-name,2.2.1/meta-refresh); the mobile pass then saw the real page.navigatenow follows a meta refresh with a delay of at most 5 s (max. 3 hops) until a new document is interactive. If the chain ends on the requested URL again, it was an interstitial; if it leads elsewhere (a real timed redirect), the requested page is reloaded and its refresh is aborted after loading withwindow.stop()— it is thus audited as delivered, including2.2.1/meta-refresh, instead of navigating away mid-analysis depending on the delay, as before. Re-measured: berlin.de 12 runs after the fix, desktop/mobile always 27/27 (interstitial resolved in 7 of them); bundesregierung.de 4 runs unchanged 41/41; local page with1; url=b.htmlstays on a.html with a meta-refresh finding. Unit tests for parsing the delay and the URL comparison. -
accname differential: corpus run and
text_transformclass, 2026-09-27:accname-diffwas limited to one URL; a corpus could only be tallied by hand. The command now takes several URLs and--url-fileand, from two pages on, writes anAccnameCorpus: totals per form and name source, cross table of both axes, recurring patterns with occurrences and page count, the individual results and pages that did not load. A page that fails to load no longer aborts the run.New form
text_transform: names that differ only in capitalisation are matched against the computed style of the element and its descendants (DOM.resolveNode+getComputedStyle, only for these candidates). If one of them hastext-transformother thannone, the case is counted separately — in the first finding this was the most frequent cause and would have dominated every corpus. Measurement on this tool’s page,accnameremains untouched. Without style (compare) it staysmismatch. Unit tests for classification, aggregate and CLI parsing. -
Stability check always reported “budget exhausted”: every audit counted as partial, 2026-09-27:
wait_for_page_stabilityevaluates a promise that resolves to an object{ status, waited_ms, mutation_count }— built withoutreturn_by_value. CDP therefore returned only an object reference,valuestayed empty, and every call fell back to the default values:budget_exhausted, full budget, 0 mutations, whatever the page did. The waiting was done correctly; only what was reported about it was wrong. Consequences:audit_qualitywas practically alwayspartialwithpage_stability_budget_exhausted:2(so on every casoon.de run), and the journeys could not see how long a click was actually waited for. Found while implementing the journey work. Re-measured: casoon.de and bundesregierung.decomplete; waiting times in the trace are now real (e.g. “stable after 201 ms, 0 mutations”). -
Disclosure findings with an uncertainty note instead of a longer wait, 2026-09-27: The wait after a click ends after 200 ms without a DOM change; a later reaction is only captured if another change happens to extend the window — measured as the cause of the roughly 8 % run-to-run fluctuation. Waiting longer cost +57 % disclosure time for a changed verdict in about 66. Instead, the trace now carries status, wait time and mutations per click, and a finding from a click whose wait ended before the budget gets
uncertainty: {kind: "late_reaction_possible", waited_ms}. Following the #406 pattern: canonicalkind+ raw value,finding_uncertainty_textas the only text source, attached to the finding in the PDF, localised; uncertain and certain findings are not merged there. -
Native
<details>: one journey run per trigger, no more false positives, 2026-09-27: A new Chrome fixture test (natives_details_erreicht_die_disclosure_journey) found three gaps. First,patterns::accordionadditionally offered every<summary>and every ARIA button witharia-expandedoutside navigation/banner as anAccordionToggle— which starts the samedisclosure_journeyas the already existingDisclosureTogglecandidate. Every such trigger was clicked through twice, its findings reported twice. The accordion now skips triggers that already have aDisclosureTogglecandidate; the number of disclosure journeys per page drops accordingly. Second,<summary>in<details name>carries the roleDisclosureTriangleGrouped: for that the accordion reportedaccordion-trigger-not-button(Medium, 4.1.2) on every exclusive accordion, and the journey determined no controlled region. Third, an open native<summary>gotaccordion-no-controls(Low) — a native element needs noaria-controls; the check now applies only to the rolebutton. The runtime fluctuation of the disclosure verdicts was measured on fixtures and documented (cause: the settling window ends 200 ms after the click, later reactions are only captured by chance); the timing behaviour stays unchanged because the remedy costs +57 % journey time on eight live pages. -
Shared rules get their own taxonomy entries, 2026-09-27: On
landmarks_and_liststhere was a finding “Missing semantic structure” with three unrelated locations — missing navigation landmark, empty list, list item outside a list. Cause:wcag_group_keygroups by rule identifier only ifLEGACY_WCAG_MAPknows it, otherwise by WCAG criterion. None of the 1.3.1 identifiers froma11y-rules(four list, three table, three heading rules) was listed there, all fell intoa11y.structure.missing. Likewisedocument/lang-invalidran under “Missing language declaration”, andkeyboard/positive-tabindexshareda11y.focus_order.weakwith the 2.4.3 group, so two findings could carry the same identifier. Now each of these identifiers has an entry of its own (title German and English, same criterion, score area);lists/item-outside-listandzoom/viewport-scale-limiteduse the entries of the superseded own rules (a11y.list_structure.missing,a11y.viewport_zoom.restricted). A test ensures that no shared identifier lands in the 1.3.1 catch-all bucket any more.The radio button outside a group carried the axe identifier
definition-list: the own ruleinfo_relationshipsstamped all three sub-checks (table, list, radio group) with the identifier of its run. The radio check now reports asradio-group(a11y.radio_group.missing); the corpus expectation is updated.The accessibility score stays the same:
AccessibilityScorergroups byViolation.rule, i.e. the criterion, not the taxonomy. The deduction of the new entries is that of the catch-all entry under which the identifier ran before; only the two reused entries bring their earlier own deduction with them. What can move is the per-area breakdown (accessibility_score_breakdown), by one to two points — heading findings now count under “Heading structure” instead of “Semantics”. axe comparison: Spearman −0.536 unchanged, no page moved. -
Unique selectors in all own page rules, 2026-09-27: Quite a few JS rules built their selector as
tagortag#id(partly with a class). Locations are merged by (rule, selector) — so all id-less elements of the same tag collapsed into one location (“a”, “button”, “div”): undercounted and not findable. Affected were 2.4.11/2.4.12 Focus Not Obscured (including the focus-walk check), 1.3.2 Meaningful Sequence, 3.3.8 Accessible Authentication (field, form, CAPTCHA widget), 2.2.2 Pause/Stop/Hide, 2.5.3 Label in Name, 1.4.11 Non-text Contrast (CSS), 1.4.13 Content on Hover, 2.1.1 click handler, 1.4.1 Use of Color and 3.1.2 Language of Parts (single-levelnth-of-type). All now use the existing__amsCssSelector(js_helpers::CSS_SELECTOR_JS); 2.5.5/2.5.8 also give up their own copy (targetSelector) for it. Elements with an id keep the formtag#id, so the corpus expectations remain valid. The child identifiers in the Meaningful Sequence message stay short — they are text, not a location. Corpus, score bands and integration tests green; axe comparison unchanged (Spearman −0.536), no page moved. -
2.5.8 Target Size: spacing and inline exception, 2026-09-26 (axe comparison):
target_size_minimummeasured only the rectangle of a target. But WCAG 2.5.8 exempts two cases: a target that is too small, around whose centre a 24 px circle intersects no other target (and no circle of another too-small target), and a link in running text. Both were missing — although the rule’s doc comment mentioned the inline exception. Every standalone flat button and every link in a sentence counted as a violation; so did “Send Message” and the skip link onperfect.html. Now implemented; 2.5.5 (AAA) gets only the inline exception, because it has no spacing exception. The inline building block is shared (INLINE_TARGET_JS).The corpus fixture
keyboard_and_targetsexpected a single 16 px button as a violation — the ground truth reproduced the bug. It now carries two adjacent 16 px buttons (violation), a single one with spacing and a link in running text (both pass, the link also for 2.5.5). axe comparison: Spearman −0.492 → −0.536.Two follow-up fixes, found by comparing with axe on
perfect.html: the inline check counts only the inline content of its own line without other targets — with the whole block text, a skip link directly under<body>counted as “in running text”. And the circle must not intersect the rectangle of any other target, even if that one is itself too small. In addition, unique selectors (tag#idornth-of-typepath): with the bare tag name, all links on a page collapsed into one location “a”.perfect.htmlnow reports the same four closely spaced links as axe (skip link, Home, About Us, Contact) and leaves out the free-standing button. -
Shared rules report English in the JSON: a11y family to 0.11.0, 2026-09-26: When checking the axe divergence of
landmarks_and_lists, German sentences in the JSON stood out (“Der Listeneintrag steht außerhalb einer Liste.” — The list item is outside a list.).run_shared_rulestakes the message froma11y-rulesunchanged, and up to 0.10 the crate phrased in German — affecting all 16 integrated shared rules, a violation of the rule “JSON is canonically English” (#406).a11y-rules0.11.0 phrases finding texts and hints in English and was already on crates.io;a11y-rules,a11y-report,a11y-domandaccnameare raised from 0.10.0 to 0.11.0, without API changes. The German PDF thus shows the location messages in English — as those of the own rules always have; titles and explanations stay localised. The too coarse classification of the shared list rules in the taxonomy is still to be addressed. -
Player controls of
<video controls>are not author content, 2026-09-26 (axe comparison): The biggest divergence in the new axe comparison wasmedia_and_motion: auditmysite 49 (Critical), axe nothing. The Critical came from Chrome’s own player UI: withcontrols, the browser puts play, mute and fullscreen buttons and a timeline as asliderwithoutvaluenowfrom its shadow DOM into the accessibility tree. The ARIA rules reported the timeline as “Required ARIA attribute missing” (Critical) and “Slider is missing accessible value” (High) — on every page with a video, capped at 49, and not fixable by any author. Fixed ina11y-perception0.2.1:AXTree::iter()omits everything belowVideo/Audio, for all WCAG rules.media_and_motion49 → 85, the three built-in defects are still found. The fixture sat in the Critical class of the score bands — only because of the false positive; it has been removed there. New axe baseline: Spearman −0.462 → −0.492, the only page that moved is this one. -
Live reference set and axe comparison for score calibration, 2026-09-26: Reference set:
tests/fixtures/reference_sites.jsonlists eight public pages; each gets a band from a manual review (not from the tool), with a date.tests/reference_sites_test.rs(Chrome + network) reports every page outside its band and runs as the new release step 0 before the tag (CLAUDE.md). Pages without a review are skipped.axe comparison:
scripts/axe-divergence.pyruns auditmysite and axe-core (WCAG 2.2 A/AA tags) over all 45 fixture pages and records score and axe violations by severity per page. The metric is the rank correlation (Spearman) between score and weighted axe load; the baseline is intests/fixtures/axe_divergence_baseline.json: −0.46 — same direction, moderately strong. A later run reports the change in correlation and every page whose score moves by ≥ 5 although axe sees the same. Agreement is not the goal; a scoring rework that clearly worsens the correlation should stand out. -
Score bands and a new cap: a Level A violation is not VERY GOOD, 2026-09-26 (step 1b): For the first time, an expectation that does not come from the scorer itself stands beside it. Decided in certificate terms: a practically clean page ≥ 95; exactly one High violation at Level A, otherwise (almost) clean, 75–89; at least one Critical ≤ 49.
tests/score_calibration_test.rschecks this on 21 fixtures against real Chrome, at the default level AA like a user audit.The middle band failed with the previous scorer: a missing alt text on an otherwise clean page gave 92, i.e. VERY GOOD — for a page that does not meet Level A and is therefore not conformant. New cap alongside the existing ones (Critical → 49, ≥ 5 Critical/High → 92): a High or Critical violation of a Level A criterion limits to 89. The same cap applies in the JSON per-area breakdown so that it does not diverge from the score again. Affected: every page with a Level A High finding and an otherwise high score — it drops from VERY GOOD to GOOD.
test_score_with_errorspinned exactly the old behaviour (95, grade A) and has been adjusted; the invariant generator now mixes Level A and AA so that the 92 cap is checked as well. -
Invariants for the accessibility score, 2026-09-26 (step 1a): The score had no check that did not depend on its own constants. Five properties that no tuning may break now run as tests over 2000 deterministically generated finding sets each (catalogued and unknown rules mixed): score in 0–100; one more finding never raises it; a higher severity never raises it; the caps (Critical → ≤ 49, ≥ 5 Critical/High → ≤ 92) hold for every set; only the empty set yields 100. All hold. The only observation: penalties are summed in
HashMaporder, so the same set may differ in the sixth decimal place — irrelevant for the integer score as displayed, the tests tolerate 1e-3. What a page should achieve is not stated by the invariants; the score bands follow for that. -
Two detection errors, found while calibrating the scores, 2026-09-26: Before fixing score bands, the tool ran over all 43 fixtures. Two findings were wrong.
1.3.5 Identify Input Purpose read the wrong source. The rule checked the AX property
autocomplete— that isaria-autocomplete(list/inline/both); Chrome does not put the HTML attributeautocompletein the tree at all. Consequence: every correctly marked-up personal data field counted as “lacks autocomplete attribute” (Medium), already visible onperfect.htmlwithautocomplete="name"/"email"; a combobox witharia-autocomplete="list"would have gotten “Invalid autocomplete value”. The rule now runs as a DOM page rule (check_input_purpose_with_page, like 1.3.6 and 3.3.7) and reads the attribute; the labelling approximates the accessible name (aria-label → aria-labelledby → label → title → placeholder). The classification is a pure function with unit tests.2.4.7 Focus Visible reported a page without focusable elements as a violation (High). 2.4.7 applies to “any keyboard operable user interface” — if there is none, the criterion is not applicable; axe-core reports nothing there. #568 had deliberately made the finding reachable again, the corpus expected it. It stays, but as a review hint (Low) without effect on the score;
no_focus_targetsnow expectsneeds_review. 21 of 43 fixtures were affected.Detection corpus green against real Chrome.
perfect.html: 97 → 99 (remaining: 2.5.8, a 21 px high button — correct under WCAG 2.2). -
AAA list in the PDF counted honestly: 11 instead of 17, 2026-09-26: The same overstatement as with the A/AA quota (30/55): the PDF listed 17 AAA criteria as “automatically checked”, but six of them cannot report a violation — 1.2.8, 2.2.3, 2.2.4, 2.2.5 and 3.1.3 deliver only an
untestedentry, 2.4.12 only a review hint. They are now inHINT_ONLY_CRITERIA; the list shows 41 criteria (30 A/AA + 11 AAA). Unlike the A/AA cases they do not go on the list of criteria to be checked manually, because that list, like the quota, refers to A/AA. The guard test now distinguishes this. Verified via--debug-typ(DE/EN). -
Journey leftovers: skip link target, scoped content, read errors, 2026-09-26: Three defects left open in the journey rework.
Skip link. The journey only checked whether the focus had left
body. That reported a non-focusable<main>as a High finding although the browser shifts the starting point of tab navigation and the next Tab lands in the content — and let a focus pass that jumped anywhere but to the target. Now the link is focused first (as with keyboard operation), the target is resolved from thehreffragment and it is checked whether the focus is inside or behind it; if it stays on the link orbody, a Tab decides. A fragment without an element is a finding. Five fixtures, tested against real Chrome.Disclosure. “Content appeared” was page-wide — a lazily loaded image at the end of the page turned “expanded belongs here, nothing to read” into a pass. If the controlled region is known (
aria-controls, or the<details>around a<summary>), only what appears or disappears in it counts. In the field this reaches less far than hoped: on 12 pages with 138 disclosure journeys the region could be determined only 8 times. The trace notesscopedorpage_wideper journey.quantity_stepper. If a CDP call failed,
focus_and_confirm/is_native_inputbecamefalse— and from that a High finding “not keyboard operable”. Unreadable values are now recorded asnot_observablein the trace, without a finding. -
Journey budget 15 s, hard limit per journey, 2026-09-25: The height of the budget was open. Measured on 48 public home pages without a limit and then recomputed per budget height (deadline checked before each start, as in the code): with 5 s, 22 % of the pages hit the limit and only 55 % of the findings were captured — the tab walk alone consistently takes about 2 s. 15 s captures 92 % (10 s: 83 %, 20 s: 98 %) and costs +1 s per page on average, because the budget only bites on heavy pages; the median of the interactive phase is 2.8 s.
The same run showed that a single journey can run indefinitely: the deadline is only checked before the start, and if the page hangs, every CDP call waits out its 30 s — on www.dm.de an accordion journey took 180 s. Every journey (tab walk, pattern journeys, SPA navigation) now runs under a limit of 10 s and is otherwise recorded as failed with
journey_timeout; the slowest journey without a hang was 5.6 s (modal).Fixed on the side: when the budget ran out, the remaining candidates were entered as
budget_exhaustedfrom the unsorted list, although since sorting by confidence the sorted one is worked through — the report named the wrong journeys as skipped.With the higher budget, the modal journeys on www.dm.de came up for the first time — and the audit then took 243 s instead of 73 s, all throttling profiles of the performance measurement ran into timeouts. Cause: Escape closes none of the three info dialogs, the journeys leave them open, and the following phases on the same tab configure throttling and cache before their own reload — under CPU throttling the renderer stopped responding with three open dialogs. A JavaScript dialog it was not (checked). After the interactive phase, the tab is now set to
about:blank; all later phases navigate to the URL themselves anyway. dm.de: 87 s, performancecompleted, all three profiles measured. -
Announcement structure to a11y-perception, words stay here, 2026-09-25:
announcer.rsdid two things in one go: decided what an announcement consists of, and at once said what that is called in German. The first half is not a property of auditmysite – that the level of a heading belongs in the role, thatexpanded=falsehas to say “collapsed” andrequired=falsenothing, that “focusable” adds something only where the role does not already give it away: that holds in every language and for every surface. It now lives ina11y-perception 0.2.0asannounce() -> Announcement(name, role, states as named parts,AnnouncedRole/AnnouncedState). What stays here is the mapping to the locale keys and the separator – 16 roles, 13 states, the same keys as before, no change tolocales/. The renderer has shrunk from 118 to 89 lines of code; the gain is less the number than what is no longer decided here.One behavioural difference, small and deliberate:
levelis now carried asu8instead of a raw string value. A heading with a non-numeric level is thus announced as “Ueberschrift” (heading) instead of “Ueberschrift Ebene” (heading level ). Chrome delivers levelas a number, so the case is theoretical.New guard
every_announced_role_and_state_has_a_german_word: the compiler enforces that every variant is in the match, but not that the i18n key exists –I18n::treturns a missing key unchanged, and “Suche, sr-role-textbox” would otherwise have passed. Verified:cargo test --lib screen_reader(44 ok),cargo clippy --all-targets -D warnings,cargo fmt. The four existing snapshot tests are green unchanged – that is the evidence that the announcements are character for character the same. -
Pinned toolchain and a slimmer crate package, 2026-09-25: Locally, in CI and in release, we built with whatever
stablewas current. Nowrust-toolchain.tomlpins Rust 1.98.1 (the current stable version, one patch version above the 1.98.0 originally planned) withclippyandrustfmt. There is deliberately no MSRV promise,Cargo.tomlgets norust-version. The README badgerust-1.75+claimed a lower bound that was never verified and now names the pinned version.dtolnay/rust-toolchaindoes not read the file. It installs what is in the ref or in the required inputtoolchainand sets it viarustup default. The file would have overridden that, butcomponents/targetswould have landed on the wrong toolchain, and the version would have had to be maintained twice. The workflows therefore callrustup toolchain installwithout an argument; that installs version, profile and components from the file. The release build adds its matrix target viarustup target add.CARGO_INCREMENTAL=0, which the action used to set, is now in theenvof both workflows.Cargo.tomlhas anexcludelist:.claude/,.github/,.githooks/,docs/,scripts/,tests/, the two additional documents andrust-toolchain.toml. The package shrinks from 623 to 386 files. The patterns are anchored with/, because the list as originally drafted, with a baretests/, would silently have removedsrc/output/tests/from the package too. Every path thatinclude_str!/include_bytes!references is in the package; the only exception is a test fixture under#[cfg(test)].cargo package --lockedruns through without--allow-dirty, and the binary from the unpacked package installs and answers to--help. The first CI run with the pinned toolchain has not happened yet. -
Browser tests run in the release gate for the tagged commit, 2026-09-25:
release.ymlcallsci.ymlas a reusable workflow and only builds once it is green. The comment inci.ymlclaimed thatbrowser-smokeandcoveragedid not run in that case because theirif:only admitspush/pull_request. That was wrong: in a called workflow thegithubcontext belongs to the caller, soevent_nameis the tag’spush, neverworkflow_call. Both jobs did run in the release call, only by accident, and a condition aimed atworkflow_callwould not have distinguished anything.Now it is stated explicitly:
browser-smokehas no job condition any more and runs on every call, including for the tagged SHA.coverageis a measurement and not a gate and is skipped for tags via!startsWith(github.ref, 'refs/tags/'). The comments inci.ymlandrelease.ymldescribe the actual behavior. A contract test intests/release_contract_tests.rschecks both. Counter-check: with the old condition onbrowser-smokeor without the tag condition oncoverageit fails. There has been no real tag run for this yet; that is pending for the next release. -
Best-effort cleanup errors no longer invisible, 2026-09-25:
cargo judge errorsreported six production sites in four files that silently discarded an I/O result. None of them may abort the audit, but two can leave files behind unnoticed. Deleting the downloaded browser archive after unpacking and deleting the.partialfile after a failed atomic write now log awarn!with the path; the installation result and the original write error stay unchanged. The flush of the “Checking for sitemap…” status line logs at debug level, and only if stdout is a terminal — a pipe or closed output is a valid environment, not an error. The cleanup of PDF screenshots and evidence crops goes through a helper,remove_temp_file, that countsNotFoundas success (most evidence slots are never written) and reports other errors at debug level so that a normal run stays quiet.Checked with a unit test for the helper (a missing file stays silent;
remove_fileon a directory yields an error that is notNotFound), the existing atomic-write test, clippy for both feature sets,cargo fmt --checkandcargo test --no-default-features.cargo judge errorsdrops from 17 to 11swallowed-resultfindings; the rest lives in tests and stays on purpose, as do deliberately lossy parse conversions. -
Desktop and mobile score from the same rules, 2026-09-25: It was assumed that the second viewport pass never moves the accessibility score. Measured on 35 public home pages, that is not the case: for 24 of 35 desktop and mobile differ, in part strongly (berlin.de 74/26, kit.edu 46/26). A repeat run over eight of them was exactly the same on six — the signal is mostly real: pages deliver different markup per breakpoint, and the differing findings come from ordinary structure rules (
interactive_name,alt_text, landmarks, ARIA).Part of the gap was an artifact, though:
html_content_modelandreflowonly run in the mobile pass and only flowed into the mobile score. Both judge a viewport-independent property of the page (raw markup; wrapping at 320 CSS pixels). The desktop score is now computed from the desktop findings plus the findings of these two rules; execution notes and the viewport labelling of the findings stay unchanged, because the rules still only ran on mobile. Re-measured: wherehtml_content_modelwas the only difference, the scores are now equal (commerzbank.de 36/36, gov.ie 73/73, hamburg.de 20/20); berlin.de keeps its real gap. -
Automation rate counted honestly: 30/55 instead of 39/55, 2026-09-25: A criterion counted as automated whenever the rule catalog has an entry for it — even if the rule can only produce review hints or an
untestedentry. A criterion that the tool cannot report as violated is not checked automatically. This affects nine criteria: 1.2.2, 1.3.2, 2.1.2, 2.2.2, 2.4.11, 2.5.1, 2.5.2, 2.5.4 and 3.3.7. They are inHINT_ONLY_CRITERIA(src/wcag/coverage.rs), drop out ofautomated_criteria()and now count as manual review; 1.3.2, 2.1.2, 2.4.11 and 3.3.7 are newly in the manual list for that. The rules keep running unchanged, their hints stay in the report. New numbers: 30 automated, 21 manual, 4 neither (of 55). Moved along with it: the principle coverage (informational, no score influence) and the EN 301 549 annex, which now lists these clauses as “manuelle Pruefung” (manual review) instead of “automatisch ohne Befund” (automatic, no finding). A guard test ensures that every hint-only criterion has a catalog rule, does not count as automated and is in the manual list.docs/PARITY_CONTRACT.jsonc,docs/PARITY_CONTRACT.md(still on WCAG 2.1, 50/36/10) and the README were updated. Checked: a--debug-typrun against a local fixture (scope “30 von ca. 55” (30 of approx. 55), manual cloud 21),cargo test --lib,parity_contract,release_contract_tests, clippy with all features. -
Criterion findings on mere presence of a technique removed, 2026-09-25: Four rules reported a WCAG criterion as soon as a technique appeared on the page that could be related to the criterion — without an observed defect. 2.2.3 No Timing fired on every
setTimeout/setIntervalin an inline script (debounce, carousel tick, analytics), 2.2.4 Interruptions on everyrole="alertdialog", 2.5.1 Pointer Gestures on strings such asontouchstart(even pure feature detection) and 2.5.4 Motion Actuation ondeviceorientation/devicemotion/shakein the script text — the latter even as a violation instead of a review hint. All four now only report theuntestedentry, whose text already says what is to be checked manually. For 2.5.2 Pointer Cancellation the second branch (anyaddEventListener('mousedown'|'touchstart')in the inline script) is dropped; the hint foronmousedown/ontouchstartdirectly on a control stays. There is no place for criterion-less informational signals, so the detection is removed without replacement. The review hints flowed into thereviewcount and from there into screen reader and risk aggregation. Checked:cargo test --lib, clippy with all features, detection corpus with real Chrome green. -
Audit target switched to WCAG 2.2 AA, 2026-09-23: The tool checked against WCAG 2.1 AA and deliberately left the 2.2 criteria it had long been checking out of the rate. The reference is now WCAG 2.2 AA: 55 A/AA criteria (2.1’s 50, minus the removed 4.1.1, plus the six new ones), 38 of them automated. The WCAG 2.1 view, which the BFSG invokes via EN 301 549 V3.2.1, is kept as an annex from the same run; criteria that only 2.2 brought are still marked as such there, because the standard does not cover them.
4.1.1 Parsing is removed in WCAG 2.2 and is no longer carried as a criterion. The two checks that hung on it now report 4.1.2 — the same mapping axe-core uses for
duplicate-id-aria. The generic duplicate check (ids/duplicate, iframe variant) now only reports what is also a violation: a duplicated ID that an IDREF points to (for,headers,aria-labelledbyand the other ARIA references). Then the relationship can no longer be resolved unambiguously. A duplicate that nobody points to no longer violates a criterion since 4.1.1 was dropped and produces no finding. axe-core removed its equivalents (duplicate-id,duplicate-id-active) for the same reason.Scores and rates shift as a result and are not directly comparable with older reports — a change of reference, not a regression. Checked on www.casoon.de (single, PDF via
--debug-typand JSON): rate 38/55,wcag_coverage.levelnow “WCAG 2.2 AA”,report-lintwithout findings. On proofreading a counting error turned up: the scope text counted 2.4.12 (AAA and new in 2.2) into the A/AA rate; now only what is also in the denominator is counted. Allhelp_urls now point toWCAG22/UnderstandingandWCAG22/Techniques; 2.5.5 along the way to the 2.2 nametarget-size-enhanced.3.3.8 Accessible Authentication (Minimum) has been added as its own rule, which raises the rate to 39/55. Only what is measured is a violation: a synthetic
pasteevent with a probe value is fired at every password and one-time-code field; the field only counts as blocked if the event was canceled and the value does not end up in the field. A handler that cancels the native paste and inserts the text itself, sanitized, thus goes unchallenged. An interactive CAPTCHA in a form with a password or code field is a review hint, not a violation, because object recognition and alternatives cannot be decided from the DOM; a CAPTCHA in the contact form does not belong to 3.3.8.autocomplete="off"on the password field is deliberately not reported — browsers ignore it there.When running the detection corpus it turned out that the
duplicate_idfixture still expected an unreferenced duplicate as a violation. It now checks both sides: referenced (label for) is a violation, unreferenced is not. Checked: detection corpus with real Chrome fully green,cargo test --all-features, clippy for both feature sets, www.casoon.de (rule runs, no finding, rate 39/55,report-lintwithout findings).3.2.6 Consistent Help is checked across pages in batch/sitemap mode. Per page,
patterns::help_mechanismscaptures the help mechanisms outsidemainin document order: contact/help/FAQ links,mailto:,tel:and known chat widgets, each with its page region (header, navigation, sidebar, footer, floating). Content inmainand invisible elements are left out, otherwise every contact link in an article would count as an inconsistency.audit::batch_consistencycompares all mechanisms that occur on at least two pages with the placement used by most pages. A deviation is either a mechanism in a completely different region (disjoint region sets, one additional occurrence does not count) or a swapped order of two mechanisms in the same region. Without a recurring mechanism the criterion stays “check manually”. In single-page mode 3.2.6 is now in the list of criteria to be checked manually (11 instead of 10), with a German title from a new table for the 2.2 criteria that EN 301 549 V3.2.1 does not contain.Along the way it turned out that the batch JSON did not output the cross-page WCAG assessments (3.2.3, 3.2.4, 3.2.6, 2.4.5) at all, although
OUTPUT_CONTRACT.mdpromises them — they were only in the PDF.site_analysis.consistencynow carrieswcag_cross_pageandhelp. Checked: new Chrome integration test of the detector (tests/help_mechanisms_detection_test.rs), unit tests for region and order deviation, PDF test for the localized deviation list, batch run www.casoon.de (12 pages): 2 recurring mechanisms, no deviation, German text in the Typst source correct.2.5.7 Dragging Movements is in the list of criteria to be checked manually (now 12). Whether a dragging movement has an alternative with simple pointing is behavior and cannot be read from the markup. A hint detector (sortable lists,
draggable) was deliberately not built: every rule with a WCAG reference counts as automated here, so 2.5.7 would have slipped into the rate without a violation ever being provable. The rate stays 39/55.summary.wcag_coverage.wcag_version("2.2") makes the reference version machine-readable. Reports from before the switch do not have the field and were based on WCAG 2.1. Both JSON schemas know the field,schema_versionstays 2.0 (additive).The reference run on www.inros-lackner.de turned up a counting error from the 4.1.1 rework:
rule_outcomesreported 10 findings forids/duplicate,violationscontained none. The filter on referenced IDs discarded the findings, but the note froma11y-ruleswas passed on unchanged. It is now trimmed by the discarded findings. Checked: unit test,cargo test --all-features, clippy for both feature sets, reference runs casoon.de (single + batch) and inros-lackner.de withwcag_version“2.2” and withoutreport-lintfindings. inros-lackner.de stands at accessibility 47 (on 2026-09-20: 20); the ten unreferenced duplicate IDs no longer count. How much of the jump is due to that and how much to changes on the site was not measured in isolation. -
Reproduce the docs.rs build in CI, 2026-09-23 (#588): The reporter of #588 pointed to an action in beta that runs the doc build in the docs.rs sandbox image — with its nightly, its resource limits and on what
cargo packagewould publish. That is the question the existing doc step cannot answer: it builds on the runner, with stable and without a memory cap.The occasion is in the build log of 1.5.1: 4.75 GB of 6.4 GB available RAM, 1m35s of 15 minutes. Since
all-features = true, docs.rs also documentsai-transparency, which lifts the dependency graph from 454 to 565 crates. A build that dies at this ceiling is only noticed aftercargo publish, and a published version cannot be replaced.The job runs on tags only: the question is “can docs.rs manage this build”, and it is to be answered once, shortly before the version is published. On every pull request it would cost seven runner minutes and a cache slot for a commit nobody publishes.
CLAUDE.mdnow lists the job as a mandatory step beforecargo publish.The action is pinned to a commit instead of a tag — it starts foreign Docker in CI — and the job runs with
continue-on-error: truewhile it is in beta. A newdependabot.ymlkeeps an eye on the pin (and the other actions). -
Remaining rustdoc warnings cleared, 2026-09-23: After #588 seven warnings were left that the gate deliberately let through at the time: two links to names that do not exist (any more) (
NodeIdwithout a path,RuleOutcomeinstead ofOutcome), three links from public docs to private items (defect_key,is_layout_only_role,score_intent_fit) — these now appear as code instead of a link, because a link the reader cannot follow is none — and two bare URLs incli/args.rs. The last two stay bare: these doc comments are clap’s--helptext before they are rustdoc, and angle brackets or backticks would then appear in front of every user in the terminal. There is now a#[allow(rustdoc::bare_urls)]with exactly this justification.The CI gate follows suit: instead of
-D rustdoc::invalid_html_tagsnowRUSTDOCFLAGS: -D warnings. Verified withcargo doc --all-features --no-deps(no warning), clippy,cargo fmt --check, 1546 unit tests and a look at--help, where the example URLs remain bare. -
docs.rs builds with all features, 1.5.1, 2026-09-22: Without
[package.metadata.docs.rs], docs.rs only builds withdefault = ["pdf"]. Everything behind an optional feature — such asc2pa— was therefore missing from the published docs.all-features = truefixes that. The setting only takes effect for versions published afterwards, hence 1.5.1 instead of an addendum to 1.5.0. -
Live regions observed over time, journeys freed from measurement artifacts, 2026-09-22: The form-error journey asked whether, after submitting, an
[aria-live]region exists that did not exist before. That made it blind to exactly the recommended implementation: whoever has the empty live container in the markup from the start got aFormErrorInvalidWithoutLiveRegionwith severity High. The add-to-cart journey compared two samples and therefore saw no message that appears and disappears again after two seconds — the normal case for cart feedback.New is
interaction::live_regions: aMutationObserverover live regions, also in shadow roots created later, records that a region received content, with timestamp and urgency. Both journeys evaluate these events. If the observer cannot be installed, no finding results but alive_observer_unavailablein the trace — without a measurement, “nothing announced” is not a statement about the page. Observed does not mean read aloud: the module only proves that the browser had cause to.On re-checking against the corpus, further journeys turned up that reported measurement artifacts:
- Tabs:
element.click()does not move focus, so the arrow key never hit the tab list. 20 of 22 tabs journeys reportedTabsSelectionNotMoved(High). Now it is only evaluated if focus is on the activated tab. - Menu: Escape is only evaluated if focus is in the menu, otherwise the key hit the page and not the menu.
- Modal: The journey now reads
modalon the opened dialog. Non-modal dialogs were so far reported across the board as a High finding; now focus containment only applies to modal dialogs, andFocusTrapBackgroundNotHiddenonly to dialogs that contain focus without identifying as modal. If focus was onbodybefore opening,bodyis the correct restoration after closing. Also, the candidate search never produced a trigger as long as no dialog was in the tree — a closed<dialog>has no role. Over 171 pages run, not a single modal journey therefore ran. - SPA navigation: Title, URL, heading and focus come from two
AXSnapshots instead ofdocument.querySelector('h1'); thus shadow roots androle="heading"count too. The initial capture is retaken before every attempt so that a failed attempt does not impute a focus movement to the next. - Disclosure: The magnitude of the native
<details>gap has been re-measured: 22 of 238 domains, not “280 of 663 pages”.
Verified with
cargo test --all-features --lib(1546 passed), three new Chrome integration tests (transient error message, correct modal dialog, correct menu — each without a false alarm) and clippy-D warningsfor both feature sets. - Tabs:
-
Raw HTML tags in doc comments, 2026-09-22 (#588): docs.rs reported truncated pages, e.g.
PageHealthAnalysis: doc comments named elements like<iframe>without backticks, rustdoc output them as real HTML, and the streaming rewriter of docs.rs broke on it. 16 places in six files are now inline code. Verified withcargo doc --all-features --no-deps: noinvalid_html_tagswarning any more. CI now builds the docs with-D rustdoc::invalid_html_tagsso that new cases are noticed before the release. -
a11y-core 0.10.0 and the heading rules handed over, 2026-09-21: The project was on
a11y-core0.6.0, 0.10.0 was published. The jump over four minor versions brought not a single API break —dom_document.rsandwcag/shared.rstranslate unchanged — but twelve additional identifiers: fivelandmarks/*,keyboard/skip-link-missing,zoom/viewport-missing,headings/h1-multiple,links/generic-name,aria/required-attribute-missingand the twocontrast/*. That makes 42 shared identifiers available.A test failed in the process, and rightly so: it demanded that with
Semanticsno rule drops out for lack of capability any more. That held at 0.6.0 because there was no tier 3 there. Since 0.7.0 the contrast rules reportCapabilityMissingwithout rendered styles — the principle “not run is not passed”, applied to auditmysite itself. The assertion now names the two identifiers instead of demanding a zero that no longer means anything. ServingRenderingover CDP remains a separate step.With
headings/h1-multiplethe last gap fell wherewcag::rules::headingscould only be replaced in part. The module is deleted, all four checks come from the shared inventory,SHARED_RULEScarries 16 instead of 12 identifiers. On clearing out, a mismeasurement came to light: the AX version sorted headings bynode_idas text, so “h10” came before “h2” and jumps in longer pages were rated wrongly. The shared version runs in document order over the DOM.Two intended differences remain: multiple
h1areREVIEWin the shared version instead of a violation and report once instead of per surplus heading — multipleh1are permitted in HTML. And “empty” means in the shared version “no text in the subtree, noaria-label”; a heading that is only named viaaria-labelledbyor analtin an image is wrongly reported by the shared version. That is noted as a finding fora11y-core, not as a reverse exception here.Verified: 1,716 tests green,
clippyandfmtclean, the corpus expectationheading_orderraised toheadings/skip-level. The completeness test of the corpus was once again the guardian that would have found a leftover identifier. -
Maintainability hotspot 1, 2026-09-20:
src/output/pdf/single_report.rswas, with 3,717 lines and 21 changes in 60 days, the most frequently touched file of the project and mixed risks/strengths, problem profile, score-driver table, subcategory breakdown, appendix, findings, root-cause analysis and roadmap.The problem-profile cluster has been extracted to
src/output/pdf/problem_profile.rs(527 lines): nine functions, two constants and two types. The cut was low-risk because nothing of it was referenced from outsidesingle_report.rs— only three functions had to go from private topub(super).single_report.rsdrops to 3,219 lines; the diff there contains nothing but deletions apart from three import lines and two visibility raises.Verified as output-neutral: the
--debug-typrun of www.inros-lackner.de has the same line count before and after and an identical problem-profile section.The test helper
test_report_view_modelwas not duplicated but made visible viapub(in crate::output::pdf)— a second copy of a 70-line fixture would be exactly the kind of duplicate this refactoring removes.Reassessment for hotspot 2:
normalized.rsis now the largest file with 4,553 lines and 20 changes/60 days and the next candidate. -
Presentation artifacts in the PDF, 2026-09-20: Six small, independent defects from a review of the two
--debug-typsources, each a few lines, none a product decision.- The appendix claimed 36 automatically checked criteria and listed 56. The cloud carried
the title of the WCAG 2.1 A/AA rate but additionally contained AAA and the WCAG 2.2 criteria
without saying so anywhere. Now it carries its real number plus a line that breaks it down.
While writing, the breakdown at first did not add up – 36 + 4 + 17 = 57 against 56 listed –
because one AAA criterion is also WCAG-2.2-only and was counted in both groups. The three
groups are now disjoint, and
the_three_appendix_groups_partition_the_automated_criteriapins the sum. ◐(U+25D0) was silently swallowed. No bundled font covers the character; Typst reported “Dropping U+25D0” and five medium-confidence rows began with a gap where all the others had a symbol. There was no legend anyway. The scale is now a word ([gemessen]/[wahrscheinlich]/[schwaches Signal], i.e. measured/probable/weak signal) – verified: no Typst warning any more, and the five rows now carry their label.- Module takeaway appeared twice. The
section-header-splitbody was repeated two components later as its own label. Newinterpretation_beyond_takeaway: the label now only shows what the header has not already said. - “Header 0/10” in the success color. The accent was pinned to teal; it now comes from the
ratio, via the same
score_colorfunction as everywhere else. inros-lackner 0/10 is red, casoon 8/10 green. - “Details im Methodik-Anhang” (“details in the methodology appendix”) led nowhere. The
appendix repeated the same sentence; which measurements were discarded was stated nowhere,
although
execution.navigation.stabilityknows it. The note now names them itself (“Betroffen: Desktop-Ansicht nach 1500 ms, Mobile-Ansicht nach 1500 ms”, i.e. affected: desktop view after 1500 ms, mobile view after 1500 ms).mutation_countis only named if it was actually counted – otherwise the value falls back to 0, and “noch 0 DOM-Aenderungen” (“still 0 DOM changes”) would be a default printed as a measurement. - Contradictory DOM classification. “(Performance 75 Pkt stabil)” (performance 75 pts stable) reassured about exactly what the action list two blocks further up prioritizes (“DOM-Struktur verschlanken”, i.e. slim down the DOM structure). Now “bei derzeit tragfaehiger Performance” (with currently adequate performance) – both facts, neither contradicts the other.
- The appendix claimed 36 automatically checked criteria and listed 56. The cloud carried
the title of the WCAG 2.1 A/AA rate but additionally contained AAA and the WCAG 2.2 criteria
without saying so anywhere. Now it carries its real number plus a line that breaks it down.
While writing, the breakdown at first did not add up – 36 + 4 + 17 = 57 against 56 listed –
because one AAA criterion is also WCAG-2.2-only and was counted in both groups. The three
groups are now disjoint, and
-
“Little text at the top” measured node position instead of page position, 2026-09-20: The finding tells the customer “Wenig sichtbarer Text im oberen Seitenbereich — Nutzer erhalten keine sofortige Orientierung” (little visible text in the upper page area – users get no immediate orientation). That is a statement about the rendered page; what was measured were the first 50 nodes of the accessibility tree in document order.
After the role fix, 93 of 2731 cached pages remained flagged, and these remainders were not a smaller version of the same problem but the failure of the approximation. On www.inros-lackner.de the first 50 nodes are a skip link and forty wrappers; the
articleelements stand as empty shells before their own text. Tree order there is no vertical order at all, so even a wrapper-skipping variant (measured: 13 instead of 93) would only have swapped one uncalibrated constant for another.Now
JourneyModule::collectmeasures in the page: aTreeWalkersums the text whose box lies within the first viewport height. In document coordinates (rect.top + scrollY), because another module may have scrolled before, and without screen-reader-only text — the same__amsIsVisuallyHiddenhelper that the in-page WCAG checks use. The same pattern as the module’s already existing<main>DOM check. The tree approximation remains as a fallback for calls without a page (analyze_journey, tests) so that a missing measurement is not read as “no text”.Verified in both directions with three fixtures: text behind a 3000px hero is flagged, a page with a heading and paragraph at the top is not, and 79 characters of pure screen-reader text at the top do not count as visible text. www.inros-lackner.de is no longer flagged, journey there 65 -> 68; www.casoon.de unchanged at 91. Two fixtures and an end-to-end test in
tests/integration_test.rspin down both directions — the old approximation could not tell them apart, because the heading is at the front of the tree either way. -
Flaky fixture server, 2026-09-20:
security_detection_corpus_matches_real_analyze_security_runfell over sporadically with a FALSE-NEGATIVE message – the worst possible form of a flake, because it reads like a real regression in the security detection. A port race was suspected; butbindon port 0 was already there.The actual cause: the listener is set to non-blocking so that the accept loop can poll a shutdown flag – and under macOS/BSD the accepted socket inherits this flag.
readandwrite_allcould therefore returnWouldBlockbefore the request was even there, and both results were discarded withlet _ =. The response went out unwritten, the client saw nothing,analyze_securityfell back to empty headers (which is right for a page that refuses HEAD and GET) and the corpus diff reported a missing header.Proven rather than suspected: a probe showed
read -> Err(WouldBlock)in every run, and under 16-fold parallel load the old test fell over in 29 of 48 runs, with exactly the message originally reported (cors_wildcard_credentials). After the fix 48 of 48 green.The fix: accepted connection back to blocking, read the request head to the end, each connection in its own thread (an accept loop waiting for one client starves all the others), and transport errors are recorded instead of swallowed. The test now checks
fixture.served() > 0before it rates anything as a detection failure – verified with a simulated transport error that is now reported as such instead of as a FALSE NEGATIVE.The same server was copied six times in the integration tests, each copy with the same race. It now lives once in
tests/common/fixture_server.rs(298 lines fewer). The four Chrome-gated suites run green with it.Along the way a second, already existing flake turned up:
test_concurrent_wait_for_stable_stays_within_its_timeout_budgetput its 4.65 s budget around the entire task includingnew_page(), although onlywait_for_stablewas meant – on a busy machine the full--ignoredround therefore fell over 2 out of 2 times on the unchanged code. The outer bound is now a pure hang guard; the actual assertion still measures onlywait_for_stable. After that 3 of 3 full rounds green. -
StaticTextwas invisible to every text-measuring reader, 2026-09-20:AXTree::iter()filters out browser-generated roles,StaticTextamong them. For WCAG rules that is right – a finding must not be reported against a node that nobody wrote. For everything that measures text it is wrong: on a real page the visible words are exactly there. Measured on two cached trees: 72-76% of all characters in anamesit on browser-generated roles, andparagraphnodes never carry anameof their own at all.Thus
matches!(role, "StaticText" | "paragraph")overiter()read nothing on any real page. Two places were affected:- Page-type classification (
page_intent.rs):text_lenwas structurally 0, soapprox_words > 500could never take effect. A second dead constant turned up in the process: the marketing fallback additionally requiredapprox_words < 300, which with a sum of 0 was always true. With real word counts, 222 pages would have dropped from “Marketing” to “Nicht erkannt” (not recognized) – a landing-page default losing against a 300 limit that was never checked. The clause is removed because it never took effect. - Journeys “early content” (
analysis.rs): readStaticText | headingand thus saw only headings.LittleEarlyText– 20 points deduction on Entry Clarity – fired on 1595 of 2731 unique cached pages. More than half of the web allegedly without text at the top.
One definition instead of role lists per call site:
AXNode::is_text()andAXTree::text_nodes()/visible_text_len()count the text exactly once –StaticTextand nothing else, because Chrome repeats the same run on theInlineTextBoxchildren and the name of a heading or link is computed from the sameStaticTextdescendants (measured: 30 of 44 heading names and 71 of 87 link names are word-for-word identical with aStaticText).Verified over 2731 unique cached pages with the new
tests/page_intent_corpus.rs(#[ignore]-gated, reads a local artifact cache):LittleEarlyTextdrops from 1595 to 93, and 68 pages change page type – all in the direction of Editorial, 48 of them on an actual blog that previously passed as Corporate.Not fixed along with it: the time window itself.
LittleEarlyTextpromises “little text in the upper page area” but measures the first 50 nodes in tree order. On www.inros-lackner.de the skip link and forty wrappers stand there. A variant that skips pure wrappers was measured (13 instead of 93 flagged) and rejected: thearticlenodes of this page stand as empty shells before their own text, so tree order there is no vertical order at all. That needs geometry instead of a new constant and is tracked separately. - Page-type classification (
-
AXTreewithout document order, 2026-09-20:AXTree.nodesis aHashMap, anditer()/headings()returnedvalues()– hash order, which Rust sets randomly per process. Detectors that read the tree as a document thereby contradicted themselves: two consecutive audits of www.inros-lackner.de from the same binary, one reported UX 78, the other UX 81, without anything having changed on the page. Affected were the heading-skip detection (last_levelpresupposes document order) and journeys “early content” (iter().take(50)over aHashMapis fifty arbitrary nodes, not the start of the page).CDP already delivers
getFullAXTreein document order –from_nodesmerely threw it into theHashMap. A new private fieldorder: Vec<String>retains it;iter()anditer_all()run over it. If the order is missing (a snapshot from the cache written before the field, or a direct write access to the publicnodes), it is reconstructed fromchild_idsby depth-first search from the root, unreachable nodes appended sorted by id – degraded, but deterministic.Verified: three consecutive runs over www.inros-lackner.de deliver identical UX findings and module values. Journey drops from 68 to 65 in the process, because
take(50)now actually reads the start of the page. TheHeadingSkipscase deliberately left out earlier is now inevery_penalty_states_its_own_reason_at_the_first_occurrence– it could not be asserted as long as h1 -> h3 was only a skip depending on the run.Not fixed along with it: the
StaticTextblindness of theiter()readers, which stood in the “Related” section of the write-up as two call sites. The one-liner (iter()->iter_all()) was implemented, measured and discarded again: it changed the classification on neither of the two test pages, and a guard test for it passed even with the defect, because the keyword scan over it does not seeStaticTexteither. That is the actual problem and is now tracked separately. -
Score hierarchy, 2026-09-20: The report carried around 30 different 0-100 values, 14 of them with a grade A-F. The subject of the tool – accessibility – was one of them, with 40% weight in another. Four decisions, four commits, after which a three-level rule holds: accessibility as the headline, the five remaining weighted modules as rated context, everything else as an indicator without a grade.
- Grade only for modules that carry the overall value (D2): Seven of the thirteen modules
have
weight_pct: 0, so they feed nothing, but carried the same A-F grade as accessibility. So “Dark Mode: F” stood there – a grade for an optional product feature that the code itself carries asmeasurement_type: "optional"– next to an F for the exclusion of screen reader users.ModuleScoreEntry::newderives weight, grade and band from one source:gradeis anOptionand only set for weight > 0,bandalways carries the canonical English FIVE_BAND label. Likewise for thegradefields ofAiVisibilityAnalysisandSourceQualityAnalysisand fordark_mode. The PDF was not affected – it showed band words anyway, the grades were only in the JSON. - Counters instead of a rate where the denominator is arbitrary (D4): Content Visibility was
(signals - problems) / signals, i.e. “share of checks that did not complain” – one more check that usually passes raised the value of every page. The score is dropped without replacement; the counters that already stood next to it are reported. In the process it turned out that the success message “Alle Content-Visibility-Signale sind in Ordnung” (all content visibility signals are fine) appeared fromscore >= 80, i.e. also with up to a fifth of problem signals; it now hangs onproblem_count == 0. One level deeper,SignalCategorycarriespassed/totalinstead ofscore_pct, and the table title says “17 von 24 Signalen erfuellt” (17 of 24 signals met) instead of a percentage weighted with six invented factors. - Declare derived indicators as such (D3): A reader saw SEO, AI visibility, source quality,
UX and Journey as five separate assessments that happen to agree.
AiSignalKind::TechnicalTrustfoldeda11y_score >= 80andsecurity_score >= 70into citability,QualitySignalKind::Accessibilitycounted the accessibility score once more in the authority dimension – both removed. The eleven invented citation weights (0.08, 0.15, 0.10, …) suggested a calibration that does not exist; now equally weighted under a namedSIGNAL_WEIGHT. What remains is declared: new fieldderived_from, fed fromtaxonomy::module_derived_from, plus a sentence in the PDF under every affected indicator. The accessibility deduction on UX and Journey is quantified instead of silently included. - The headline is accessibility (D1): Grade and certificate hung on the weighted overall
value (#233, so that they do not contradict each other). That resolved the internal
contradiction but moved the figure away from the subject of the report:
inros-lackner.de with accessibility 20 appeared on the cover as 45, because performance,
mobile and SEO pulled it up; casoon.de with accessibility 100 as 92. Both now read the
accessibility score, so they still cannot contradict each other. The weighted value remains as
a named ScoreCard “Kombinierter technischer Wert” (combined technical value) with its weight
basis – without it, it would have disappeared from the PDF, since it only stood on the cover.
report-lintchecks againstaccessibility_score; new fixture, because in all previous ones both scores are equal and none would have noticed the switch. Incidentally two more band tables eliminated: the batch builder computed grade and certificate with its own literals (95/90/85/80/70/60), the batch cover withBATCH_GRADE– so the same score was graded differently depending on the report. Both now use the same two functions as the single report;BATCH_GRADEis dropped.
Verified on fresh reports of www.casoon.de (accessibility 100, combined 92, grade A) and www.inros-lackner.de (accessibility 20, combined 45, grade F, certificate NICHT BESTANDEN, i.e. not passed);
report-linton both without findings. - Grade only for modules that carry the overall value (D2): Seven of the thirteen modules
have
-
Report quality pass, 2026-09-19: Result of a
report-criticrun over fresh single-URL reports for www.casoon.de and www.inros-lackner.de.auditmysite report-lintfound nothing on either report — all points are semantic in nature and structurally invisible to the deterministic linter. Six commits, one per finding.- Explanation lookup skipped the axe identifier: The JSON writer and the batch report
resolved the customer-facing explanation via the taxonomy
rule_id;get_explanationfalls back from there to the bare WCAG number, and the rule-specific entries hang off the axe identifier. Finding: 4 of 15detail.fix_guidanceentries carried foreign text — the three landmark rules appeared as “Missing semantic structure” with table markup as the code example. The single PDF was correct, only the JSON was not. Same class of error as #571. Newresolve_explanationas the single resolver at all three call sites. While fixing it, it turned out that the now-reachable code examples would have put German text into the canonically English JSON; the guard now checks for more than umlauts. accessibility_score_breakdownwas a second score model: its own severity weights (20/14/8/4), a cap at 90, invented importance weights. Finding: anaccessibility_scoreof 20 next to areas whose weighted average came to 57. A weighted average cannot reproduce the score —diversity_factor, sqrt compression,apply_soft_floorand the cap are non-linear and depend on the entire set of findings. The two conflated questions are now two fields:scoreis the area on its own, run through the scorer (newscore_from_penalties),estimated_lost_pointsis its share of the actual loss.sum(estimated_lost_points) == 100 - accessibility_scoreholds exactly and is checked byreport-lint. Schema unchanged.- Score areas came from running text:
score_area_for_findingsearched for words inrule_id + title + description + subcategory. Finding:a11y.landmark_region.missingended up under “Images / alternative text” because its description mentionsrole 'image';seo.headings.multiple_h1drove an area of the Accessibility breakdown. Newtaxonomy::score_areawith a totalrule_id -> ScoreAreatable over all 120 Accessibility rules and three inventory tests.score_area_for_key_pointwas a second, word-for-word copy of the same search and now delegates. - “Erwartungswert fuer diesen Seitentyp” (expected value for this page type) was a literal:
intent_fit_scoreis one of eleven constants and was compared againstseo.score— a different function, a different scale. ForThinContent(28) the statement flipped: a thin page “met the expectation”. The comparison is dropped; the number stays as a quality value. In addition, the gateintent_fit_score < 65for three page types hangs on a pure type constant, so a media-heavy page received the advice regardless of its quality. - Two models for the same risks:
build_management_risksfilled the JSON,compute_dimension_rowsbuilt the PDF panel alongside it. Finding: the JSON carried 4x high, the panel showed 3x bad and 2x warn, two high dimensions were missing entirely, and all evidence-backed rationales were discarded. Newaudit::management_riskas the single derivation following the #406 pattern. In the process three statements without a measurement basis were dropped: the conversion chains (which reached no output format anyway), the constant trust sentence and the template conclusion drawn from a single page.RiskTier::Unknownis new — a module that had not run was previously rendered as a strength viaunwrap_or(100). - Security claimed a clean bill of health over open findings: The clean notice and the
takeaway hung on the score, not on the findings list, and
derive_security_recommendationsonly checks for missing headers — a present but misconfigured header produced nothing, and the default claimed the headers were set cleanly. Finding: casoon.de, score 95, three open CSP findings (one High), and the section read “Sehr gut — keine wesentlichen Sicherheitsauffaelligkeiten” (Very good — no significant security findings). The band correction is now symmetric, the recommendations hang offSecurityIssueKind, and the ScoreCard takes the same corrected band — otherwise “95 — Sehr gut” (Very good) stood above a takeaway “Verbesserungswuerdig” (Worth improving). The same defect was present in the SEO section.
- Explanation lookup skipped the axe identifier: The JSON writer and the batch report
resolved the customer-facing explanation via the taxonomy
-
Heuristic hygiene: no more silent deductions, 2026-09-19: Parts 1 and 2.
- Deductions without a stated reason: In
ux/analysis.rs, three checks lowered the score completely silently (word count 50-100, long page with fewer than five headings, fewer than three trust keywords), and four more deducted from the first occurrence but only reported from a considerably higher threshold. Finding:reports/inros-lackner-audit.jsonshowedcontent_clarity: 80without any ContentClarity finding in the list — 80 is exactly one 20-point deduction, the silent word-count branch. The rule was already in the code: theLargeDombranch carries the comment that the score must never drop without a stated reason — but it was applied in exactly one place. Now every deduction reports; so that this does not flip from silent to alarming,ux_issue_severityis value-dependent: mild bands reportlow. Injourney/analysis.rs, five deductions had no friction point; there are five newFrictionKindvariants for them. - Binary thresholds next to the percentage they ignore: The cross-page consistency signals
were booleans while the report printed the real percentage — 94 % HSTS coverage counted
exactly like 0 %, visibly next to a “94 %”.
QualitySignalnow has afulfilment(0.0-1.0);presentremains the pass/fail marker, the calculation is proportional.ErrorFreePagesuses theclean_pctthat it had already computed and discarded. True yes/no signals remain unchanged. - Found along the way:
AXTreeiterates over aHashMap, and the heading-skip detection reads that anyway — two runs of the same page produced different findings. In addition,analyze_content_claritycounted text viaiter()and listedStaticTextas the first role, althoughiter()filters out exactly this role: the branch could never trigger, and the deduction was a false finding. Withiter_all(), inros-lackner.de goes fromcontent_clarity80 to 100. Fixed here because otherwise a silent false finding would have become a visible one.
- Deductions without a stated reason: In
-
Verdict, rating and derivation of the overall value, 2026-09-19: Continuation of the report quality pass.
- The overall value was not derivable: The table “Warum ist der Gesamtwert, was er ist” (Why
the overall value is what it is) listed the modules with their weights; recalculated, that
gave 90.05 against a reported 92 (casoon) and 47.05 against 45 (inros-lackner). Finding:
there are two calculation paths, and only one of them is the module weighting. In
viewport_weightedmode the value arises from a desktop/mobile blend with security mixed in — this is inscore_breakdownand was rendered nowhere. The table there is now called “Die gewichteten Module im Einzelnen” (The weighted modules in detail), a second table shows the real calculation and reproduces the value exactly. Inmodule_weightedmode everything stays as it was — there the weighting is the derivation. - Verdict and rating were missing from the PDF entirely:
summary.certificatewas only read as a gate,verdict/verdict_reasonswere not rendered at all. TheSummaryBlockfield namedverdictis a prose sentence, a different value under the same name. Finding: the CLI printed “FAIL — legal_flags: 5, blocking_issues: 36”, nothing of this was in the document, and the cover page read “Ausbaufaehiger technischer Zustand” (Technical state with room for improvement). Decided: the PDF names both, and the label is “Gesamteinstufung” (overall rating) instead of “Zertifikat” (certificate) —calculate_certificatemaps the score to a band label and certifies nothing. A partial run may carry a rating, but as a provisional one, and this now stands up front instead of only in the appendix. - The verdict reasons were machine tokens: Rendering
legal_flags: 5unchanged would have brought canonical English into the German PDF.VerdictReasonKindnow carries the numbers,text(en)is the single reader-facing source;VerdictResult::reasonskeeps its exact strings for JSON and CLI,reason_kindsisserde(skip).
- The overall value was not derivable: The table “Warum ist der Gesamtwert, was er ist” (Why
the overall value is what it is) listed the modules with their weights; recalculated, that
gave 90.05 against a reported 92 (casoon) and 47.05 against 45 (inros-lackner). Finding:
there are two calculation paths, and only one of them is the module weighting. In
-
Switch to the shared a11y-core crates, second part, 2026-09-19: All three crates from 0.2.0 to 0.3.0. This removes the blocker of the first part:
RuleRunnow carriesviewportandwcag, andFindinghasrule_name,with_element(role, name)and the opaqueExtraslot — the fields on which the switch ofViolationpreviously failed.-
RuleOutcomereplaced bya11y_report::RuleRun: The execution note comes from the shared crate. The key of a note is thus(rule_id, viewport)— the same rule runs once per viewport, andrule_runsandfindingsuse the same set of names. Finding: Of the seven values of the localRuleOutcomeStatus, four said the same thing — that the rule ran. No evaluator in the code ever distinguishedViolationsFound,Warning,ManualReviewRequiredandNoViolationDetected; onlyFailedandSkippedwere ever read. The four were write-dead. That they collapse is not a loss but the two-axis cut: how certain a statement is lives on the finding (Outcome), not on the note. JSON changes inpages[].detail.rule_outcomes[]:statusis dropped (not_runnow says whether and why a rule did not run),wcag_criterion→wcag(array instead of a single value),reason_code→reason,finding_count→findings. -
The translation layer in
wcag::sharedis dropped: Both sides speak the same model, the note froma11y-rulesis passed through instead of translated. Only the WCAG criterion is added, which the shared inventory does not carry on the note. -
Two more rules replaced and deleted, not placed alongside:
parsing::check_parsing_with_page(axe identifierduplicate-id) now runs asids/duplicate,focus_order::check_positive_tabindex_with_pageaskeyboard/positive-tabindex. Both read the DOM via JavaScript, because neitheridnortabindexis an AX property (#QA-030); the shared rules read the same attributes from the CDP dump. JSON changes:rule_idfor these findings isids/duplicateandkeyboard/positive-tabindexrespectively. Severity drops in both cases fromHighto theMediumof the shared inventory — this affects scoring and is deliberately not overridden locally, because a custom severity would break the guarantee that the same finding is named the same everywhere. -
What stands alongside and why:
parsing::check_parsing(duplicate-id-aria, contradictoryaria-ownsrelationships in the AX tree) andfocus_order::check_focus_order(focusable despitearia-hidden) remain — they check something different from the replaced halves.iframe_rulesstill producesduplicate-id, but for the document inside the iframe. -
Finding about our own test coverage: The identifier change to
keyboard/positive-tabindexpropagated intopatterns_disclosure.expected.json— this corpus case expectedfocus-order-semantics, triggered by thetabindex="5"in its fixture, not by the ARIA half of the same identifier. Two rules behind one axe identifier thus cannot be told apart in the corpus. -
Finding about
docs/OUTPUT_CONTRACT.md: The contract claimed thatrule_outcomesuses the same execution states asmodule_runs(completed,partial,failed,skipped,not_applicable). That was already wrong before this switch —RuleOutcomeStatuswroteviolations_found,no_violation_detected,warning,manual_review_required. It was only noticed becausedocs/json-report.schema.jsonlistsrule_outcomesas an unconstrained{"type": "array"}and does not check the shape of the entries at all. The contract text has been updated. -
Still open:
Violationis still auditmysite’s own type and nota11y_report::Finding— the conversion is now possible, but with 295 construction sites and 155 affected files too large for this part. Of 24 shared identifiers, 4 are now adopted (document/lang-missing,document/lang-invalid,ids/duplicate,keyboard/positive-tabindex), 20 are pending. -
Why not more rules: A rule-by-rule capability comparison shows a systematic pattern instead of individual gaps: auditmysite’s rules decide on Chrome’s computed accessibility tree, the shared ones on tags and attributes. Where both serve the same criterion, the AX-based version is therefore usually the broader one. Three documented cases:
lists/invalid-structureonly checks<ul>/<ol>with foreign children, whilerules::list_structureadditionally knows empty lists and<dt>without<dd>and, via roles, also catchesrole="list"on a<div>;tables/header-missinglooks for<th>, whilerules::table_ruleslooks forcolumnheader/rowheaderas roles and thus also finds ARIA-marked header cells;zoom/viewport-lockedcompares thecontentvalue without lowercasing first and thus missesuser-scalable=NO, and it does not know the gradation with whichrules::resize_textseparatesuser-scalable=no(High) frommaximum-scale<2(Medium). These three are candidates for strengthening the shared inventory instead of weakening auditmysite — but that belongs in a separate pull request in a11y-core and must be published there before auditmysite can use it. -
The three gaps are fixed in a11y-core, but not yet published: A separate pull request there (branch
feat/staerkere-strukturregeln, intended as 0.4.0) lowercases the viewport’scontentvalue before comparing, letsrole="list"/role="listitem"androle="columnheader"/role="rowheader"/role="table"count on an equal footing with the tags, and adds the identifierlists/empty. Until this is on crates.io, auditmysite cannot use it — the three rules remain auditmysite’s own until then.
Verified:
cargo clippy --all-targetswithout findings;cargo test --lib1404 tests andcargo test --testsall browser-free binaries green. This time run with Chrome, which the first part owed:cargo test --test detection_corpus_test -- --ignoredgreen (218 s) — that is where it shows that both identifier changes really hold, and exactly there the fixture gap inpatterns_disclosurewas noticed.cargo test --test integration_test -- --ignoredyields 22 passed, 1 failed — the same state as onmain, against which it was explicitly cross-checked:test_concurrent_wait_for_stable_stays_within_its_timeout_budgetalso fails without these changes as soon as the full suite runs concurrently. It is a load-dependent time-budget test, not a regression finding — but a separate one, not previously noted. -
-
Switch to the shared a11y-core crates, first part, 2026-09-19: auditmysite takes its finding model and a first part of its rule inventory from a11y-core (all crates 0.2.0), so that the same finding carries the same identifier in astro-post-audit, auditmysite and liveaudit. Deliberately incremental: this state switches the model and one rule, not the whole inventory.
- Duplicate type definitions removed:
SeverityandViolationEvidencewere structurally identical toa11y_report::Severityanda11y_report::Evidencerespectively — same variants, same order, same serde representation. Both are replaced by the shared types; auditmysite’s own additions toSeverity(German labels, converters from the legacy systems) hang off it asSeverityExt, because inherent methods cannot be added to a foreign type. The formerDisplay for Severityfalls victim to the orphan rule; the one use site usesas_str(), which returns exactly the same strings. JSON unchanged. FindingKindreplaced bya11y_report::Outcome: Variant for variant the same enum under another name. JSON changes: The fieldkindnow writes"fail"/"review"/"pass"/"untested"instead of"violation"/"warning"/"positive"/"not_testable". No fixture and no snapshot observed the field — the change would have gone unnoticed, so a new test now pins the vocabulary explicitly.- CDP DOM as an
a11y-domdocument (accessibility::dom_document): The shared rules are generic over a deliberately DOM-shaped trait, because the majority of them decide on tags and attributes (lang,tabindex,id,alt). The AXTree does not provide these at all. The DOM is now fetched once viaDOM.getDocumentand materialized into an arena;Semanticsis fulfilled via Chrome’s native accessibility tree, not viaaccname— that is the substitute for hosts without a native tree. Both trees find each other via the backend node ID. The root is<html>(the rules checkdoc.root()), shadow-root children hang under their host, iframe contents are not entered (ownlang/title). - 3.1.1 runs as a shared rule, our own is deleted: auditmysite checked 3.1.1 twice and badly
both times.
rules::language::check_languageread the AX propertylanguage, which Chrome synthesizes from locale and context even when the author never set alang— so it was blind for the most common violation. This was compensated bypipeline::apply_lang_attribute_check, a second check pushed in afterwards via JavaScript, which withdrew or added to the first one’s finding. Neither knew invalid language codes. Both are deleted; 3.1.1 now runs asdocument/lang-missing/document/lang-invaliddirectly against the DOM attribute. JSON changes:rule_idfor this finding isdocument/lang-missinginstead ofhtml-has-lang.html-has-langremains, but is now only produced byiframe_rules— for the document inside the iframe, a different finding. - “Not run” is not “passed”: The shared identifiers that auditmysite does not yet carry are
noted per identifier as
shared_rule_not_yet_adoptedinstead of being silently discarded. If the DOM fetch fails, they are noted asFailed, not as passed. - Still open:
Violationis still auditmysite’s own type and nota11y_report::Finding(it lacks fields that auditmysite carries per finding:rule_name,role,name,evidence_screenshot,evidence_viewport);RuleOutcomehas not been switched toRuleRun; of 24 shared identifiers, one rule with 2 identifiers is adopted.
Verified:
cargo clippy --all-features --all-targetswithout findings; 1667 tests in 18 browser-free test binaries passed, 0 failed. The browser-backed corpus tests (detection_corpus_test) need Chrome and did not run. - Duplicate type definitions removed:
-
a11y-core 0.6.0, 2026-09-19 — three rules replaced:
list_structure,table_rulesandmeta_viewport_largeare deleted; their checks now come from the shared inventory.SHARED_RULESthereby carries 12 instead of 4 identifiers.This only became possible after a11y-core closed the gaps on which the replacement would previously have failed: term without definition, presentational table with header cells, table name, the separation of zoom violation and zoom restriction — and while clearing up, a fourth turned up, the orphaned list item (
<li>without a list above it). The old rule ran over the AX tree and saw it; the shared one ran over lists and would never have visited it. Withoutlists/item-outside-listin 0.6.0, the replacement would have lost a check instead of sharing it.One deliberate deviation: The missing table naming is
needs_reviewin the shared inventory, notviolation— whether a table needs a name depends on context, and a violation would be a claim the rule cannot back. The corpus records this.meta_viewport_largedisappears fromPAGE_RULES(47 → 46); the viewport helpers located there have moved toresize_text.rs, which remains their only user and, beyond the 200 % threshold, checks text enlargement itself.Verified: 1,430 browser-free tests, 27 test binaries, clippy
-D warningsandfmtclean, browser corpus with real Chrome (217 s). The corpus completeness test was the guard that found the three remaining fixture references to the old identifiers. -
a11y-core 0.4.0, 2026-09-19 — what cannot yet be replaced: With 0.4.0 the shared structure rules also read
roleattributes (role="list",role="columnheader",role="table"), andpositive-tabindexis back onHigh. Three obvious replacements still do not happen — they would be a loss of capability, not an exchange:- Lists:
lists/invalid-structureandlists/emptycover two of the three checks fromrules/list_structure.rs. Missing is whether a<dt>has an associated definition. - Tables:
tables/header-missingcovers only the header cells.rules/table_rules.rsadditionally checks caption or accessible name, and whether presentational tables wrongly carry header cells. - Viewport:
zoom/viewport-lockedchecksmaximum-scale < 2.0and thus corresponds torules/resize_text.rs(1.4.4, 200 %) — notrules/meta_viewport_large.rs, which checks the same markup at the stricter 500 % threshold. Replacingmeta_viewport_largewould have been the wrong mapping.
Verified: Build and 1,442 browser-free tests against 0.4.0, clippy
-D warningsclean. The three gaps belong in the next a11y-core round, not in a local special case. - Lists:
-
1.5.0, 2026-09-19 — license change to MIT: From this version on, auditmysite is under the MIT license. Earlier releases remain under the license that applied at the time — AGPL-3.0-or-later up to 0.25.x, Business Source License 1.1 from 0.26.0 to 1.4.0; this is recorded in
NOTICEand does not need to be changed retroactively.Why: The rule inventory is moving to a11y-core, so that the same finding is named the same in astro-post-audit (build time), auditmysite (CI/crawl) and liveaudit (running site). If auditmysite stayed under BUSL, the license would have to be decided individually for every module that moves there — a demarcation that would have to be maintained permanently and runs counter to the goal.
Irreversible: A release once published under MIT cannot be taken back. Decided deliberately.
-
1.4.0, 2026-09-18 — upgrade notes: Not a pure patch release. What consumers of the JSON report and the library should check when upgrading (details in the entries below):
- Overall scores shift: Since the per-cause scoring fix, HTML conformance counts with 5 % in
the overall score, SEO drops from 20 % to 15 %. Reports of the same page yield different
overall_scorevalues than under 1.3.x. - Changed JSON values (not just added fields):
rich_snippets_potentialnames the bare schema type ("FAQPage"instead of"FAQ Rich Snippet"); the keys inmobile.issues[].values.small_by_contextare canonically English (other/forminstead ofsonstige/formular). - Two SEO findings are dropped:
pagination_missing_rel_linksandpwa_missing_service_workerare no longer emitted. - Additive:
security.issues[].valuesandmobile.issues[].valuescarry the interpolated raw values; when empty they are omitted.header,issue_typeandmessageremain unchanged. - Rust API breaks:
security::coop_corp_verification_textis gone (merged intosecurity_issue_text),SecurityIssueandMobileIssuehave a new public fieldvalues, anda11y_journey::link_inventory::analysenow takes page and fallback language instead of a locale. - Known consumer: Studio was stuck on 1.3.1 (see auto-memory) — check before upgrading.
- Overall scores shift: Since the per-cause scoring fix, HTML conformance counts with 5 % in
the overall score, SEO drops from 20 % to 15 %. Reports of the same page yield different
-
Report statements: contradictions and overclaims fixed, 2026-09-18: Triggered by an external critique of the casoon.de report. In several places the report claimed more than the measurement supports, and contradicted itself in doing so.
- Link text heuristic produced false WCAG 2.4.4 claims:
a11y_journey::link_inventory’sis_genericcompared vialower.contains(stopword), i.e. as a substring. As a result, any descriptive link text that contained a stopword anywhere counted as generic — on casoon.de “Claude-Code-Kontingent: Der Verlauf kostet mehr als jede Konfiguration” (the history costs more than any configuration; 200 characters of card text), “Mehr über Jörn Seidel” (More about Jörn Seidel), “Mehr Sichtbarkeit bei Google & KI” (More visibility on Google & AI); the English list additionally hit German words in the middle viahere/more/open. All four reported links were false positives. Now an exact comparison on the normalized name (lowercase, surrounding non-alphanumerics removed, so that “Mehr erfahren »” (Learn more ») still matches). In addition, the detection language now follows the page language (<html lang>, read viaeval_stringin the journey hook) instead of the run language, with an explicitSTOPWORD_LOCALEScheck —I18n::newsilently returns the German bundle for unknown locales, so a French page would otherwise have been scanned with German stopwords (#406 separation of detection vs. message language). Four regression tests, including the three real casoon.de names. The finding text also no longer claims “do not meet WCAG 2.4.4” but marks itself as a heuristic warning requiring manual review. - Three evidence classes instead of one: New
EvidenceClasses(confirmed WCAG violations / heuristic warnings / criteria to be checked manually) on theFindingsBlock, computed once in the builder. Scores remain unchanged — they are still derived solely from the confirmed violations. The classes exist so that no count sentence can say “0 findings” while four pages later there are findings: The cause analysis now says “Keine bestätigten WCAG-Verstöße … Es bleiben N Warnung(en) und M Prüfhinweis(e)” (No confirmed WCAG violations … N warning(s) and M review note(s) remain) instead of “Es wurden keine Barrierefreiheits-Befunde erkannt” (No accessibility findings were detected), and below the count strip of the management view it states explicitly that only confirmed violations are counted there. The “Heuristische Warnungen” (heuristic warnings) metric value now also counts the journey and screen reader signals, no longer just the WCAG engine’s warnings. - BFSG statements reduced to technical criteria: “BFSG-Prüfung: keine Verstöße im geprüften Umfang” (BFSG check: no violations within the scope checked; green) and the checklist row “Rechtliche Konformität (BFSG) — Geringes Compliance-Risiko” (Legal conformity (BFSG) — Low compliance risk) read like legal clearance. A scanner can determine neither whether a service falls under the BFSG at all, nor whether all statutory requirements are met. Both are now called “BFSG-relevante technische Kriterien” (BFSG-relevant technical criteria) and say explicitly “Dies ist keine rechtliche Konformitätsprüfung.” (This is not a legal conformity check.)
- Breadcrumb contradiction (
seo::serp): The SERP signal only checked the type presence ofBreadcrumbListand then reported “Google zeigt Pfadangabe im Listeneintrag” (Google shows path information in the list entry) — while the schema table of the same report printed “Pflichtangaben fehlen: itemListElement (minimum 2 entries)” (Required fields missing: itemListElement (minimum 2 entries)). The signal now consults the already existingrule_assessments; an incomplete schema becomes a warning naming the missing fields. Two regression tests. - Measures list across modules: “Die 5 wichtigsten Maßnahmen” (The 5 most important
measures) was fed exclusively from WCAG finding groups and, at 0 WCAG findings, reported
“Keine dringenden Maßnahmen erforderlich” (No urgent measures required) — although the same
report documented a duplicate host, a faulty breadcrumb schema, 13,756 DOM nodes and a CSP
misconfiguration. New
cross_module_measuresfills up the list from security, mobile, SEO and performance recommendations, sorted by severity and then by the overall points the module costs. The empty text of the measures plan no longer denies findings but refers to the module sections. - Terminology and PDF artifacts: TBT is no longer presented as a Core Web Vital
(
perf-lab-data-bodynames LCP/CLS as CWV and TBT as a lab approximation, because INP cannot be measured headless); the sections “Desktop/Mobile — Core Web Vitals” are now called “Kennzahlen (Labormessung)” (Metrics (lab measurement)), because their strips also contain FCP and TTFB, the additional table is called “Weitere Lab-Metriken” (Further lab metrics). The thresholds for DOM nodes, load time and DOMContentLoaded are labeled “Richtwert” (guideline) instead of “Ziel” (target) (Lighthouse heuristic, not a standard). Internal journey IDs (tab_walk,disclosure_0,skip_link_0) no longer appear raw in the customer PDF but as labels, falling back to the raw ID for unknown journeys. The callout above the interactive findings is no longer green (the success branch was unreachable anyway, because the section is only rendered when findings exist) and is grammatically correct in the singular.rich_snippet_typeis no longer called “FAQ Rich Snippet” but names the bare schema type — existing markup is not a promise about the search presentation. The overall verdict says “im automatisierten Accessibility-Prüfumfang” (within the automated accessibility scope) instead of “im Accessibility-Audit” (in the accessibility audit). - Verified:
cargo test --all-features(1376 lib plus integration tests green),cargo clippy --all-features --all-targetswithout warnings,cargo fmt --check, and a real run against www.casoon.de — the link text finding is gone (2 → 1 interactive findings), the breadcrumb signal is at “Warnung” (warning) with a rationale, the measures list carries five cross-module items, andreport-lintstill reports no findings. Score unchanged (Accessibility 100, Overall 92). - Two technically questionable SEO rules removed (addendum of the same day):
pagination_missing_rel_linksreported missingrel="prev"/rel="next"markup as an SEO problem — Google has not used the pair for indexing since 2019. The remaining pagination checks stay: they only trigger when rel links are actually present and wrong (self-reference, prev == next), and that is broken markup in any case.pwa_missing_service_workerreported a missing service worker registration as soon as a web app manifest was present — but a manifest is routinely shipped solely for icons and theme color (on casoon.de exactly this case: valid manifest,display: standalone, no registration) and does not evidence an intent to be an installable, offline-capable PWA. Theservice_worker_*fields remain as information in the JSON. Both tests replaced by negative tests. Result on casoon.de: “Technische SEO-Probleme” (Technical SEO problems) shrinks from three rows to one (the real duplicate host finding). - Measures list merges findings of the same kind: After the removal of the two SEO rules,
three separate CSP misconfigurations moved up and occupied three of the five places.
cross_module_measuresnow merges findings with the same module and the same title into one measure and appends “(+N weitere gleicher Art)” (+N more of the same kind) — three CSP findings are one measure “CSP korrigieren” (fix CSP).TopMeasurecarries title and detail separately for this; performance and technical SEO recommendations have no title of their own and are rendered without a separator. Three rendering tests. Also corrected along the way: the mobile entries carried the raw snake_case category key (touch_targets,fonts) — they now use the samemobile_category_labelthat the mobile module section already used (“Touch-Targets”, “Schriftgrößen” (font sizes)). - Security and mobile messages localized (addendum of the same day, #406): Both modules
baked English prose into
messageand the PDF renderer output it unchanged in the German report (“CSP allows unsafe-inline scripts without nonce/hash protection”, “1 touch targets are too small”). Both now follow the kind-enum pattern:SecurityIssueKind(19 variants) andMobileIssueKind(6) plus*IssueValuesfor the interpolated raw values, and a puresecurity_issue_text/mobile_issue_texteach as the SINGLE text source — the analysis calls it withen=true, the PDF presentation layer vialocalized_message()with the run language. The constructorssecurity_issue/mobile_issuebuildmessagefrom it, so that no call site writes a message text by hand any more.kind()is derived from the already storedheader/issue_typefields instead of being serialized as a fourth field, so that reports and cached artifacts of older builds keep localizing unchanged; unknown types fall back to the stored canonical version. JSON contract remains identical (header,issue_type,messageunchanged English;valuesis additive and omitted when empty), secured bysecurity_issue_types_match_the_stored_contract. Also corrected along the way: the mobile page script wrote the German context keyssonstige/formularinto the supposedly English-canonical JSON — nowother/form, localized viamobile_context_label(unknown keys pass through unchanged). The #578 special solutioncoop_corp_verification_textis gone, it was merged intosecurity_issue_text. Guard tests per module (every variant localized, EN without umlauts) plus fallback and round-trip tests. - Check inventory from the enum instead of the source text:
tests/common/nonwcag_rule_inventory.rsdetermined the canonical security check IDs by searchingsrc/security/mod.rsforSecurityIssue { header: "…", issue_type: "…" }string literals — after the refactoring there were no literals there any more and the corpus test failed. The IDs now come fromsecurity::all_security_check_ids(), derived fromSecurityIssueKind::ALL; the text scan along with the hand-maintainedCSP_DYNAMIC_DIRECTIVE_IDSlist is dropped, and the required CSP directives live in one place asCSP_REQUIRED_DIRECTIVES. - Audit scope on the cover page (addendum of the same day): The scope line stood only on
page 2, the cover page showed “Website-Qualitätsbericht · casoon.de · 92” (Website quality
report · casoon.de · 92) and a bare “Barrierefreiheit 100” (Accessibility 100) gauge — anyone
who stops there reads both as a statement about the whole website. The line now comes from a
common source (
single_report::audit_scope_line) and is in the cover subtitle; the label above the gauge strip reads “MODULE · 0–100 IM AUTOMATISIERTEN PRÜFUMFANG · HÖHER IST BESSER” (MODULES · 0–100 WITHIN THE AUTOMATED SCOPE · HIGHER IS BETTER). - Created and fixed a layout bug along the way: The first attempt appended the scope line to
the full kicker, the subtitle wrapped onto two lines and pushed the labels of the lower gauge
row (Mobile, UX, Journey) off the page — the Typst template gives every gauge label a fixed
22pt box and the cover page does not grow, the overflow was silently discarded. Discovered via
the rendered PDF, not visible in the Typst source.
narrative-cover-kickeris therefore now short (“Technischer Website-Check” (Technical website check) instead of “… mit Fokus auf Accessibility, SEO und Performance” (… with a focus on accessibility, SEO and performance)) — the gauge strip directly below names the dropped areas anyway. New guardtest_cover_subtitle_stays_on_one_line(character budget 95, measured: ~83 fit, 132 wrapped) plustest_cover_carries_scope_line_and_gauge_qualifier. - Deliberately not changed: the score inflation.
- Link text heuristic produced false WCAG 2.4.4 claims:
-
Product documentation: contradictions with actual behavior corrected, 2026-09-17: Three confirmed discrepancies fixed. (1)
README.md’s HTML5 conformance description still said “score-neutral”, although the module has really flowed into the overall score since the per-cause scoring fix of 2026-09-16 (contributes_to_overall: true,weight_pct: 5). (2)src/lib.rs’s module overview listed “HTML” as a report format, although no HTML export exists. (3) The short description said in several places (Cargo.toml,src/lib.rs,src/cli/args.rs,src/cli/plan.rs’s runtime CLI banner,CLAUDE.md,docs/ARCHITECTURE.md) a blanket “WCAG 2.1”, whileREADME.mdalready correctly labels individual WCAG 2.2 rules (2.4.11/2.4.12, 3.3.7, 2.5.8) separately — unified everywhere to “WCAG 2.1 AA (+ select 2.2 criteria)”. In the process, one more, directly adjacent finding was corrected:src/lib.rs’s “Comprehensive: Checks WCAG 2.1 Level A, AA, and AAA” contradictedREADME.md’s own statement “AAA is not fully implemented yet” — now precise: 36 of 50 automated A/AA criteria (docs/PARITY_CONTRACT.jsonc), plus selected 2.2 and individual AAA criteria.docs/browser-architecture.md’s outdated Homebrew formula example was deliberately left untouched — the file already declares itself an old, not fully implemented collection of proposals, not current behavior documentation. Three new, machine-checkable regression guards inscripts/release-check.sh(unqualified “WCAG 2.1 Accessibility Checker” phrase, HTML5 conformance “score-neutral”, HTML as a report format), each verified with a manual negative case (old text temporarily restored → check fails; reverted → green again). -
Release workflow: quality gates enforced before the artifact build, 2026-09-17:
.github/workflows/release.yml’sbuildjob previously depended only onverify-version— tests, formatting, Clippy and the dependency advisory gate were not a prerequisite for av*tag release..github/workflows/ci.ymlgets an additionalworkflow_call:trigger (alongsidepush/pull_request),release.ymlnow calls it as a new jobquality-gatesviauses: ./.github/workflows/ci.ymlon the same commit SHA, whichbuildnow has as a prerequisite in addition toverify-version— technically secured via the SHA (same checkout), not just via the branch name.browser-smoke/coveragedeliberately do not run again in this (their ownif: github.event_name == 'push' || ... == 'pull_request'already excludesworkflow_call) — the Chrome/corpus tests already ran at the merge tomainand run again locally via the pre-push hook (scripts/release-check.sh) before a release tag is even pushed; repeating them in the release gate would have slowed down every release unnecessarily. Both platform build steps get--locked, so that releases are built reproducibly from the checked-inCargo.lock. Two newrelease_contract_tests(test_release_build_requires_quality_gates_to_pass_first,test_release_build_uses_locked_lockfile) prevent the release job from running into the artifact build without a gate in the future — negative case verified (needs:reset toverify-versiononly → test fails). -
Dependency security: RustSec gate added, 2026-09-17:
cargo auditreported 9 vulnerabilities inCargo.lock. Patch-level updates without API impact were applied:rustls0.23.40 → 0.23.45 (RUSTSEC-2026-0285),crossbeam-epoch0.9.18 → 0.9.21 (RUSTSEC-2026-0204),quinn-proto0.11.14 → 0.11.18 (RUSTSEC-2026-0185).lopdf(dev dependency, PDF test helper) was raised from 0.34 to 0.45 (RUSTSEC-2026-0187) — the API in use (Document::load_mem,.objects,.catalog(),.get_pages(),.extract_text()) stayed unchanged across the version jump, all PDF tests still green. Two advisories remain open and are documented individually with a justification in.cargo/audit.tomlinstead of being blanket-ignored:rsa(RUSTSEC-2023-0071, only via the optionalai-transparency/c2pachain, no upstream patch available, auditmysite holds no private RSA key) andquick-xml(RUSTSEC-2026-0195/-0194, two transitive copies viahayagriva/syntect, each already at the version ceiling allowed by the parent packages — the fix requires an upstream release of thetypst/renderreportchain; the affected inputs are bundled, non-attacker-controlled data such as citation styles and theme.plistfiles, not the content of audited web pages). A new CI jobdependency-audit(.github/workflows/ci.yml) runscargo auditon every PR. -
Screen reader module: reading order counted layout artifacts, 2026-09-17: Triggered by the review of a RankingLab report (Sachsen-Anhalt): the section “Screenreader-Lesereihenfolge” (screen reader reading order) reported 237 “angekündigte Knoten” (announced nodes) and four findings “Langer Abschnitt ohne Landmark, Überschrift oder Fokusziel” (long section without landmark, heading or focus target) — with heading and landmark quality at 100/100 at the same time. Reproduced exactly locally at www.sachsen-anhalt.de. Cause:
linearizeemitted every non-ignored AX node as aReadingItem, including 67InlineTextBox— Blink’s line fragments into which aStaticTextis split by a line break. They exist for caret/selection bounds, are never handed to an assistive technology, and carried the same text two to four times. As a result, every number derived from the reading order was inflated: the desert heuristic counted a news teaser card made of four announcements (headline, date, teaser, image credit) as a 23-entry desert; all four findings of the page were false positives, produced solely by the line break. New:linearizer::is_layout_only_roleskipsInlineTextBoxwhen emitting, but keeps traversing (descendants are preserved);analyzer::carries_announced_contentcounts only items with their own name or value for the desert distance, so empty wrappers (figure,paragraph,group,generic,Figcaption,list) no longer count the same announcement twice — role-agnostic, agroupwith anaria-labelstill counts.CONSENT_WALL_NODE_THRESHOLDwas recalibrated from 200 to 145, because the node count drops by the same proportion. Result at sachsen-anhalt.de: 237 → 170 nodes, four false positives gone, the one real finding (button without accessible name, 4.1.2 → § 12 No. 3 BFSGV) remains; tab stops and all three quality values unchanged. Verified by a before/after run and 4 new unit tests. -
HTML conformance: score counted occurrences instead of causes, 2026-09-16: The module was at
weight_pct: 0with the report note that its HTML5 schema did not know RDFa/Open Graph attributes andog:meta tags therefore produced false positives. Both were outdated: the RDFa gap has been closed sincehtml-conform0.2.1 (schema/html5/meta.rnc, block “RDFa Lite Property Metadata”); checked directly against a page withog:tags — not a single such finding. The actual defect was the penalty formulaerror_count * 10: it counted per occurrence, not per cause. One faulty template element produces one occurrence per rendering, so every real page floored at 0 — at sachsen-anhalt.de, 201 of the 208 reported errors traced back to a single<link as=…>withoutrel, 6 distinct causes in total. New:html_conform::defect_keynormalizes rule ID plus message (backtick values andat line:columnremoved) into one cause;score_findingspenalizes per cause, with a capped accumulation surcharge (at most double the base) and rank damping (first cause full, second/third half, the rest a quarter), so that the score stays meaningful over the whole range instead of saturating at 0. Sachsen-anhalt.de thus goes from 0 → 64. The module counts toward the overall score again (5 %, moved over from SEO: SEO 20 → 15) and reportsmeasurement_type: "measured"instead of"heuristic". Report side: new fielddistinct_defect_countin the JSON, KPI “Ursachen” (causes) in the PDF, findings table one row per cause with a column “Vorkommen” (occurrences) (instead of 20 redundant occurrence rows),ScoreCardwith the normal grade band again, the outdated RDFa note replaced by an explanation of the cause counting. Verified at sachsen-anhalt.de (JSON +--debug-typ) and with 8 new unit tests. -
PDF abort due to foreign glyphs and panic in the HTML content model, 2026-09-16: (1) A single icon-font character on the audited page aborted the entire PDF generation: link texts, selectors and custom property names carry private-use code points into the report, Typst falls back to
LastResortand the PDF/UA export fails (PDF/UA-1 error: the text "\u{e900}" could not be displayed). Affected 8 of 84 domains of a RankingLab run (among them kit.edu, fu-berlin.de, uni-goettingen.de). New:output/pdf/sanitize.rsremoves private-use characters from all strings of theRenderRequest(a single chokepoint afterbuilder.build(), hence no field-by-field upkeep) and learns the remaining non-displayable characters from the compile error: discard the character, re-render, at most 8 rounds — this is how a↳from a CSS variable name was caught on jyu.fi. Presentation layer only; the canonical JSON keeps the original text so that selectors remain copyable. (2)enclosing_tag_stack(wcag/rules/html_content_model.rs) panicked on ikea.com because the byte offset of the external parser lay in the middle of a\u{a0}— contrary to its own promise “never panics”. The offset is now reset to the character boundary, the raw-text close-tag comparison runs over bytes instead ofstrslices. Verified on the live domains plus two regression tests each. -
1.3.1 fixes, 2026-09-16 (#581, #582, #583): (1) The accessibility subcategory and security category scores from
d6daf7bappeared only in the PDF, not in the JSON report — the JSON builder (build_page/PageDetail) never read them. They are nowpages[].detail.accessibility_subcategory_scores/security_category_scores({ name, score }, canonically English) in the single report, with a schema, registry andOUTPUT_CONTRACT.mdentry; batch details stay compact and omit both. (2) The CI step for the four detection corpus binaries aborted at the first failure, the others never ran (this is what happened in the first 1.3.0 CI run) — now one step per binary withif: !cancelled(), andrelease-check.shcollects failures and aborts only at the end. (3)Cargo.lockheld the deletedspin 0.9.8(vialazy_static) — raised to 0.9.9. -
Blank page after empty report part fixed, renderreport 0.5.1, 2026-09-15: the
pdf-smoketesttest_single_pdf_technical_pages_are_not_blank_when_pdftoppm_is_availablefailed: in the technical fixture, the part 3 divider page (with its own trailingPageBreakby then) was followed by no module content but directly by the appendix with its ownPageBreak— with a blank page in between. The cause lay in renderreport: forLayoutHint::AlwaysNewPage(onlypage-breakuses it) the engine wrote a hard#pagebreak()before every otherwise soft break component, so two adjacent breaks produced a blank page. renderreport 0.5.1 writes a soft break there (with a regression test that was red without the fix). Real reports were not affected in three live runs (standard, technical, without--full), because part 3 always has content there. -
Finish batch progress before the report, 2026-09-15 (#580):
run_batch_mode(src/cli/runners.rs) calledfinish_verdictonly afteroutput_batch_reportoroutput_batch_as_single_reports— in a TTY the active bar drew over the report, in a pipe the verdict line came after the report (regression against the #530 acceptance criterion). The order is now fixed inBatchLifecyclePresenter::finish_then_render, both branches use it. Regression testlifecycle_is_finished_before_report_renders; verified live via pipe with the reproduction from the issue (verdict line before the report, ANSI-free). -
CLAUDE.md’s “Current State” history moved toCHANGELOG.md, 2026-09-06: the file had grown to 1058 lines, of which 805 were pure chronological history.CLAUDE.mdnow keeps only working rules + a short pointer here; new entries go here from now on, no longer intoCLAUDE.md. Pure cut and paste, no entry changed in content. -
Review batch fully completed, 2026-09-06 (items 7–11): Item 7 (condense the management summary) was implemented as a “lighter condensation” at the user’s request instead of exactly 2 pages: the strengths/weaknesses cards of
render_module_split_dashboardsshowed the same 4-5 weighted modules (Accessibility/Performance/Security/Mobile) for a third time (after the radar chart and the new score driver table from item 2) — now filtered tomeasurement_type != "measured", so it shows only the unweighted indicator modules (UX, Journey, Search Experience, …), including an adapted “all good” fallback message (scoped to “additional indicator modules” instead of “all modules” across the board). New leverage sentence on the action plan page (“Die N wichtigsten Ursachen erklären rund X % der erkannten Vorkommen — ihre Behebung hat die größte Hebelwirkung …”, i.e. “the N most important causes explain about X % of the detected occurrences — fixing them has the greatest leverage …”) — shares its computation with the diagnosis sentence from item 3 via a new sharedcompute_problem_concentrationfunction (one number, two differently worded sentences on two pages, no duplicate text). Both changes verified by a--debug-typsmoke test (cards disappear correctly when no indicator modules are present; the leverage sentence computes “4 causes, 50 %, 8 occurrences” correctly on the fixture). Items 8–11 (detection corpus tests in the release script, README accuracy claim, file size confirmation, version number + module list) were small, independently verified fixes. -
Report review batch items 1–6 implemented, 2026-09-06 (external report review of inros-lackner-de): seven distilled items, six implemented (item 7 — management summary 4→2 pages — deliberately deferred, a layout decision needs separate user confirmation). Item 1 (P0) uncovered a considerably larger bug than reported: the reported case (a
landmark-uniquefinding showed the wrong, generic WCAG 1.3.1 title “Fehlende semantische Struktur” (missing semantic structure) instead of “Landmarks nicht eindeutig benannt” (landmarks not uniquely named)) was a simple missingexplanations.rsentry (#571 pattern). The root-cause investigation, however, uncovered a second, structural bug inwcag_group_key(src/audit/normalized.rs): everyaxe_idwithout its ownLEGACY_WCAG_MAPentry falls back to the raw WCAG criterion ID as grouping key — if two independent checks share a criterion (e.g. several 1.3.1 landmark checks, several 4.1.2 ARIA checks), their violations blend into a single finding with a summed occurrence count and the title of whichever hit came first. A systematic scan ofsrc/wcag/rules/*.rsfound 43 affected axe_ids across 10 WCAG criteria (1.1.1, 1.3.1, 1.4.4, 2.1.1, 2.4.1, 2.4.4, 2.4.7, 3.3.1, 4.1.1, 4.1.2) — not just the 14 axe_ids under 1.3.1 that the reported case suggested. Every affected axe_id got its owntaxonomy::rules::Ruleentry +LEGACY_WCAG_MAPentry; 32 of them additionally got a new bilingualRuleExplanation, 3 (region,focusable-no-role,link-name-context) already had a matching explanation and only needed the missing rule/map entry. Two axe_id string collisions between independent checks were discovered and resolved (renamed, since a globalLEGACY_WCAG_MAPentry would otherwise have wrongly merged both checks):labels.rs’s 4.1.2 check"label"→"control-missing-label"(collision with the deliberately shared 3.3.2"label"ofinstructions.rs/form_rules.rs),link_purpose_link_only.rs‘s 2.4.9 check"link-name"→"link-name-only"(collision with the 2.4.4"link-name"oflink_purpose.rs). An already existing test (tests/wcag_coverage.rs::no_undocumented_severity_collisions_in_group_key_mechanism, part of the QA-009 follow-up) confirmed the fix independently: it required removing 5 of the 6 documentedALLOWED_MIXED_SEVERITY_GROUPSexceptions, because their severity mix no longer occurs after the fix — the remaining3.3.2exception is a deliberately shared axe_id (not a grouping bug). Item 2 (score driver table): newModulesBlock.module_scores(raw fromNormalizedReport.module_scores, not from thedashboardreshaped for the radar cards, since e.g. the “Sichtbarkeit & Nutzerverständnis” (visibility & user understanding) card merges SEO with heuristic AI visibility signals into a composite score that is not the raw SEO score with SEO’s real weight) feeds a new table directly after the quality profile radar: module/score/weight/classification (“Größter Schwachpunkt” (biggest weak point)/“Erheblicher Risikotreiber” (significant risk driver)/ “Stabilisiert Gesamtwert” (stabilizes overall value)), classified by(100-score)*weight_pctdrag instead of raw score (a bug found and fixed by a live smoke test: the first version sorted by score with weight only as a tie-breaker and wrongly picked the low-weighted Security 30 instead of the highly weighted Accessibility 40 as the “biggest weak point” — exactly the case the review named as an example). Item 3: new generated diagnosis sentence (“N Vorkommen erkannt, rund X % auf 4 wiederkehrende Ursachen zurückführbar, besonders betroffen: …”, i.e. “N occurrences detected, about X % traceable to 4 recurring causes, particularly affected: …”) directly after the score driver table, scope deliberately Accessibility+SEO combined (user decision). Item 4: “Root Cause” wordings unified to a more cautious phrasing (“X Vorkommen folgen demselben Muster — deutet stark auf … hin, bestätigt erst mit Belegen von weiteren Seiten”, i.e. “X occurrences follow the same pattern — strongly suggests …, confirmed only with evidence from further pages”), and in doing so an independent #406 localization leak was found and fixed (src/output/pdf/findings.rs: the “Root Cause” card label was hard-coded English, even in German reports) and an identical hard-coded duplicate inbuilder/batch.rswas fixed along with it. Batch reports’TemplateCluster::confidence(confirmed/likely) already met the question posed for a stronger, actually justified wording given multi-page evidence — no change needed. Item 5: new scoring subsystem, because contrary to the assumption in the item no real 0–100 subcategory score existed yet (only a taxonomy categorization for labels and a heuristic top-3 text). Accessibility:compute_accessibility_subcategory_scorespartitions the same rawViolations bytaxonomy::Subcategory(via the already existingwcag_group_keyresolution) and runs the realAccessibilityScorer::calculate_scoreper subcategory subset — no newly invented penalty scheme. Security has no WCAG-equivalent rule registry; the newsecurity::SecurityCategory(response headers/transport security/access policies/ third-party exposure) groupsSecurityIssue.headerstrings and uses the same severity→penalty mapping ascalculate_security_score. The PDF shows “Kritische Schwächen: … · Vergleichsweise stabil: …” (critical weaknesses: … · comparatively stable: …) (threshold: the existingFIVE_BANDcutoff at 60, no new threshold invented), per module only if both sides are non-empty. Item 6: newRoadmapItemData.leverage(“Sehr hoch”/“Hoch”/“Niedrig”, i.e. very high/high/low; fixed rule fromoccurrence_count≥10 → Sehr hoch, else ≥5 occurrences or quick fix + high priority → Hoch, else Niedrig — the threshold of 10 deliberately mirrors the existingFindingGroup::is_component_issuethreshold) as a new line in the action plan card text, wording “betroffen” (affected) instead of “behoben” (fixed) (consistent with item 4). All six items verified bycargo test/--no-default-features/--all-features+cargo clippy --all-targets --all-features -D warnings+ several--debug-typsmoke tests against enriched fixtures (1368 tests in the fullpdf_testfeature run, 0 failures). -
CI permanently red for several weeks — real cause found and fixed, 2026-09-06 (repo cleanup session): while cleaning up,
gh run listwas checked (never done before — locally onlycargo check --all-featureswas ever verified via the pre-push hook, never the actual CI status) and it turned out that practically every push since at least 2026-07-16 failed in CI. Cause: the testastro_structured_data_exports_work_...insrc/seo/schema.rsloads its fixture viainclude_str!("../../tests/fixtures/astro_structured_data_components.json")— this file existed on disk locally but was never tracked in Git (caught by.gitignore’s blanket*.json, no whitelist exception as for the other fixture directories).cargo check(the pre-push hook) does not compile test targets and never noticed it; everycargo test/cargo clippy --all-targetsrun in CI, on the other hand, aborted on it with a hardinclude_str!compile error before a single test ran — affecting practically all CI jobs (Check & Test, PDF Smoke Tests, Coverage). Same class of error as thedetection_corpus_nonwcag/*/*.htmlgitignore gap found earlier the same day (symptom: a fixture file present locally but never committed), but here with real CI impact instead of merely “would get lost the next time one is added”..gitignorewas extended by!tests/fixtures/astro_structured_data_components.json, and the file was checked in. In the processtests/wcag_fixtures/*.html(7 files, used bytests/coverage_matrix.rsvia a runtime directory scan, noinclude_str!— hence no CI blocker, but the same tracking gap) was fixed as well. Verified locally with the exact CI commands:cargo clippy --all-targets --all-features -- -D warnings,cargo clippy --no-default-features -- -D warnings,cargo test --no-default-features— all green. -
Repo consolidation, 2026-09-06: removed an orphaned worktree + branch
worktree-agent-*(0 own commits that were not already in main — a pure leftover of an oldisolation: "worktree"agent run).archive/main-history(local + origin) deleted at the explicit request of the user, onlymainexists now. Stray files in the project root removed (delete.html, a leftover Shopify page dump; a separate leftover test JSON from a previous session).reports/(68 MB) andtmp/pdfs/(local, gitignored test report outputs) emptied completely at the user’s request — regenerable, no Git tracking affected. Localtarget/folder remnant cleaned up (CARGO_TARGET_DIRactually points to~/.cargo/target, seereference_cargo_target_dir.md). -
Non-WCAG detection corpus for vulnerable_libs/schema_rules filled, 2026-09-06 (remaining scope of #558 completed — the security domain was already done): both domains need a real Chrome/CDP (unlike security, which is only an HTTP fetch), hence two new
#[ignore]-gated tests analogous totests/detection_corpus_test.rs. vulnerable_libs (8/8 covered):tests/vulnerable_libs_detection_corpus_test.rsdiffs the real output ofanalyze_vulnerable_librariesagainst 4 combined HTML fixtures (no more needed, since minimal global stubs suffice —window.jQuery.fn.jqueryetc., no real library functionality necessary). Split into 4 instead of 2 files because of a real constraint documented by the module itself: Lodash and Underscore share the global_and would overwrite each other if used together. Prototype/MooTools are flagged unconditionally as vulnerable in the code (unmaintained), so they have only a violation fixture, no pass fixture. A real, pre-existing bug was found and fixed in the process:.gitignore’s*.htmlblock had an exception fortests/fixtures/detection_corpus/*.html(WCAG corpus), but none for the equivalentdetection_corpus_nonwcag/*/*.html— new fixtures in this domain would have been present locally but never checked in, unnoticed. schema_rules (17/17 covered): before building the full corpus it was checked and found that the pureassess_noderule logic ofschema_rules.rsalready has very thorough pure-Rust unit tests for 14 of 17 features (edge cases such as EventRescheduled, remote jobs, merchant-vs-editorial context) — presented to the user, who nevertheless decided on the full Chrome corpus (tracking consistency with the security/vulnerable_libs domain mattering more than avoiding redundancy).tests/schema_rules_detection_corpus_test.rsdiffs the real output ofdetect_structured_dataagainst 2 combined fixtures (all 17 types complete/valid → expected “pass”; the 11 types that can have required fields at all, incomplete → expected “violation”).merchant_listingdeliberately expectsneeds_review, not pass/violation:detect_structured_dataalways evaluates rules withProductRuleContext::Indeterminate, the real page intent context is only set later by thederivestep ofseo::moduleviaschema_fit/refresh_rule_assessments— this is real, correct behavior of this entry point, not a test gap. Five features (Article/Organization/WebPage/WebSite/Person) have no required fields inassess_nodeand can structurally never become “violation” — tested as “pass” in the “complete” fixture, no separate violation fixture needed. Both new tests were verified with a deliberately falsifiedexpected.jsonto show that they detect a real diff (reset afterwards). -
Two new best-practice ARIA hygiene rules, 2026-09-06 (last item from the current Insights article batch):
redundant_role.rs(4.1.2/redundant-role, e.g.<button role="button">,<a href="..." role="link">— fixed, context-independent tag-to-implicit-role table; tags with an ancestor-dependent role such as<header>/<footer>deliberately excluded) andfake_navigation_link.rs(4.1.2/link-as-button,<a href="#" onclick="...">/href="javascript:..."as a button substitute — only inlineonclick, the same boundary asclick_handlers.rs). BothSeverity::Low,WcagLevel::A, tag"best-practice", registered in the normalPageRuleEntrymechanism (page_rules.rs), no new infrastructure. Two real bugs found and fixed during live verification, not just wording: (1) the first version built selectors manually from tag+id+class (asclick_handlers.rsdoes) — with several same-named tags without id/class (e.g. two<a>elements without a class) both collided on the same selector string"a"; not reproduced in the fixture at first and thus unnoticed, but real: the doc comment ofjs_helpers::CSS_SELECTOR_JSitself explicitly warns about it (“Never falls back to a bare tag name”). Switched to the more robust, already existing__amsCssSelectorhelper (likearia_prohibited_attr.rs), verified live:body > a:nth-of-type(1)/:nth-of-type(3)/:nth-of-type(4)now remain distinguishable. (2) Naive string concatenation ofCSS_SELECTOR_JS(a top-levelfunctiondeclaration) directly followed by the rule’s own standalone(function(){...})()produced a real live error (TypeError: (intermediate value)(intermediate value)... is not a function) —Runtime.evaluateparses a leadingfunctiontoken at expression position as a function expression instead of a declaration, so the following IIFE is interpreted as a function call argument instead of a standalone statement. Fixed following the same pattern asaria_prohibited_attr.rs: embed both in an explicit outer(function() { ... })(), instead of concatenating two independent top-level snippets — missed on the first attempt becauseclick_handlers.rs(the original model) does not useCSS_SELECTOR_JSat all and this concatenation problem therefore never occurs there. Verified live against a localfile://fixture (5 test cases: 3× redundant role, 2× fake navigation, 2× correctly unflagged legitimate cases) — both rules fire exactly as expected, no false positives. Two hard-coded page rule counter regression tests (level_a_filter_includes_only_level_a_rules,level_aa_filter_includes_aa_plus_a_rules,page_rules.rs) were counted up accordingly (36→38, 47→49). No new detection corpus fixture entry (#556 format) — in line with the existing precedent of pure DOM-JS rules without an offline unit test in this module. -
4.1.3 deepening — late live region insertion detected, 2026-09-06: new
InteractiveFindingKind::FormErrorLiveRegionLateInsertion(Severity::Low, advisory) insrc/a11y_journey/form_error.rs— an extension of the existing form error journey instead of a new detection path, as required:check_error_statealready capturedlive_before(before submit) andlive_after(after submit);new_live = live_after && !live_beforehad so far been used only internally to deriveFormErrorInvalidWithoutLiveRegion, never reported as a finding of its own. New check: whennew_liveis true (the live region announced correctly but was not in the DOM initially), this is now reported as a standalone advisory finding — clearly separated from the existing “no announcement at all” case (FormErrorInvalidWithoutLiveRegion/silent failure, which both require!new_live, so never fire at the same time as the new finding) and from the polish conflict check instatus_messages.rs(unchanged). Deliberately advisory/Low instead of High: the announcement worked in this run, it is a robustness recommendation for other browser/AT combinations, not a confirmed error. Checked live against casoon.de (home page + /kontakt) — no form error journey candidate was detected there (no matching form/submit structure on these two pages), so the new code path is verified only by build/clippy/the full test suite (1318 tests) and the EN locale umlaut guard, not by a live observed hit — like all otherFormError*findings in this file,form_error.rshas no test infrastructure of its own (ChromePageinteraction, no mocking precedent in this module). -
Concrete AT self-test instructions instead of a generic “check manually”, 2026-09-06: new
manual_recheck_instruction(wcag_criterion, en)(src/output/pdf/helpers.rs), keyed by WCAG criterion, with VoiceOver rotor / NVDA elements list shortcuts for the four criteria for which a layperson can verify a suspicion themselves in a few minutes: 1.3.6/1.3.1 (landmarks/headings via rotor VO+U or Insert+F7), 3.3.2 (form field labels via VO+Cmd+J/NVDA F), 4.1.3 (error message announcement — trigger the message, check whether it is announced automatically without a focus jump). Deliberately no new JSON structure/no kind enum — pure PDF presentation text (analogous torender_manual_only_criteria_note), appended at three already existing places instead of a new appendix detached from the finding: the screen reader findings table (detail_modules/accessibility.rs, keyed onissue.wcag_criterion), the WCAG violation finding card (findings.rs, new “Selbsttest” (self-test) row in the action assessment block, keyed ongroup.wcag_criterion) and the manual check points checklist (single_report.rs, appended to therecommendation/textstring, keyed onfinding.rule).1.3.1deliberately covers both heading and landmark duplicate findings with one shared text (both sub-cases share the samewcag_criterionconstant in the code and are checked in the same VoiceOver rotor/NVDA elements list tool, no artificial separation necessary). Verified live against casoon.de (--debug-typ): the landmark instruction appears correctly at every 1.3.6 screen reader finding. -
Fixed list “Strukturell nur manuell prüfbare Kriterien” (criteria structurally checkable only manually) in the PDF, 2026-09-06: new
render_manual_only_criteria_note(src/output/pdf/single_report.rs), directly after the WCAG coverage section, unconditional (no--annexflag, same report-level gate as the coverage section itself). Five fixed, page-independent rows (2.4.3 focus order, 3.3.1 error identification, 1.4.4/1.4.10 zoom & reflow, 1.1.1 alt text correctness, 1.2.1/1.2.2 video content summary) — deliberately NOT derived from the findings of this page like the EN 301 549 / BIK annex, because precisely the third, “invisible” confidence category from the Insights article would otherwise remain completely invisible in a 0-findings report. Verified live against casoon.de (--debug-typ): renders correctly, without a status dot (no good/warn/bad verdict, a pure scope statement). Discovered while implementing: there is already a separate, similarly named “So testen Sie manuell” (how to test manually) section (src/output/pdf/wcag_coverage.rs) with AT test instructions (keyboard navigation, screen reader, 400% zoom, reduced motion, …) — a different function (instruction “how to test” instead of explanation “why structurally not automatable”), deliberately not merged, but a relevant anchor point for the AT self-test instructions. -
“Process instead of certificate” sentence added to the disclaimer, 2026-09-06: the check showed that the scope caveat itself (“kein vollständiger Konformitätsnachweis” (no complete proof of conformance), “ersetzt keine manuelle Prüfung” (does not replace a manual check)) was already present in the existing
disclaimertext (build_methodology,src/output/builder/single/methodology.rs) and in the cover label (“WCAG-Vorkommen” (WCAG occurrences) instead of blanket “Accessibility-Befunde” (accessibility findings)) — both places left unchanged. What was missing was the process statement emphasized in the article: accessibility as an ongoing task, not a state that can be reached once. One sentence appended to the existingdisclaimer(DE+EN, no new callout component, no change togate_certificate_by_risk/CERTIFICATEthresholds). Deliberately not placed on the cover — that is a fixed, concise dashboard page (renderreportCoverPage), scope/legal texts consistently live in the methodology chapter in this project, not on the cover. -
Three-tier confidence labelling closed as already satisfied, 2026-09-06: the item derived from an Insights article wanted to introduce a new
DetectionConfidenceenum (Certain/HeuristicSuspicion/ManualOnly) plus a registry classification perrule_idand a new PDF badge. Checked during implementation and rejected:NormalizedFindingalready carriesconfidence/false_positive_risk/verification(heuristic per rule viaderive_confidence/derive_false_positive_risk/derive_verification,src/audit/normalized.rs), and every finding card in the PDF shows unconditionally “Erkennungssicherheit”/“Falschpositiv-Risiko” (detection confidence/false-positive risk) in the “Prüfmetadaten” (verification metadata) block (src/output/pdf/findings.rs) — not only for suspected cases. A first attempt to additionally show the existingverificationfield (derived 1:1 fromfalse_positive_risk) symmetrically as another row was discarded again: it would have shown the same information a third time in other words on the same card — real redundancy instead of insight, the opposite of whatreport-lint/report-criticare meant to prevent in this project. The third tier “decidable only contextually” (media alternative, contrast on image background) already runs visibly separated under the PDF section “Manuelle Prüfpunkte und heuristische Hinweise” (manual check points and heuristic notes) (render_assessment_and_execution_notes) with its own “Manuelle Prüfung” (manual check) label. No code change — on close comparison the item was already fulfilled by existing, differently named infrastructure. The item’s text also contained an internal contradiction (point 1 vs. point 4 on classifying media alternative asManualOnlyvs.HeuristicSuspicion), which was clarified with the user (point 1/ManualOnlyis correct). -
build_idgets a-dirtysuffix for an uncommitted working state (2026-09-05):build.rspreviously read thebuild_idonly fromgit rev-parse --short HEAD— as long as work is done uncommitted (as is usual in this project), the embedded SHA stayed identical across several actually different builds and made two live reports with different fix states indistinguishable (confirmed live on three reports from 2026-09-05, all withbuild_id: "be9aed2"despite changes committed since). Newis_dirty()check (git status --porcelain, same no-git fallback as in the SHA lookup — error/no git ⇒ not dirty, no hard failure) appends-dirtyfor an uncommitted state, e.g.44e7480-dirty. Since the dirty status can change on any working tree change, not only on a HEAD/ref change, the existingrerun-if-changed=.git/HEADalone is not enough — an additionalrerun-if-changedon a guaranteed non-existent path forces Cargo to re-run the build script on every build (verified empirically against a scratch project: 3 builds → 3 script runs). Verified live against the deliberately uncommitted working state itself (stringson the built binary shows44e7480-dirty). -
Verified: 1.3.6 finding count on casoon.de is no counting error (2026-09-05): a live report had shown 200 occurrences for WCAG 1.3.6 on a single page, logged as a low-priority observation without suspicion of a concrete bug. Verified against a fresh live run (
--format jsonagainst www.casoon.de): no double-counting bug across desktop/mobile viewport (build_sr_audit_reportruns only once per report, on a single AXTree) and no real discrepancy through theis_real_node_idsanitizing filter (analyze_reading_sequenceinanalyzer.rsremoves empty/synthetic IDs fromaffected_node_idsafter the analysis — message texts such as “18 entries” deliberately count the unfiltered raw set, whileaffected_node_ids.len()can be smaller afterwards, e.g. 8). The Structure chapter ofderive_bik_chapterssumsissue.affected_node_ids.len()over all1.3.6-tagged findings of a page (the identical, already existing aggregation pattern as in every other chapter/criterion) — on casoon.de these are 14 separate “long section without landmark/heading/focus target” locations found bydetect_announcement_deserts, whose filteredaffected_node_idslengths add up to exactly 200. A real, verified structural property of the page (many long content sections without an orientation point in between), not a tool bug — no behavior change needed. Clarifying comment added inbik_guide.rsso that future reviewers do not misread the summation as a counting error again. -
#406 fix: NotTestable/warning findings showed raw English text in the PDF (2026-09-05): a localization violation confirmed live in DE reports (casoon-de, satower-mosterei-de, inros-lackner-de) —
render_assessment_and_execution_notes(src/output/pdf/single_report.rs) called onlyget_explanation(rule_id)forwcag.not_testables(axe_id lookup, e.g."video-caption") and, on a miss, fell back to the raw canonical Englishfinding.fix_suggestioninstead of the safe localized fallback sentence;wcag.warnings(contrast on image/gradient background, 1.4.3) did not attempt aget_explanationlookup at all. Fix: two-stage lookup (rule_idfirst, thenrule/WCAG ID as a fallback — covers both axe-id override entries such as"region"and the new WCAG ID entries) in both loops, with the existing localized fallback sentence as the last step instead offinding.fix_suggestion. Four newexplanations.rsentries for the previously completely missing 1.2.x video family (1.2.1, 1.2.2, 1.2.3, 1.2.8). A real side effect discovered in the process was fixed: the “Videos” chapter ofwcag::bik_guide::derive_bik_chaptersshowedNoFindingsDetectedalthough a real, PDF-visible 1.2.2 finding existed —findings[](NormalizedFinding) is built exclusively fromwcag_results.violations(audit::normalized::normalize), never fromwarnings/not_testables, and video checks almost always resolve to exactly these two kinds.derive_bik_chaptersnow additionally takes&[AccessibilityAssessment](NormalizedReport.accessibility_assessments, an already existing carrier for exactly this data, available in every report path) and additionally feeds the videos chapter from it;normalize_assessmentswas raised from private topub(crate)for this. New regression tests: EN/DE fallback guard insrc/output/pdf/tests.rs(fictitious rule without anexplanations.rsentry) as well as two newbik_guidetests (manual-review-only finding appears in the videos chapter; an unrelated criterion does not leak in). -
New
html_conformmodule: HTML5 specification conformance via thehtml-conformcrate, 2026-08-30: a new, standalone module (src/html_conform/) that useshtml-conform(crates.io, pure Rust, no network/subprocess) to perform browser-style HTML5 tree construction, full W3C RelaxNG schema validation, Schematron co-constraints as well as import map / speculation rules JSON and CSP enforcement checks — considerably deeper than the existing, unchangedhtml5everparse error check inseo::page_health(validate_html_locally). Runs as part of--full(check_html_conform: full_audit, no CLI flag of its own), only on the mobile viewport pass (analogous to SEO/Mobile/DesignQuality), and feeds into the score (not score-neutral likedesign_quality/ai_transparency): its ownModuleScoreEntrywith 10 % weight, funded by a proportional reduction of the five previous weights (Accessibility 40→36, Performance 20→18, SEO 20→18, Security 10→9, Mobile 10→9). Likesecurity, a standalone top-level field onAuditReport(html_conform: Option<HtmlConformAnalysis>, URL/page level instead of viewport experience) and applied tooverall_scoreoutside the viewport blend (ScoreBreakdown.html_conform_score/ _weight_pct, analogous tosecurity_score/security_weight_pct).rule_id/messageremain an opaque canonical-English passthrough (html-conform’s rule set is open, not a small enum, and the messages are third-party running text) — deliberately not the #406 kind-enum pattern, same precedent asbest_practices::console_errors/vulnerable_libs. On a technical setup error or HTML extraction error:checked: false/score: 100(“not measured”, excluded from the weighted overall score) instead of a punitive 0, analogous to Performance’smetrics_available == 0handling. Full JSON/PDF integration (ModuleBlob.html_conform,HtmlConformPresentation, its own PDF renderer with ScoreCard/ MetricStrip/AuditTable). Batch PDF narrative arms (batch_report/sections.rs) and URL matrix column deliberately not part of this change (the score already counts automatically into every batch aggregate) — same precedent as the acceptedcommerce-has-no-PDF gap. -
New
ai_transparencymodule: C2PA image provenance check (EU AI Act Art. 50), 2026-07-31: a new, opt-in (--ai-transparency) and score-neutral module that reads embedded C2PA (“Content Credentials”) manifests on<img>elements of the audited page and — if the manifest declares AI/algorithmic generation (IPTCdigitalSourceTypetrainedAlgorithmicMedia/compositeWithTrainedAlgorithmicMedia/compositeSynthetic/virtualRecording/trainedAlgorithmicData) — produces a manual-review advisory finding. Deliberately report presence only, no attempt to automatically detect a visible label near the image (the same fragility problem as chat widget disclosure detection, hence taken out of scope), and deliberately no EXIF software tag fallback (C2PA is the standard mechanism referenced by the AI Act, EXIF would be a second, unreliable detection logic). Single-URL mode only (PipelineConfig.check_ai_transparency = args.ai_transparency && args.url.is_some(), exactly thecapture_element_evidencepattern): a batch run would do a network fetch + C2PA parse per image, only forbuild_batch_detail()to discard the entire module blob per page anyway (#256). Double opt-in: new Cargo featureai-transparency(c2pa = "0.90.3",default-features = false, features = ["rust_native_crypto"]— no native OpenSSL, no HTTP client features, so that the reader structurally never fetches or phones home by itself), not part ofdefault(precedent:pdffeature) — plus the runtime flag. If the feature is missing at build time but the flag is set,check_ai_transparency_featureinsrc/cli/runners.rsaborts loudly before pipeline start with aConfigError(rebuild hint) instead of silently remaining a no-op. SSRF hardening (the first fetch in this codebase to foreign origins potentially controlled by the audited page — unlikeseo::robots/securitywith their pure same-origin fetch): own DNS resolution + IP range check (private/loopback/link-local/multicast/IPv4-mapped IPv6, explicit range checks instead of newerIpv6Addrmethods that may not be stable everywhere yet) BEFORE every fetch, plusreqwest::ClientBuilder::resolve()pins the connection to exactly the checked IP (prevents a second, unchecked DNS lookup at the actual connect — DNS rebinding TOCTOU). Manifest evaluation uses the typedc2paAPI (Manifest::find_assertion::<Actions>(labels::ACTIONS)→Action::source_type()/.software_agent(),Reader::validation_state()), no blind JSON string walk — more robust against schema drift and running-text false positives. Localization follows the established kind-enum pattern (#406):finding_message_text(rule_id, en)is the only text source. New local enumsAiProvenanceKind/ManifestValidationmirrorc2pa::DigitalSourceType/ValidationState, so thatsrc/ai_transparency/mod.rs(types, JSON/PDF integration) compiles without the Cargo feature — onlyimage_provenance.rs(the actual fetch+parse) is#[cfg(feature = "ai-transparency")]-gated; module registration inAuditCatalog, theModuleDatavariant,ExperienceSection.ai_transparency,ModuleBlob/PDF dispatch remain unconditional (smaller diff than originally planned, no#[cfg]sprinkled across catalog/report/output). Test fixtures for the C2PA parser are synthetically self-generated at test time (c2pa::Builder+EphemeralSigner, signed into a hard-coded 1×1 PNG) instead of vendored from the public C2PA test files (c2pa-org/public-testfiles, CC-BY-SA-4.0) — those contain no samples clearly marked as AI-generated (only Adobe editing conformance tests from 2022), and a synthetic fixture avoids any license/ attribution question. A real side effect discovered in the process:c2paunconditionally enables (hard-wired in its ownCargo.toml, not behind one of its optional features)serde_json’spreserve_orderfeature — through Cargo feature unification this changes the backing map ofserde_json::Value::Objectproject-wide from a sortedBTreeMapto an insertion-orderIndexMapas soon asai-transparencyis built along, regardless of whether the runtime flag is ever set. Affected 4 existing snapshot tests (src/output/sr_audit_json.rs, 3×tests/snapshot_tests.rs) that silently assumed alphabetical key order — fixed with a smallsort_json_keysnormalization function before the respectiveassert_json_snapshot!, not by re-recording snapshots (the order must remain stable independent of the feature set). Fully verified green:cargo test --all-features --lib(1157 passed),cargo clippy --all-features -- -D warningson lib+bins+the two affected test targets (a separate dead-code problem intests/wcag_rule_id_inventory.rs/tests/common/that already existed before this session — unfinished, uncommitted work elsewhere — verified as pre-existing viagit stash, not part of this change). Batch report rollup (analogous totemplate_clusters) deliberately not part of this change — a separate follow-up issue. -
Canonical WCAG rule ID inventory, 2026-07-31 (#552, tracking #559): closes a previously false assumption —
src/taxonomy/rules.rs’sRULES(117 entries, 85Dimension::Accessibility) was wrongly treated as the complete list of all rules. In factRULESis a curated scoring/report classification table, not a runtime registry;PAGE_RULES’srule_id(page_rules.rs) is, per its own doc comment, “used for logging only”, andrun_if_allowed!’s axe_id (engine.rs) is onlyRuleOutcometelemetry. The actual mechanism behindViolation.rule_id: oneRuleMetadataconstant per rule file. A new, browser-free testtests/wcag_rule_id_inventory.rsscanssrc/wcag/rules/*.rs(RuleMetadata literals + the bare*_AXE_IDconstants inaria_roles.rs/widget_rules.rs) andsrc/patterns/*.rs(literal.with_rule_id("...")calls in the Accordion/Modal/TabList/DisclosureMenu pattern detection modules, which get by entirely withoutRuleMetadata) — real, verified number: 116 distinctrule_ids, not 117/85. Reconciled empirically against a full--full --level aaarun (casoon.de); two real, previously unnoticed discrepancies found in the process: (1)NormalizedFinding.rule_idcarries a second, parallel ID namespace (a11y.*, fromtaxonomy::rules::RULES) next to the axe_id namespace inventoried here — both are visible in the JSON for the same rule at the same time, depending on the report location; not a bug, but important for future rule comparisons (which namespace is meant?). (2) Reflow carries two diverging IDs for the same check —RuleOutcome.rule_id = "reflow"(telemetry label inpipeline.rs) vs.Violation.rule_id = "css-overflow-hidden"(REFLOW_RULE.axe_id, the actual finding). Additionally discovered along the way and filed as its own bug issue #560 (deliberately not fixed within #552, independent problem): contrast (1.4.3) and reflow (1.4.10) both run inline inpipeline.rs’srun_rules, without ever checkingRuleFilterConfig.should_run(...)—[rules] disabled/enabled_onlyinauditmysite.toml(documented feature,src/cli/config.rs:75) currently has no effect for these two rules. This inventory is the basis for the planned ground-truth detection corpus (#553–#558), notRULES. -
Detection corpus format + completeness check, 2026-07-31 (#553, #554, tracking #559): builds on the rule inventory (#552). New, browser-free
tests/common/(shared test support, not itself a test binary — standard Rust idiom):rule_inventory.rs(the #552 scan logic, now reusable) anddetection_corpus.rs(ExpectedCase/Expectation/Verdicttypes + loader fortests/fixtures/detection_corpus/<case>.expected.jsonandstructurally_deferred.json— both loaders return an empty list instead of failing if the directory/file does not exist yet, since the corpus deliberately starts empty and is only populated by #556).tests/detection_corpus_format_test.rs(7 tests, parsing/loader against a tempdir, no real fixture needed — avoids unverified ground-truth values before #556).tests/detection_corpus_completeness.rsdiffs the 116 rule IDs against the IDs referenced in the corpusstructurally_deferred.json, reports covered/deferred/gap without failing on low coverage (current starting state: 0/0/116 — expected backlog, not a regression failure), but fails hard on a genuine authoring error (a referencedrule_iddoes not exist in the inventory at all, or a rule is marked both covered andstructurally_deferred).
-
Runemark terminal presentation + batch progress adapter, 2026-07-30 (#529, #530): #529 replaces the previous
colored/comfy-tablerenderer (src/output/cli.rs, deleted) for--format tablewith a thin presentation layer onrunemark(own sister crate, published on crates.io, likerenderreport; version checked live against crates.io: 0.2.0 is the currently published version, not guessed). The newsrc/output/terminal.rsmaps the already existing presentation layer shared by JSON/PDF (ReportViewModel/BatchPresentation— deliberately reused instead of rebuilt, both are not gated behindfeature = "pdf", so available for--format tablein every feature combination) ontorunemark::report::Report(Console,Verdict,Metric,FindingGroup,NextStep,RenderOptions). New--color {auto,always,never}flag (ColorPolicy); terminal width viaconsole::Term::stdout()(already a transitive dependency ofdialoguer, now direct).console_for()forcesNeverwhen the result is written to a file (--output), except with explicit--color always— prevents ANSI bytes in saved report files.comfy-tableremoved completely (0 remaining references);coloredstays, as it is still used in many other CLI places (banner, doctor, sitemap-suggest) — deliberately out of scope for this issue, which only demands “remove only once nothing requires it”. #530 replaces the directindicatif::ProgressBarusage inrun_batch_mode(src/cli/runners.rs) withBatchLifecyclePresenter(new,src/cli/batch_lifecycle.rs), a thin adapter overrunemark::ProgressSink(TerminalProgress/SilentProgress,progressfeature of runemark, which now pulls inindicatiftransitively instead of directly — ownindicatifdependency removed). New--progress {auto,always,never}flag (ProgressPolicy), independent of--quiet(which still suppresses everything).run_concurrent_batch’s signature/concurrency algorithm unchanged — only the callback body inrunners.rsnow callspresenter.advance/notice_errorinstead of touching the progress bar directly. Real bug discovered along the way and fixed: banner/plan/ diagnostic/result/verdict lines insrc/cli/plan.rsandrun_batch_modewere throughoutprintln!(stdout), gated only by--quiet, not by the output format — a batch run with--format jsonwithout--output/--quietmixed plain text into the JSON payload on stdout. Mechanical fix: all these lines are noweprintln!(stderr) or, for the actual batch lifecycle (sitemap/crawl diagnostic one-liners, results line, final verdict), go throughpresenter.notice()/presenter.finish_verdict().print_verdict()(also used by single mode) remains as a standalone function, but is noweprintln!-based — fixes the same class of bug for single-mode JSON runs as well. A second leak, uncovered by the first live verification, found and fixed: the globaltracing_subscriber::fmt()insrc/main.rshad no explicit.with_writer(...)and therefore wrote (tracing-subscriber’s own default) to stdout — atracing::warn!during a batch run (e.g. a page timeout insrc/audit/batch.rs:164) therefore still ended up, ANSI-colored, ahead of the JSON payload on stdout and brokejq. Now.with_writer(std::io::stderr)+.with_ansi(...), the latter coupled to the same--colorpolicy (not to tracing-subscriber’s own, independent auto-detection). Verified live again after this fix (timeout case deliberately reproduced): stdout with--format jsonstays, in a batch run without--quiet, clean JSON thatjqparses validly even on a page timeout;--progress never --quietproduces exactly 0 bytes on stderr;--color alwaysforces ANSI on stderr;report-linton the result JSON reports no findings. -
Contrast pixel-sampling coverage + new
design_qualitymodule, 2026-07-30 (#527, #528): #527 fixes a real gap in WCAG 1.4.3:build_sample_tasks(src/wcag/rules/contrast.rs) previously sampled only if the background WAS uncertain and the CSS ratio already failed — an element with visually plausible CSS colors whose rendered result is reduced by an opacity stack, blend mode or a real<img>behind the text was never sampled and stayed completely invisible (confirmed live on casoon.de:finding_count: 0despite a visibly failing hero area). Fix: the sampling condition now samples for every uncertain background regardless of the CSS ratio (with aMAX_SAMPLE_TASKS = 60cap, largest area first);styles.rs’s ancestor walk now additionally detects “uncertain” foropacity < 1,mix-blend-mode/background-blend-modeand an overlapping<img>/positioned overlay sibling (limited to the first 3 ancestor levels). A real duplicate-finding bug found along the way was fixed as well: the same selector/rule combination could, through different sampling results between the desktop and mobile pass, appear simultaneously as a confirmed violation AND as a NeedsReview warning —merge_wcag_violations(src/audit/pipeline.rs) now suppresses warnings for every selector/rule combination that already exists as a violation. New fixturetests/fixtures/opacity_overlay_contrast.html+test_opacity_overlay_contrast_pixel_sampling. #528 addsdesign_qualityas a new, opt-in (--design-quality, deliberately not yet part of--full) and score-neutral module: heuristic UX/readability hints (overflow clipping on positioned/interactive elements, line length, line spacing, long uppercase text, layout-affecting CSS transitions) from the already open CDP page, a singlepage.evaluate()pass for all text rules. A dedicatedDesignQualityFindingtype (notwcag::types::Violation) guarantees score neutrality by construction — there is never apush_indicatorcall/ModuleScoreEntry, so no code path touchesAccessibilityScorer/the weighted overall score; verified by an integration test (report.accessibility.score/grade/certificatebyte-identical with and without the module). The layout-transition rule does not detect transitions itself anew, but projectsperformance::animationsfindings (filtered to layout-affecting properties) as advisories — avoids a second independent detection path and thereby duplicate findings by construction. Localization follows the established kind-enum pattern (#406):finding_message_text(rule_id, level, en)is the single text source, analysis calls withen=true(JSON canonically English), PDF builder with the run language. NewExperienceSection.design_qualityfield, full JSON/PDF integration (ReportModule,ModuleBlob,ModuleDetailsBlock, dedicated PDF renderer without ScoreCard). Cache signature bumped tofmt=12. -
Report Quality Layer v1.2 — Phase 5: visual verification pipeline, 2026-07-16 (#510, tracking #512): closes the gap previously documented as open (see the previous entry below, “partial”). Instead of a stored pixel-diff baseline (font rendering/anti-aliasing would make that flaky across different machines/CI runners), two new, deterministic same-run checks in
src/output/pdf/tests.rs: (1)test_dual_viewport_performance_renders_two_gauges_not_a_flat_strip— structure regression guard for the historical case named concretely in #510 (the “wrapped dual-viewport cell”): checks in the Typst source (not pixels) that the desktop/mobile performance comparison still renders as two standaloneGaugecomponents in a 2-columnGrid(type: "gauge"≥ 2×, ownlabel: "Desktop"/label: "Mobile") instead of falling back to the former flat “Desktop 85 · Mobile 67” text line — with a newdual_viewport_performance(desktop_score, mobile_score)test helper that constructsreport.performance(mobile) +report.dual_viewport.desktop.performance(desktop), the only way to populate bothPerformancePresentation.desktop/.mobile. (2)test_representative_fixture_pages_are_not_blank_and_stay_within_page_budget— rasterizes an enriched fixture (WCAG findings, dual-viewport gauges, tech-stack tables, throttled network table; thereby covers cover/score cards/tables/findings/methodology/technical metrics from #510’s acceptance criterion) at Technical level and checks non-emptiness AND a page budget (60 pages, detects a reflow outlier without judging subjective layout quality pixel-based — that deliberately remains the job of thereport-criticskill, #509). On a failure, all rasterized pages are copied totarget/pdf-visual-debug/<reason>/(tempdir contents would otherwise be deleted before any manual inspection). Real, previously unnoticed gap found and fixed: thepdf-smokeCI job never installedpoppler-utils— everypdftoppm/pdftotext- gated test (all blank-page/visual tests from Phase 5 as well as the olderpdftotext-based content traceability tests) silently skipped itself in CI since its introduction (find_executable("pdftoppm")→None) instead of running — never visible as red CI, because a skipped test does not fail..github/workflows/ci.yml’spdf-smokejob now installspoppler-utilsviaapt-getand uploadstarget/pdf-visual-debug/on failure as a build artifact (actions/upload-artifact@v4,if: failure()) — closes #510’s acceptance criterion “generated artifacts are traceable in CI”. -
Report Quality Layer v1.2 — Phase 3: feedback corpus, 2026-07-16 (#511, tracking #512): new
tests/regression_corpus/*.json(16 entries, one file per confirmed case) — format{id, category: Invariant|Semantic|Completeness|Explanation|Visualization, problem, evidence, expected, regression, counter_examples[], status: resolved|known_gap}. Covers the starter corpus from issue #511 (score mismatch, critical-as-label-for-critical+high, score without scale, counter without scope, available data without report usage, metric strip wrapping, batch classification from wrong score basis) plus the concrete cases confirmed in this session: the four localization leaks (SEO details, tech-stack severity, TechCategory debug format, renderreport component default labels) and theviolated_rule_countscope false positive from group C — allstatus: resolvedwith a reference to their respective regression test. Four further cases, found by thereport-criticskill dry run against real batch/single reports and not fixed in this session (score_area_for_findingsubstring misclassification,is_generic()link-text substring false positive, impact-vs.-reach contradiction in batchtop_actions,{:?}debug leak + truncating division inmanagement_risks[].rationale) arestatus: known_gap— deliberately documented instead of silently dropped. Newtests/regression_corpus_contract.rsvalidates only the corpus shape itself (required fields, enum values, unique/filename-matchingid, non-emptycounter_examples,resolved⇒ non-nullregression) — it does not re-run the referenced regression tests..gitignore’s blanket*.jsongained a!tests/regression_corpus/*.jsonwhitelist entry (same pattern astests/lint_fixtures/). -
report-lint false-positive fixes from the report-critic eval, 2026-07-16 (#507 follow-up): the eval run found two real false positives in
src/lint/checks.rs, confirmed on a real batch report (reports/casoon-batch-en301549.json— previously 2 findings, now 0): (1)check_grade_and_certificatedid not knowgate_certificate_by_risk(src/audit/normalized.rs:515) — a certificate intentionally downgraded because of Risk=High/Critical/legal_flags/ blocking_issues (“EINGESCHRÄNKT” (restricted)/“NICHT BESTANDEN” (failed)) was wrongly reported as a score mismatch. Now the check accepts any value thatgate_certificate_by_riskcould legitimately produce for the given risk inputs (risk_gate_inputs/acceptable_certificates, new helpers). (2)violated_rule_count(globally distinct rules) vs.severity_counts.total(sum of the per-page-distinct rule rows) are structurally different aggregations at batchsummarylevel that only coincidentally agree for single reports — the check wrongly compared them for exact equality. NewScopeRelationdistinction:Exactfor single reports and each individual page,AtMost(global ≤ sum) only for thesummaryof a batch report. 5 new regression tests insrc/lint/checks.rs. -
Localization follow-up from the report-critic eval, 2026-07-16: the report-critic eval run (see the skill entry below) found real localization leaks — German words without umlaut/ß, therefore undetected by the existing guard test. Fixed:
build_seo_details(src/output/builder/single/module_details.rs) fully localized (meta_tags, identity_facts, page_profile_facts, heading/social/technical/tracking_summary, SchemaExtracted text blocks,signal_rowsrating — ~50 places);Severity::label()(always German) at two further PDF places (detail_modules/indicators.rs,detail_modules/overview.rs— a third supposed occurrence there was actuallyBudgetSeveritywith its own, already language-neutral “Error”/“Warning” labels, not a bug);single_report.rs(“Absprungrate” (bounce rate) was itself mistranslated in the EN branch, “Vorkommen” (occurrences) hardcoded in the format string). Side finding:{:?}debug leak attech.category(TechCategoryhad nolabel()method) — now fixed. New regression testtest_seo_details_english_locale_has_no_known_german_leaks(src/output/pdf/tests.rs) — the first EN-locale check that runsbuild_seo_detailsat all with real SEO data (pdf_fixture_report()alone carries no SEO). Important methodology correction discovered along the way:--debug-typdumps contain the complete renderreport component library (include_str!), not just the content actually rendered — a string occurrence in the dump does not prove that it appears on a page (it can come from a never-instantiated component definition). Led to two renderreport fixes (v0.2.36, see below) and an addition to thereport-criticskill. -
renderreport v0.2.36:
dominant-issue-spotlightandseverity-overview(two components currently unused by auditmysite) had German labels hardcoded in the Typst template (label-text("Empfehlung")(recommendation) etc.) instead of receiving them, like all other components, as a data field from the Rust caller — no live bug (unused), but an inconsistency with the established pattern (Rust always passes already localized strings, templates themselves have no language logic). Both templates now accept optionallabel_*data fields with German defaults (data.at(key, default: "..."));DominantIssueSpotlight/SeverityOverviewin renderreport have newwith_labels(...)builders analogous toCoverPage. Purely additive, no behavior change for existing callers.cover_page.typ’s German fallback value formodules_labeldeliberately left unchanged — auditmysite always sets this field explicitly for both languages, the fallback is unreachable. -
New skill
report-critic(.claude/skills/report-critic/SKILL.md, #509): evidence-bound AI critique of a finished report (JSON +--debug-typtext) for contradictions, missing scope, unsupported conclusions, missing action linkage, text-visible layout artifacts — complements (does not replace)report-lint. Tested via skill-creator eval loop (3 test cases, with/without skill, real 1.1 MB batch report from casoon.de): both configurations consistently found real bugs (substring classification bug in two independent modules,Some(84)debug leak, impact-vs-reach contradiction in an aggregation table, among others) — the skill mainly brings consistent output structure, not additional capability over an already very competent baseline agent. Eval workspace under.claude/skills/report-critic-workspace/(not committed, local). -
Report Quality Layer v1.2 — Phase 5 (partial): visual PDF smoke checks, 2026-07-16 (#510, tracking #512): correction to the original Phase 5 plan — rasterization via
pdftoppmwas not greenfield;src/output/pdf/tests.rsalready had twopdftoppm-gated smoke tests (find_executable("pdftoppm")skips gracefully when unavailable, matching CI’spdf-smokejob which runscargo test --features pdf_test). Extended that existing infra rather than building a newxtask: apng_luma_std_devhelper (grayscale pixel std-dev via the already-presentimagecrate) plusrasterize_pages, backing two new tests —test_single_pdf_technical_pages_are_not_blank_when_pdftoppm_is_availableandtest_batch_pdf_pages_are_not_blank_when_pdftoppm_is_available(batch PDF rasterization had no test at all before this) — flagging a near-solid-color page (missing font/asset → blank render) without exact pixel-diff, which is deliberately avoided: font hinting/anti-aliasing differs across machines/CI runners, so an exact-match baseline would be flaky by construction. Not yet done, open design question: the plan’s “visual diffs for stable layout regions” (e.g. cover skeleton) needs a real decision on baseline storage/regeneration workflow and tolerance before implementing — deferred rather than guessed at. Overflow/cut-content/misalignment detection and the semantic/ visual AI judgment pass both still route to #509 as originally planned. newtests/coverage_matrix.rs— an#[ignore]-gatedexport_coverage_matrixtest (same pattern asoutput::builder::tests::export_all_interpretations) walks everyAuditCatalog::standard()module and counts literal id() occurrences across four surfaces (src/output/pdf/**,docs/OUTPUT_CONTRACT.md, both JSON schemas,tests/**+ fixture dirs), writingreports/coverage_matrix.jsonfor human review. Deliberately not a CI gate — a substring count can false-negative on indirection and false-positive on a common word (confirmed: the tool’s own doc-comment mentioning “commerce” counts as one of commerce’s “fixture references”). Only one hard, always-true assertion ships (every_catalog_module_has_a_unique_nonempty_id— a tripwire on the catalog itself, not on coverage outcomes) rather than “every module has PDF coverage”, which would immediately fail today. Real gap the first run surfaced:commercehas 0 PDF references and 0 references anywhere undertests/outside its own module directory — the module has JSON output (src/output/module.rs,src/output/json.rs) but no PDF rendering and no cross-cutting test coverage, despite CLAUDE.md recording it as “COMPLETE, alle Slices 1-4 gemergt” (complete, all slices 1-4 merged). Not fixed as part of #508 (out of scope — #508 is the detection tool, not a mandate to close every gap it finds); flagged here for a deliberate decision on whether that’s an intentional Studio/JSON-only scope or a real oversight.#509/#510/#511(AI critic, visual PDF pipeline, feedback corpus) are planned but not started. -
Report Quality Layer v1.2 — Phase 2: deterministic report-lint, 2026-07-16 (#507, tracking #512): new
src/lint/—lint(report: &serde_json::Value) -> LintReportruns four registry-driven (#506) checks with zero network/Chrome dependency, each producing aLintFinding{check_id, evidence_path, expected, actual, severity}: (1)summary.score/summary.overall_scorealias consistency plus single-report summary-vs-page cross-check (the “18/100 vs 20/100” corpus shape); (2)grade/certificatere-derivable fromoverall_scorevia the same sharedLETTER_GRADE/CERTIFICATEBandSets the production scorer uses, checked on bothsummaryand every page; (3)severity_counts/occurrence_counts.totalequal the sum of their four severity fields, andviolated_rule_count/violation_countmatch the corresponding scoped total (the “Zähler ohne Scope” (counter without scope) corpus shape); (4) the report’s ownmetric_contextblock matches whatREGISTRYcurrently generates (catches a stale/cached or hand-edited report). New CLI subcommandauditmysite report-lint <file> [--fail-on low|medium|high|critical](defaulthigh) prints findings and returns a non-zero exit code (viaAuditError::ConfigError, exit 3) when the worst finding meets or exceeds the threshold — verified end-to-end against a hand-built broken report before considering this feature done, not just via unit tests.registry::json_path_candidates(moved from a private test-only helper intests/registry_contract.rstosrc/registry/paths.rssolintand the contract test share one implementation) had a latent bug caught while writing paths.rs’s own dedicated unit tests: splitting on" and "before trimming turned prose like “…score and nested dimension scores” into a second bogus path candidate (“nested”) — fixed by dropping the" and "split entirely (only" / "ever separates two real paths in this codebase’sjson_pathtext;take_whilealone already stops at the first invalid character, which discards trailing “ and …” prose). Added a 5th check: everyREGISTRYentry’sdocs_urlis a well-formed<path>#<anchor>reference (shape only, no filesystem access — a released binary has no guaranteedocs/exists alongside it; the deeper anchor-resolution check stays intests/registry_contract.rs, which only needs to hold in the dev/CI checkout).tests/lint_fixtures/*.json(clean single, 3 broken variants covering score-alias/grade/batch-certificate mismatches) plustests/report_lint_tests.rsspawn the compiled binary end-to-end viaCARGO_BIN_EXE_auditmysiteand assert on exit code + finding check-ids — these fixtures double as the seed for #511’s regression corpus. No new CI job was added: since this test file has no network/Chrome/pdf-feature dependency, it’s already exercised by the existing unscopedcargo testin thecheck/check-all-featuresjobs. Added a 6th, narrowly-scoped PDF-traceability check instead of the originally-sketched “does any number in the PDF appear anywhere in the JSON” scan (rejected: real false-positive risk from dates/page counts/unrelated percentages). New optional--typst-source <path>onreport-lint(the--debug-typTypst source for the same report); when given,check_pdf_certificate_traceabilitycomputes the certificate token the JSON’soverall_scoreimplies via the same sharedCERTIFICATEBandSetthe PDF itself uses, and checks that exact token is present in the Typst text — presence-only (not “no other certificate word may appear”, since a legend explaining the band system may legitimately mention other tokens),Severity::Low(advisory, never breaches the default--fail-on highon its own).lint()’s signature grew a secondOption<&str>parameter for the Typst text. Two.typfixtures added undertests/lint_fixtures/; a first draft of the “broken” fixture accidentally spelled the certificate word out in its own comment (“SEHR GUT” (very good) contains “GUT” (good) as a substring) and silently passed — caught only because the CLI integration test asserted on the actual finding appearing, not just the exit code, which is why report-lint’s own test fixtures need their negative-case text double-checked for accidental substring self-matches.#508–#511(coverage matrix, visual PDF pipeline, AI critic, feedback corpus) are planned but not started. -
Report Quality Layer v1.2 — Phase 1: canonical metric registry, 2026-07-16 (#506, tracking #512): new
src/registry/(MetricSpec/BandSet/MetricKind/Direction/Scope/Aggregation,REGISTRYconst table) gives every specialized number one machine-readable definition instead of scattered renderer/doc logic. Seeded 1:1 fromsrc/output/json.rs’s former hand-writtenmetric_context()vec —metric_context()now derivesscore_definitions/count_definitionsfromREGISTRYinstead of the other way around, with the samefield/unit/meaningtext (zero JSON output change, verified against snapshot/schema/consistency test suites).docs/OUTPUT_CONTRACT.mdgained a## Metricssection with one<a id>anchor per registry entry;tests/registry_contract.rs(mirrorstests/parity_contract.rs’s “contract file + test” shape) checks unique ids,docs_urlanchors resolve,reviewed_atparses as a date, andjson_pathresolves againstdocs/json-report.schema.json/docs/json-batch-report.schema.json. Phase 1 complete (all 7 migration steps): every one of the ~19 independent score→label/grade definitions found across taxonomy, PDF renderers, and module-specific label functions now references a namedBandSetinsrc/registry/bands.rsinstead of re-coding thresholds —FIVE_BAND(90/75/60/40 words),FIVE_BAND_LETTERS(same cutoffs, A–F),LETTER_GRADE(90/80/70/60, A–F),SECURITY_GRADE(90/80/70/60/50, A+–F),BATCH_GRADE(95/90/80/70/60, A+–F),CERTIFICATE(90/75/60/40, SEHR GUT…UNGENÜGEND (very good … insufficient) — was independently re-implemented in bothaudit::scoring::calculate_certificateand the PDF’scover::batch_certificate_labelbefore this migration),COVER_PHRASE/SCORE_RANGE(90/75/60/40, sentence variants),MEDAL(90/80/60, terminal-table GOLD/SILVER/BRONZE/FAILED),BAR_COLOR_BAND(90/80/70/50, terminal color only), andSEO_BAND(90/70/55/35 — SEO’s own family, deliberately kept distinct, not collapsed intoFIVE_BAND). No threshold values changed;output::cli::colorize_gradewas deliberately left untouched (keys off an already-resolved grade letter, no threshold to register). Found and flagged but not fixed (out of scope for #506):performance::scoring::PerformanceGrade::emoji()/.label()/Displayare dead code — never called anywhere reachable insrc/(JSON serializes the enum variant name directly; the PDF renders scores via the now-migratedscore_band_label/score_range_labelinstead), so the emoji never actually reaches a report despite existing in source.#507–#511(report-lint, coverage matrix, visual PDF pipeline, AI critic, feedback corpus) are planned but not started. -
BFSG / EN 301 549 mapping annex, 2026-07-15 (#en301549):
src/wcag/en301549.rs— canonical 50-entry WCAG 2.1 A/AA ↔ EN 301 549 (chapter 9, “Web”) clause table,derive_annex/derive_batch_rollupas pure projections overNormalizedFinding(nothing new stored onNormalizedReport, no cache-signature change). Four-way scope split per clause: violations found / no violations in automated scope / manual review required / (chapter-level, not per-clause) out of audit scope.screen_reader/bfsg.rsreduced to a thin wrapper; the legally-unverified"§12 Abs. 1"citation stays local there, deliberately not propagated. JSONen301549_annexalways emitted (PageDetail, single + batch) plus a batchUnifiedSummary.en301549_rollup; the PDF appendix only renders behind the new opt-in--annex en301549flag (“Zusatz” (addendum), not default-on). Disclaimer text (DE/EN) is a scope-of-testing disclosure only — no statutory citation, no conformity claim — reusing this project’s existing “manual audit with assistive technologies (screen reader, keyboard navigation)” wording rather than inventing new phrasing. -
Plain-language content in the existing PDF, 2026-07-15: no separate report variant — the Chapter 02 finding card gained a plain-language lead-in (
customer_description+user_impact) between the header and the QA-meta block (previously not rendered there at all, not just misordered).finding_group_from_normalized’s no-RuleExplanationfallback no longer leaks raw canonical-Englishf.descriptioninto German reports. Part-1 divider reframed as dual-audience (“Inhaber, Entscheider und Entwickler” (owners, decision makers and developers)). -
Journey × Commerce deepening, 2026-07-14/15: form-error journey now groups required fields into up to 3 per-form candidates (was one page-wide candidate) and a
PURCHASE_FINAL_HINTSdeny-list guarantees a purchase-final button (e.g. “Jetzt kaufen” (Buy now)) is never a synthetic-click target. New commerce-aware journeys on a detected shop’s product-detail page under--interactive full: add-to-cart feedback (SC 4.1.3) and quantity-stepper operability (SC 2.1.1/4.1.2).CommercePageKind::Cart/::Checkoutremoved entirely (breaking JSON change) — this tool has no cross-page session/cart state, so a cart/checkout URL reached cold is almost always empty or redirects before rendering anything a page-kind-gated heuristic could act on; confirmed no reference in the siblingauditmysite_studiorepo before landing. -
WCAG coverage + correctness sweep, 2026-07-14: new rules 1.3.2 Meaningful Sequence, 3.3.7 Redundant Entry, 2.4.11/2.4.12 Focus Not Obscured, 2.2.2 Pause/Stop/Hide (automated WCAG-AA count now 36/50, up from 33). Fixed three known-defective rules:
focus_visible_css.rs(never fired in production — missing evidence selector demoted every finding to a warning),focus_visible.rs(dead AX-treetabindexread, removed),non_text_contrast.rs(mistagged/ dead, replaced by a real CDP-basednon_text_contrast_css.rs). Closed remaining #406 localization gaps (Dark Mode, keyboard journey,expected_impact/complexity_reason) and several report-wording/readability fixes across Chapters 01–03 of the single report. -
Evidence-Grade Findings (single report only) + Template-Root-Cause-Dedup (batch only), 2026-07-14: Single-report finding cards now embed a cropped element screenshot (
src/accessibility/element_capture.rs, gated on single-URL mode viaPipelineConfig.capture_element_evidence, capped at 12 crops/report, contrast findings excluded by construction), a ≤3-level DOM path, and computed contrast-ratio evidence (ViolationEvidence::computed,OccurrenceDetail.evidence: Vec<ViolationEvidence>— new additive JSON field,docs/json-report.schema.jsonupdated). Batch reports gain verified template-level clustering (src/audit/template_dedup.rs): findings sharing an identical(rule_id, normalized selector)fingerprint across ≥3 pages / ≥60% coverage become aTemplateCluster(confirmedwhen the HTML-snippet shape also matches,likelyotherwise — decision-action wording only upgrades forconfirmed), surfaced additively inUnifiedSummary.template_clustersand the batch PDF. Both features are additive/JSON-safe (screenshot bytes are#[serde(skip)], never touch cachedreport.json). Fixed two pre-existing binary-test regressions surfaced by running the fullcargo test --features pdf/--no-default-featuressuites (not covered bycargo test --lib): a stalenon_text_contrast→non_text_contrast_cssrename reference and a staleKNOWN_EXCEPTIONSentry intests/wcag_coverage.rs. -
Product-grade PDF redesign (single report, PR feat/report-product-redesign): cover as a composed dashboard (dominant overall score + grade-band phrase + module gauge strip); management view with severity counters, spider radar “Qualitätsprofil” (quality profile) and strengths/optimization cards; every module its own level-2 chapter with magazine opener + key-statement line (#15); AI Visibility + Content Visibility + Source Quality merged into one chapter “KI & Vertrauen” (AI & Trust); action plan as action cards grouped by problem level (systemic/local, without time/effort); cause distribution as a bar chart; ToC at top level (depth 2); modern borderless tables; consistent 4-color law in
src/output/pdf/design.rs(score_color/severity_color, thresholds 75/40); no “/100”, no A–F grade (band label viascore_band_label), no emoji. renderreport 0.2.26 (composedcover-page, real spider radar, borderlessaudit-table, de-emojified callouts, sticky headings/component titles against orphaned headings). JSON fix: cache-hit JSON now emits the fulldetail.modulesblob (previously empty, since normalized-only path). -
Semantic-Eval removed completely: module
src/semantic_eval/(Fastembed + Mistral), CLI flag--no-semantic-eval/--semantic-eval,[semantic_eval]TOML section,fastembeddependency +semantic-evalCargo feature, typeAdvisoryFindingand the fieldadvisory_findings(fromNormalizedReport/AuditReport/JSON as well as the PDF advisory sections).audit_signatureno longer contains asemanticsegment (cache invalidated once). -
Scoring correctness + report readability (PR fix/perf-relative-weight-cap): relative weight-penalty cap (≤70 % of the vitals base, protects low-base pages from 0); renderreport 0.2.23 (progress-arc gauges + fixed label box, no cover overlap); customer passages without jargon duplicates/meta prefixes; cover label “N Accessibility-Befunde” (N accessibility findings; scope explicit, WCAG-only); vuln detection Lodash↔Underscore via
_.runInContext; #406 leaks (search_experience components + warnings re-derived); pluralization “1 Schema”;compact_html(data URIs → “data:…”, line heights); empty “Befunde nach Ursache” (findings by cause) divider page filled; short indicator modules (Best Practices/Tech Stack) packed via divider instead of each getting its own almost-empty page. -
Cache correctness (PR #458, #404/#405): the full
AuditReportis cached (report.json, screenshots stripped), cache hits render faithfully instead of via the lossyto_audit_report;screen_reader_audit(#[serde(skip)]) is rebuilt from the AXTree viahydrate_cached_report.NormalizedReportfields withskip_serializing_ifnow have#[serde(default)](round-trip blocker fixed — the cache never loaded). Verdict always fromcached.audit.persist_artifactsruns after the canonical perf adoption (audit_pagereturnsSnapshotData).audit_signaturecontainslang; corrupt cache → miss + warning. -
Report quality (PR #459, #446): Security/SEO/Page-Health emit a “keine Auffälligkeiten” (no findings) confirmation line when the findings collection is empty (
pdf-section-clean) — “checked & clean” vs. “not checked” can be told apart. -
Scoring corrections (PR #460, #455/#456/#457): DOM size as a degressive penalty (max 35) instead of a hard 59 cap; throttled profiles get the headline
content_weight(no Slow3G>Fast3G inversion); risk-breadth path decoupled from critical occurrences (legal_flags >= 3),driven_by/summary reflect the real trigger (breadth vs. volume). -
Audit quality (PR #454): localization fixes (security CSP, WCAG findings, SEO heading canonically English); scoring desaturation (DOM cap >6000/>10000, accessibility root curve from penalty 70, mobile soft floor, Risk=Critical only with systemic exposure #250); Core Web Vitals measurement correctness (CLS session window, LCP+TBT limited to the load window,
MeasurementContext::LabThrottledMobilemarks throttled headline vitals in the JSON). -
Localization architecture (#406): JSON canonically English, only the PDF is multilingual. Analysis bakes in English, PDF presentation derives (kind-enum pattern). See the section “Lokalisierungs-Architektur” (localization architecture). Plus audit finding fixes (#442–#452, #411, #447, #449) — PR #453.
-
Catalog refactoring (phase A+B):
trait AuditModule+AuditCatalogregistry with topo sort; all 12 modules migrated; table-driven WCAG page-rule catalog;audit/interpretation.rs(pre-computed DE/EN texts);audit/summary.rs(aggregation logic); builder is a pure mapper (#330–#338) -
Branch:
main -
Cache:
--reuse-cachevalidatesCacheMeta.audit_signature(tool version + WCAG level + active modules + consent) against the current configuration; on mismatch cache miss + warning, a legacy cache without signature is never reused (#260) -
Crawler: parser-based link extraction via html5ever incl.
<base href>(#263) -
Batch JSON: optional
sampleblock (source, total_discovered, audited, sample_limit, selection, is_sample) + PDF scope-of-audit line (#261) -
Performance:
VitalMetric.measurement(lab_headless/estimated_lab); INP/TTI/Speed Index marked as lab estimate, lab disclaimer in the report (#262) -
Contrast: image/gradient backgrounds are demoted to manual-review warnings instead of confirmed violations (#264, pixel sampling open)
-
Accessibility Journey Layer (
--interactive off|basic|full): tab walk, skip link, disclosure, modal, TabList, menu, form-error announcement, SPA navigation, link text/heading/landmark inventory (#297–#301). Results ininteractive_findings+accessibility_journeyin the JSON. -
Snapshot Export (
--export-snapshot <path>): AXTree + journey traces as YAML for CI regression (#301). -
Link-text stopwords in i18n FTL (
locales/de|en/report.ftl, keylinktext-generic-stopwords) — extensible without code changes (#299). -
95+ WCAG rules implemented (Level A, AA, full AAA coverage)
-
2 output formats (json, pdf); table for quick terminal checks
-
Batch processing with configurable concurrency
-
Pattern Detection: MainNavigation, SkipLink, Accordion, Dialog, DisclosureMenu, TabList, Form
-
Modules: Performance, SEO, Security, Mobile, Dark Mode, Design Quality (opt-in, score-neutral), UX, Journey, AI Visibility, Content Visibility, Source Quality, Tech Stack, Best Practices, Commerce, Accessibility Journey Layer
-
Consent:
--dismiss-consentflag; CMP cookie injection + banner click;consent_banneraudit_flag in the JSON -
audit_flagskinds:conflicting_signal(3.1.1 vs. SEO lang),viewport_gap(desktop/mobile ≥20 points),consent_banner,consent_wall_artifact,bypass_blocks_untested(skip link present but functionally broken — static check has PASS, journey FAIL) -
JSON: Unified Report Envelope v2.0 — uniform schema for single + batch (
schema_version,report_type,summary,pages[],pages[i].detail). Breaking change vs. v0.17. -
Scoring: depth saturation (two-phase), diversity factor, soft floor + logarithmic compression for extreme penalties (≥85 points), WCAG principle coverage;
score_breakdown(only withscore_calculation_method = "viewport_weighted", otherwise absent) -
Findings:
categoryfield onNormalizedFinding("wcag"/"seo");severity_countscounts findings (one row per rule/severity, WCAG category only — remains risk/legal relevant). In the JSON report,occurrence_counts,violation_countandviolated_rule_countcover all categories (WCAG + SEO) — consistent withfindings[]anddetail.fix_guidance(#254/#255).top_recurring_rulesremains WCAG-only. Note:NormalizedReport.occurrence_countsis still WCAG-only (feedsSiteState/risk), the JSON PageEntry computes the all-category variant separately.risk.severity= most severe violation across all findings (no separateseverity_maxfield) -
Risk level: score-based fallback (score ≤ 20 → at least Medium);
legal_flags > 0orblocking_issues ≥ 1raise the level to at least Medium.legal_flagscounts distinct WCAG Level A rules with High/Critical severity (not occurrences). -
History:
schema_version: "1.0",report_type: "history"in history JSON files -
PDF: throttled performance table, indicator labeling consistent, empty page after ToC fixed; accessibility journey section in single and batch reports
-
Performance score: Lighthouse v10/v11 weighting (FCP 10 %, LCP 25 %, TBT 30 %, CLS 25 %), log-normal score curves with p10/p50 calibration; CLS > 0.5 hard-capped to 0
-
tool_versionas top-level field in the JSON report (alongsideschema_version/report_type) -
Sitemap summary contains
violated_rule_count(deduplicated across all pages) andtop_recurring_rules(max. 10 most frequent WCAG violations) -
Pass criterion (
passed_url_count): accessibility_score ≥ 80, no critical findings and no WCAG Level A High/Critical findings (i.e.legal_flags == 0) -
detail.fix_guidanceis always present in the JSON (empty array with 0 findings) — also in batch/sitemap reports; there each page carries a compactdetail(onlyfix_guidance, without module blob), see #256