Accessibility Conformance Report

Report information

Based on VPAT® Version 2.5Rev. "Voluntary Product Accessibility Template" and "VPAT" are registered service marks of the Information Technology Industry Council (ITI).

Name of Product/Version

ravenwatchstudios.com, the public website of Raven Watch Studios. The site deploys continuously from a version-controlled source repository; this report describes the build deployed to production on July 30, 2026 (source revision 89dddfe, the accessibility remediation release).

Report Date

July 30, 2026

Product Description

A static content website built with Astro 7.1.3, with page content managed in Sanity CMS and hosting on Cloudflare Pages. At the assessment date the site comprised the following pages: home, about, games index, the Iron Latitudes game pages (overview, roadmap, media), the news index and individual news posts, press kit, contact, and a custom 404 page. The only interactive functionality is the primary navigation (including one disclosure submenu and a mobile disclosure menu), a category filter on the news index, a contact form, and a newsletter subscribe form. The contact form embeds one third-party component, Cloudflare Turnstile (see Third-Party Components below). As of the September 2026 revision the game media pages and news posts can also carry a prerecorded video clip hosted on YouTube, embedded so that nothing is requested from the video host until a visitor activates the player (see Third-Party Components). The site contains no audio-only content and no live audio or video.

Contact Information

info@ravenwatchstudios.com

Notes

• This is a self-assessment prepared by Raven Watch Studios. It has not been certified by an independent third party.
• This report covers WCAG 2.2 Levels A and AA only. Level AAA conformance is not claimed and Table 3 is not included. Two Level AAA criteria that were checked incidentally during the assessment (2.3.3 Animation from Interactions and 2.4.12 Focus Not Obscured, Enhanced) passed, but no Level AAA claim is made.
• Two manual verification items on the third-party Cloudflare Turnstile component remain open and are marked in the relevant table rows below. The affected rows state exactly what has and has not been verified.
• September 2026 revision. Video was added to the site after the assessment date. Six rows were rewritten to describe it: 1.2.1, 1.2.2, 1.2.3, 1.4.2 and 2.2.2 at Level A, and 1.2.5 at Level AA. Nothing else in this report changed.
• The site deploys continuously. Changes made after the assessed revision are outside the scope of this report and are covered by the studio's stated practice of re-assessment after significant changes.

Evaluation methods used

1. Automated scanning (local, before and after remediation). axe-core 4.12.1, driven through @axe-core/playwright 4.12.1 on Playwright 1.62.1 (Chromium), at a 1280x900 viewport, across all 12 routes of the site, with all WCAG 2.0, 2.1, and 2.2 Level A and AA rule tags (wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa) plus the Deque best-practice rule set. Before remediation the production baseline showed 53 failing nodes on WCAG-tagged rules (plus 73 on best-practice rules). After remediation: 0 failing nodes on all rules, all routes.
2. Automated re-verification against production (post-deploy, same day). After the remediated build was deployed on July 30, 2026, axe-core 4.12.1 was injected into headless Chromium and re-run against https://ravenwatchstudios.com across 15 routes (every page live at that time, including all published news posts and a 404 probe) at two viewports, 1440x900 desktop and 375x812 mobile, with all WCAG 2.0/2.1/2.2 A and AA rule tags. Result: 0 violations. The cross-origin Turnstile iframe cannot be script-injected and was excluded from automated scanning; that component is assessed separately (see Third-Party Components).
3. Manual assessment, modelled on the Accessibility Insights for Web assessment, covering the criteria automation cannot decide: scripted sequential-focus (Tab) walks across 10 routes, with 45-stop walks on 5 routes; per-stop computed-style assertions of focus indicator presence (outline style, outline width, box shadow); heading hierarchy and landmark checks on all 12 routes; reflow at a 320px viewport with overflow masking neutralised so hidden overflow cannot conceal a failure; the full 1.4.12 text-spacing override set applied at 320px; 200% text resize on 4 routes; 640x360 landscape orientation; emulated prefers-reduced-motion; programmatic target-size measurement of every target against the 24x24 rule and both of its exceptions; and focus-obscured overlap measurement against the sticky header at 1280x700, per focus stop. All 8 WCAG 2.2 additions at Levels A, AA, and AAA present in the assessment model were checked explicitly.
4. Pixel-measured contrast for the 52 text nodes axe-core returned as "needs review" (text over gradients, over the hero backdrop, and inside cards with image headers). Method: hide the element's own ink, screenshot its exact bounding box, compute the relative luminance of every pixel of the true backdrop, take the worst (minimum contrast) pixel, and compare it against the element's computed foreground colour with the correct large-text threshold applied. Result: 0 failures in 52 checks, measured range 4.77:1 to 17.59:1.
5. Live browser session (July 30, 2026), in desktop Chrome on the production contact page, closing the assessment's two open third-party items: a physical keyboard walk into and through the Cloudflare Turnstile widget with the focused element sampled at every stop and each stop screenshotted (3 internal stops, visible focus indicator on each, clean exit, no trap), and inspection of the widget region through the browser's host-visible accessibility view (no named frame node exposed; the internals sit in a closed shadow root). The widget completed non-interactively in this session; no interactive challenge could be induced. Results are recorded in Table 1 rows 2.1.1 and 4.1.2, Table 2 row 2.4.7, and Third-Party Components.
6. Final verification of the expanded site (July 30, 2026). The site grew from 12 to 17 routes on the assessment date (an accessibility statement, this conformance report, and redesigned game-area pages). The full automated scan was re-run across all 17 routes at two viewports (1440x900 and 375x812) with the same WCAG 2.0/2.1/2.2 Level A and AA rule tags: 0 violations. The raw JSON output is archived in the site repository (a11y-results/) as the audit trail behind this report, and the scan is preserved as a repeatable command that fails the check on any violation.

