Accessibility
Last reviewed: May 28, 2026
This statement explains how Code Quality Check ("we", "us") approaches accessibility on codequalitycheck.com and how to tell us if something on the site does not work for you. We aim to make our service usable by people with disabilities and to provide an equivalent experience for all visitors. We treat accessibility as ongoing work, not a one-time check.
We aim to review this page on a six-month cadence and after material changes to the site.
Accessibility contact: accessibility@codequalitycheck.com
1. Standard and scope
We target Web Content Accessibility Guidelines (WCAG) 2.2 Level AA on the public pages of codequalitycheck.com, including the scanner and scan result pages.
Scope on the scan result page is in three tiers:
- The site interface itself (page chrome, navigation, forms, result summaries, footer): in scope.
- How we render data from the sites you scan (the layout and formatting that surrounds scan output): in scope.
- Content originating from the sites you scan (titles, URLs, image contents, extracted snippets shown in scan results): out of scope, since we cannot fix accessibility issues in content we did not author.
Out of scope for this statement: authenticated dashboard pages and other non-web product surfaces.
2. Jurisdictions
Israel
Conforms to Israeli Standard 5568 Part 1 (September 2023), which adopts WCAG 2.0 with Israeli amendments. We additionally target the broader WCAG 2.2 AA, which is forward-compatible with the WCAG 2.0 AA basis of IS 5568. This statement also covers the accessibility arrangements required by regulation 34A of the Equal Rights for Persons with Disabilities Regulations (Service Accessibility) 5773-2013; see section 10.
Other jurisdictions
We voluntarily target WCAG 2.2 AA, which is the technical bar used by the EU Accessibility Act (EN 301 549), the UK Equality Act 2010, and US ADA Title III case law, and which exceeds the WCAG 2.0 AA basis of US Section 508. We make no binding commitment under these regimes today; we report WCAG 2.2 AA as the unifying conformance target.
3. Conformance status
Partially conformant. codequalitycheck.com partially conforms with WCAG 2.2 Level AA. "Partially conforms" means some parts of the content do not fully meet the standard.
On the pages we have evaluated, we know of no blocking accessibility issues as of the last review date. We describe our status as "Partially conformant" rather than "Fully conformant" because our evaluation is a self-evaluation, not a third-party audit.
4. What we have done
Concrete steps we have taken to make the service accessible:
- Navigation is consistent across pages. A skip-to-main-content link is the first focusable element on every page.
- Content is written in plain language and organised hierarchically. Pages use a single
<h1>and consistent heading order. - Pages reflow at 320 CSS pixels width (WCAG 1.4.10) without horizontal scrolling.
- All graphic elements have a textual alternative. Decorative graphics are marked to hide from assistive technology.
- Font sizes scale with browser zoom up to 400% without loss of content or functionality.
- The site does not use moving, blinking, or auto-playing content.
- Forms have programmatic labels and clear error messages. Error states are announced via ARIA live regions.
- The site has been tested with keyboard-only navigation. Every interactive element is reachable, with a visible focus indicator. No keyboard traps.
- The site has been tested with NVDA + Chrome on Windows. Landmarks, headings, and toggle states are announced correctly.
- The site respects browser and operating system preferences for reduced motion, light or dark colour scheme, increased contrast, and forced-colors mode.
- Information pages on the site work without JavaScript. The scanner and authenticated areas need JavaScript to function.
5. Accessibility preferences widget
The site offers a small preferences widget in the bottom-right of every page. It opens a panel with toggles for text size, text spacing, contrast, theme, reduced motion, link underlining, and a stronger focus indicator. The widget saves your choices to local storage on this site so they apply on later visits. A Reset button clears every saved choice.
The widget is a convenience layer for visitors who do not want to change their browser or operating system preferences. It is not the basis for our accessibility claims. The site is built and tested to be accessible independently of the widget. Industry guidance (the multi-vendor Overlay Fact Sheet signed by Deque, TPGi, WebAIM and others) is explicit that accessibility-overlay widgets do not produce conformance; conformance comes from how the underlying page is built.
We do not detect or infer that you use assistive technology, and we do not store any disability label. The widget only writes the toggle values you set on the panel.
6. How we evaluated this
We follow the W3C WCAG-EM self-evaluation methodology.
Automated checks: axe-core (WCAG 2.0 / 2.1 / 2.2 A and AA tags, plus best-practice rules) injected via Playwright across nine sampled pages; per-page tab-order recording; focus-visibility checks; reflow checks at 320 CSS pixels viewport; forced-colors and reduced-motion emulation captures.
Manual checks: keyboard-only navigation, focus order verification, 200% and 400% browser zoom, forms-with-deliberate-errors, NVDA + Chrome screen-reader read-through on the main flow, reduced-motion and forced-colors visual review, live-region announcement timing.
We document the sample, the methodology, the findings, and the conformance conclusion in an internal evaluation report, available on request at accessibility@codequalitycheck.com. We re-run the automation and the manual checks on a six-month cadence and after material changes.
7. Compatibility
The site is designed to work in current versions of Chrome, Firefox, Safari, and Edge. Screen-reader compatibility verified with NVDA + Chrome on Windows. Other assistive-technology combinations (VoiceOver + Safari on macOS, JAWS, TalkBack on Android, etc.) have not been spot-checked in this pass; if you use one and run into issues, please tell us so we can address them and broaden the verified set.
8. Known limitations
As of May 28, 2026: no known blocking accessibility issues on the pages we have evaluated.
If you find an issue we have not listed, please tell us using the channel in section 9.
9. Report an accessibility problem
If something on the site does not work for you, please email accessibility@codequalitycheck.com.
We aim to acknowledge accessibility reports within 5 business days, and to respond substantively as soon as we can, typically within a few weeks depending on the complexity of the issue.
To help us reproduce the problem, please include:
- A description of the problem and what you were trying to do.
- The URL of the page you were on.
- Your browser type and version.
- Your operating system.
- Any assistive technology you were using (and its version).
You can also reach us via the contact form linked from the site footer. If your concern is not resolved through this channel, you may contact the national equality body in your jurisdiction.
10. Accessibility arrangements
This section covers the accessibility arrangements required by regulation 34A of the Israeli Equal Rights for Persons with Disabilities Regulations (Service Accessibility) 5773-2013.
Our team handles accessibility-related requests through the feedback channel in section 9, within the response window stated there.
Israeli regulations require organisations above 25 employees to name a dedicated accessibility coordinator (רכז נגישות); our organisation is below that threshold.
We do not operate physical premises open to the public, so no physical accessibility arrangements apply. We do not offer phone support; accessibility-related contact is via the email or contact-form routes in section 9.
11. Responsible role
Responsible role: CQC Accessibility Contact, reachable via accessibility@codequalitycheck.com.
12. Changes to this page
We update this page when the site's accessibility posture changes (new features, new tested combinations, fixed issues) or when the widget itself changes.
- First version of the accessibility statement published. Structure based on Israeli regulations 91 + 34A, W3C WAI guidance, and US Section 508 model statements.