Accessibility Statement
Effective: 2026-09-24 Last updated: 2026-10-15 Version: 1.2 (Section 3 corrected to the full 55 WCAG 2.2 A and AA criteria)
Score Network, Inc. is committed to making Score usable by everyone, including people who use assistive technology such as a screen reader, switch device, or voice control, and people who navigate by keyboard alone, need larger text or higher contrast, or are sensitive to motion.
1. Our conformance target
We build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We treat this as the floor for every customer-visible surface we release: the marketing website, the customer portal, email, the assessment flow (including inside Slack), and every other product surface that reaches a customer, employee, or candidate.
We picked WCAG 2.2 AA because it is the level every regime we are subject to converges on: it satisfies the evidentiary basis for a Section 508 VPAT (which maps to WCAG 2.0 AA), the EN 301 549 standard behind the EU's European Accessibility Act (which tracks WCAG 2.1 AA moving to 2.2), and the standard the UK courts and the Equality and Human Rights Commission treat as the practical benchmark for the Equality Act 2010 reasonable-adjustments duty. Building to the highest, most recent AA level satisfies the floor everywhere we operate.
Of 55 WCAG 2.2 A and AA criteria in scope, we fully support 31 (56%), partially support 4 more (7%) under active remediation, with 2 failing (4%), 2 not yet assessed (4%), and 16 not applicable to the marketing site (29%). Transparency about where we stand and the specific work underway matters more than silence.
2. What this statement covers
This statement covers the public marketing website at score-corp.com. Score's other customer-facing surfaces (the customer portal, the assessment flow, email, and the Slack integration) are held to the same WCAG 2.2 AA target but are not yet covered by a published statement of their own; that is on our build plan, not a decision to exclude them.
3. Conformance status
This conformance status is based on a complete criterion-by-criterion audit of all 55 WCAG 2.2 Level A and Level AA success criteria (4.1.1 Parsing is obsolete in WCAG 2.2 and is not scored; Level AAA criteria are outside our target and are not scored). The audit was independently verified by @qa against live pages on 2026-09-24; the five Level AA criteria added in version 1.2 (1.2.4, 1.2.5, 1.3.4, 1.3.5, 3.1.2) were checked against the live site on 2026-10-15 and independently verified by @qa the same day. We use standard VPAT vocabulary: Supports (verified), Partially Supports (partially verified; defect under active remediation), Does Not Support (material failure), Not Applicable (genuinely outside scope for this site), Not Assessed (claimed but unverified).
Level A Conformance
| # | Criterion | Conformance | Notes |
|---|---|---|---|
| 1.1.1 | Non-text Content | Supports | All images carry descriptive alt text or aria-hidden; decorative imagery marked. Logo is markup, not rasterised. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | Not Applicable | No prerecorded audio or video content on marketing site. |
| 1.2.2 | Captions (Prerecorded) | Not Applicable | No prerecorded video with audio. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded multimedia content. |
| 1.3.1 | Info and Relationships | Partially Supports | Semantic HTML and heading hierarchy are correct site-wide. Contact form fields (Name, Email, Message) lack programmatic id/for label association; screen-reader users rely on placeholder fallback. Subject field has correct association. Defect under active remediation. |
| 1.3.2 | Meaningful Sequence | Supports | Heading order is semantic and consistent (h1 → h2 → h3, no skips) across all 14 pages; content reads correctly to assistive technology. |
| 1.3.3 | Sensory Characteristics | Supports | Instructions never rely on shape, colour, size or visual location alone; no "click the blue button" phrasing. |
| 1.4.1 | Use of Color | Supports | Colour is not the only means of conveying information; nav links carry underline or weight change in addition to colour. |
| 1.4.2 | Audio Control | Not Applicable | No auto-playing audio. |
| 2.1.1 | Keyboard | Supports | All interactive elements are operable via keyboard (Tab, Enter, Space); no keyboard traps. Tested on /, /contact, /pricing. |
| 2.1.2 | No Keyboard Trap | Supports | Focus can be moved away from any component; Tab/Shift-Tab navigation escape all interactive elements cleanly. |
| 2.1.4 | Character Key Shortcuts | Not Applicable | No single-character keyboard shortcuts implemented. |
| 2.2.1 | Timing Adjustable | Not Applicable | No time-limited content requiring user action. Site includes one animated GIF (homepage, assessment-rate.gif) which auto-plays once and stops within 5 seconds, exempting it from timing restrictions. |
| 2.2.2 | Pause, Stop, Hide | Not Applicable | One animated GIF on homepage (assessment-rate.gif, 122 frames, 4.88s total duration, single play) complies because it plays once and stops in under 5 seconds. No moving, blinking or scrolling content elsewhere on site. |
| 2.3.1 | Three Flashes or Below Threshold | Supports | No flashing, strobing or seizure-inducing content. Animated GIF on homepage contains smooth transitions with no flashing pattern. |
| 2.4.1 | Bypass Blocks | Not Assessed | No visible "skip to main content" link found in keyboard navigation sequence or DOM. Short, non-repeated navigation structure does not trigger the criterion's "repeated block" requirement, but a reproducible bypass mechanism was not found. Recommend further review. |
| 2.4.2 | Page Titled | Supports | All 14 tested pages carry distinct, descriptive <title> elements visible in browser tab. |
| 2.4.3 | Focus Order | Partially Supports | Navigation order follows DOM and visual sequence correctly. However, on pages taller than one viewport (/, /pricing, /assessments, /levels, /how-it-works), tabbing past certain elements moves focus to content far below the visible area without scrolling it into view. Keyboard-only users lose visual track of focus. Defect under active remediation. |
| 2.4.4 | Link Purpose (In Context) | Supports | All link text is descriptive and conveys purpose without surrounding context; no generic "click here" or "read more" phrasing anywhere on site. |
| 2.5.1 | Pointer Gestures | Supports | No functionality requires multi-point gestures or path-based gestures; all interactions use standard click/tap. |
| 2.5.2 | Pointer Cancellation | Supports | No action triggered on pointer down; all interactions triggered on pointer up (standard click). Mouse and touchpad use not required. |
| 2.5.3 | Label in Name | Supports | Visible text labels on buttons and links match their accessible names everywhere verified. |
| 2.5.4 | Motion Actuation | Not Applicable | No functionality requires device motion or accelerometer input. |
| 3.1.1 | Language of Page | Supports | <html lang="en"> present on all 14 pages; page language correctly declared to assistive technology. |
| 3.2.1 | On Focus | Supports | No unexpected context change (navigation, new window, form submission) occurs when any form control receives focus. |
| 3.2.2 | On Input | Supports | No unexpected context change when input value changes; contact form requires explicit submit button and does not auto-submit on input. |
| 3.2.6 | Consistent Help | Supports | Help and support mechanisms (contact email link in footer) are consistent in position and function across all pages. |
| 3.3.1 | Error Identification | Supports | Contact form fields marked required; native HTML5 validation displays field-specific error messages ("Please fill out this field", "Please enter an email address") on empty submit. |
| 3.3.2 | Labels or Instructions | Does Not Support | Name, Email and Message form fields on /contact carry plain-text <label> siblings without id/for association or wrapping <label>. Accessible name falls back to placeholder attribute, but persistent visible label is not programmatically tied to the control. Screen-reader users lose the label text once typing begins. Subject field has correct id/for association and serves as the reference implementation. Defect under active remediation. |
| 3.3.3 | Error Suggestion | Supports | Native HTML5 validation provides error-specific guidance: email field validation prompts correct format; other required fields prompt with field-specific messages. |
| 3.3.7 | Redundant Entry | Not Applicable | All forms on site (contact, waitlist, request-job-family) are single-page, single-submit processes. No multi-step flow asks the user for information already provided earlier in the same process. |
| 4.1.2 | Name, Role, Value | Supports | All interactive elements have accessible names and roles. Form inputs carry associated labels (programmatic association issue noted separately in 3.3.2); buttons carry text; links carry descriptive text. axe-core aria-input-field-name, button-name and link-name rules pass across verified pages. |
Level AA Conformance
| # | Criterion | Conformance | Notes |
|---|---|---|---|
| 1.2.4 | Captions (Live) | Not Applicable | No live audio or video content on the marketing site: no video, audio, iframe or embed element, no streaming or media-file request, and no link to a live-stream platform on any of the 14 pages (checked 2026-10-15). |
| 1.2.5 | Audio Description (Prerecorded) | Not Applicable | No prerecorded video on the marketing site (same check as 1.2.4). The one moving image, the homepage assessment-rate.gif, is a silent animated image, not video with an audio track. |
| 1.3.4 | Orientation | Supports | No page restricts display to portrait or landscape: all five sampled pages (/, /contact, /pricing, /waitlist, /request-job-family) render the same content with no horizontal overflow at 390x844 portrait and 844x390 landscape, and no stylesheet rule keys on orientation (checked 2026-10-15). |
| 1.3.5 | Identify Input Purpose | Partially Supports | /waitlist declares autocomplete="email" on its email field. The /contact Name and Email fields, and the /request-job-family Email and Organisation fields, collect the user's own details but carry no autocomplete attribute, so browsers and assistive tools cannot fill or identify them. Defect, not yet remediated: add autocomplete="name", "email" and "organization" to those fields. |
| 1.4.3 | Contrast (Minimum) | Supports | Normal text 4.5:1 or higher; large text 3:1 or higher on all pages. Teal CTA button (#3ECFBF) maintains 4.2:1 contrast against dark chrome in default, hover and focus states. Tested across 144 flagged nodes in automated scanning; all meet or exceed required thresholds. |
| 1.4.4 | Resize Text | Supports | Text remains readable and layout does not reflow incorrectly when zoomed 200%; no horizontal scrolling introduced. Tested by halving viewport from 1280 to 640px as the standard text-zoom proxy. |
| 1.4.5 | Images of Text | Supports | Text is not rendered as bitmap image. Wordmark ("score.") is real text (<span> + Metropolis font). Logo mark is SVG markup, not rasterised. |
| 1.4.10 | Reflow | Supports | Content reflows without loss at 320px viewport width; no horizontal scrolling occurs. All 14 pages tested at 320x720; scrollWidth === clientWidth on every one. |
| 1.4.11 | Non-text Contrast | Supports | UI components including buttons, borders, form inputs maintain 3:1 contrast minimum. Teal CTA border and background tested in default, hover and focus states. Cookie banner buttons meet 44x44px touch target. |
| 1.4.12 | Text Spacing | Supports | Page layout does not break when CSS is injected with WCAG reference technique (line-height 1.5, letter-spacing 0.12em, word-spacing 0.16em). Content reflows cleanly; no text clipping or overlap observed. |
| 1.4.13 | Content on Hover or Focus | Not Applicable | No hover/focus-triggered content (tooltips, modals) present on site. Cookie banner is persistent, not triggered by focus or hover, and does not obscure page content. |
| 2.4.5 | Multiple Ways | Supports | Multiple independent navigation paths exist (primary menu, footer link list, breadcrumb where applicable) to reach the same pages. |
| 2.4.6 | Headings and Labels | Supports | Each content section across all pages is introduced by a descriptive heading. Form fields carry descriptive, visible text labels (though programmatic association issue noted in 3.3.2). |
| 2.4.7 | Focus Visible | Partially Supports | A visible 2px teal outline is applied to every focused element via CSS and is present in computed styles. However, on pages taller than one viewport, the focused element often moves off-screen without scroll, rendering the visible indicator invisible to keyboard users. Defect under active remediation. |
| 2.4.11 | Focus Not Obscured (Minimum) | Does Not Support | On pages taller than one viewport, focus moves far below the visible area without auto-scroll. While the focus indicator itself is not obscured by overlaying content, a sighted keyboard-only user loses all visual track of focus; the indicator is scrolled out of view. Users report tabbing into invisible content. This is a functional keyboard-navigation defect. Fix is under active remediation; likely requires scrollIntoView({block: 'nearest'}) on focus or investigation of smooth-scroll library interactions. |
| 2.5.7 | Dragging Movements | Not Applicable | No drag-and-drop functionality on marketing site. |
| 2.5.8 | Target Size (Minimum) | Supports | All interactive targets meet 24x24px minimum via spacing exception (WCAG 2.5.8 Spacing criterion). Touch targets include adequate spacing from neighbouring interactive elements (nav items 36px horizontal gaps, footer items 18.5px vertical gaps). CTAs ("Get started" 110x33 to 157x55, "Sign in" 82x33) exceed 24x24px outright. |
| 3.1.2 | Language of Parts | Not Applicable | All content on all 14 pages is in English, matching <html lang="en">; no passage, phrase or label in another language was found, so no lang override is needed (checked 2026-10-15). |
| 3.2.3 | Consistent Navigation | Supports | Primary navigation structure, order and visual styling are identical across all 14 pages. No unexpected change in navigation menu appearance or function. |
| 3.2.4 | Consistent Identification | Supports | Interactive components with the same function use consistent labels. CTA "Get started" carries the same text and styling across all pages. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | Not Applicable | Contact form, waitlist form and job-family request form collect no legal, financial or sensitive personal data. No sensitive category is in scope for this criterion. |
| 3.3.8 | Accessible Authentication (Minimum) | Not Applicable | No login, authentication, or password-protected content on marketing site. |
| 4.1.3 | Status Messages | Not Assessed | Contact form success message cannot be verified without actual email submission (which would send a live email). No programmatic aria-live region or role="status" container is present in the static page markup to announce submission success. Recommend implementation of a visible, screen-reader-announced success message region before claiming "Supports". |
4. What to do if something is not accessible to you
If you use assistive technology and something on this site does not work for you, please tell us. Email legal@score-corp.com with:
- The page or link where the problem is.
- What assistive technology or browser setting you were using.
- What you expected to happen, and what happened instead.
We treat an accessibility report as a priority issue, not a routine support ticket. We will confirm receipt and give you a realistic timeline for a fix.
5. Enforcement bodies
Depending on where you are, you may also be able to raise an accessibility concern with a regulator or bring a claim:
- United States: Title III of the Americans with Disabilities Act (42 U.S.C. § 12182(a)).
- United Kingdom: the Equality Act 2010, sections 20 and 29 and Schedule 2 (the anticipatory reasonable-adjustments duty), enforceable through the courts; the Equality and Human Rights Commission can also intervene.
- European Union / EEA: the European Accessibility Act (Directive (EU) 2019/882), enforced by the relevant national market-surveillance authority in the member state where you are.
Raising a concern with us first is not a precondition to any of the above. We would simply rather have the chance to fix it.
6. Changes to this statement
We update this statement whenever our conformance status materially changes, in particular when our three known defects (contact form labelling 3.3.2, focus scroll-into-view 2.4.3/2.4.7/2.4.11, and missing input-purpose autocomplete attributes 1.3.5) are remediated and verified. The date at the top tells you when the current version took effect.