Applicable standards and guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Terms

Supports

The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.

Partially Supports

Some functionality of the product does not meet the criterion.

Does Not Support

The majority of product functionality does not meet the criterion.

Not Applicable

The criterion is not relevant to the product.

Not Evaluated

The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

WCAG 2.2 Report

Table 1: Success Criteria, Level A

All results describe the remediated build deployed July 30, 2026, verified locally and re-verified against production the same day. The table scrolls sideways on narrow screens.

Table 2: Success Criteria, Level AA

All results describe the remediated build deployed July 30, 2026, verified locally and re-verified against production the same day. The table scrolls sideways on narrow screens.

Third-Party Components: Cloudflare Turnstile and YouTube

Verified by this assessment (from the host page):

• Keyboard focus enters the widget, traverses 3 stops, and exits cleanly to the next control. There is no keyboard trap (2.1.2).
• The widget no longer breaks reflow at narrow widths: below 420px the compact build is requested, and the document lays out at 320px with no horizontal overflow (1.4.10).
• In default managed mode, no cognitive function test is presented, and a conforming alternative (a visible, programmatically associated email address) is provided against the case where the vendor escalates to an interactive challenge (3.3.8).
• All labels, errors, hints, and status messaging surrounding the widget are site-authored and conform as documented in Tables 1 and 2.

Checked in a live Chrome session (July 30, 2026), completing the assessment's two open items:

1. The accessible name of the challenge frame: could not be confirmed. The widget renders inside a closed shadow root, and the host-visible accessibility view exposed no named frame node for the widget region. Table 1, row 4.1.2 is graded Partially Supports on that conservative basis.
2. The escalated interactive challenge: did not present and could not be forced from the client side (the widget completed non-interactively, with no cognitive or interactive test). Its keyboard operability remains vendor-owned and unverified; the documented email alternative covers that case regardless. Recorded in Table 1, row 2.1.1.
3. Observed in the same session, improving on the headless result: a clearly visible focus indicator on each of the widget's 3 internal stops, screenshot-verified. Recorded in Table 2, row 2.4.7, which conservatively remains Partially Supports because that styling is vendor-supplied.

Not verifiable from the host page, and owned by Cloudflare:

• The naming, rendering, contrast, and semantics of everything inside the widget, and the focus styling of its internal stops across browsers.

YouTube, the embedded video player (added September 2026):

• Nothing is requested from YouTube or from any other Google host until the visitor activates a clip. Until then the page shows a still frame served from the studio's own content delivery network, inside a button labelled with the clip's title. The player is created only on activation, and it is loaded from the privacy-enhanced host youtube-nocookie.com.
• The player is the vendor's, so its internal controls, its contrast and its keyboard behaviour are Google's surface and Google's claim to make, in the same way the Turnstile internals are Cloudflare's. What the studio controls and has verified from the host page: the activation control is a real button, reachable and operable by keyboard, carrying the clip's title in its accessible name; the frame is given the clip's title as its own accessible name; focus moves into the player on activation; and captions are requested on by default.
• Nothing about a clip depends on the player working. The summary, the description of what happens on screen, the caption status and the transcript download are static markup below the frame, present before activation and after it, and present with scripting disabled. Where scripting is off, the still becomes a plain link to the clip's page on YouTube.

Scope of This Report and Honest Limits

• Self-assessment. This report was produced by Raven Watch Studios about its own website. It has not been audited or certified by an independent third party.
• Assessment date. All testing was performed on July 30, 2026. The initial audit and remediation ran against the build deployed that day (source revision 89dddfe), with a same-day post-deploy re-scan of production showing zero violations. The site was then expanded and redesigned the same day, and the full scan was re-run across all 17 routes of the expanded build (zero violations, archived), with the two open third-party items closed in a live browser session against the production contact page.
• What "zero automated violations" does and does not claim. Automated rules detect a minority of possible WCAG failures. A clean axe-core result means no failure was found by any of the roughly 100 applicable automated rules on any scanned page; it does not by itself demonstrate conformance. The conformance claims in this report rest on the automated results combined with the manual assessment described under Evaluation Methods, which covered keyboard operation, focus behaviour, structure and semantics, reflow, spacing, motion, target sizes, and pixel-measured contrast where automation could not decide.
• Not yet performed. Assistive-technology sessions with real screen readers (NVDA, JAWS, VoiceOver) have not been conducted. The assessment verified the programmatic properties those tools consume (names, roles, states, landmarks, live regions), but observed screen reader behaviour is a known gap that the studio intends to close.
• Conformance formulation. On the basis above, the site conforms to WCAG 2.2 Level AA based on self-assessment, with the exceptions documented in this report: the Cloudflare Turnstile items under Third-Party Components, and 1.2.5 Audio Description (Prerecorded), where a descriptive text alternative is provided for every clip and a separately narrated audio description track is not.

Download the report PDF, 132 KBBack to Accessibility