Accessibility

Built for every crocheter.

Many crocheters have arthritis, low vision, or other accessibility needs. We design the site so everyone can use it. Here's our standard and how to report problems.

Last updated: 11 May 2026

Our target

Crochet Calc aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across all pages. We are not perfect, but we treat barriers as bugs and fix them.

What we do

  • Semantic HTML — pages use real headings, real lists, real form labels. Screen readers can navigate the structure.
  • Keyboard navigation — every interactive element (calculator inputs, FAQ disclosures, navigation, buttons) is reachable and operable from the keyboard alone.
  • Visible focus indicators — keyboard focus is always visible, with a 3 px outline on form fields and clear focus rings on links and buttons.
  • Colour contrast — body text contrast ratio is at least 7:1 (WCAG AAA), and interactive elements are at least 4.5:1 (WCAG AA).
  • Resizable text — all text scales to 200 % without layout breaking. The site uses rem units throughout.
  • Reduced motion — animations respect the prefers-reduced-motion system setting. If you have vestibular sensitivity, motion is suppressed automatically.
  • Skip link — every page begins with a "skip to content" link for screen-reader and keyboard users.
  • Form labels — every calculator input has an explicit <label> tag. Placeholder text is never used as the only label.
  • Image alt text — informative images carry descriptive alt text; decorative images carry an empty alt attribute so screen readers skip them.
  • Language tag — pages declare lang="en" so screen readers pronounce content correctly.

What may still be a barrier

We are honest about gaps:

  • Long-form articles — some technique articles include diagrams. Where a diagram is essential, we describe the technique in text as well, but the description isn't always equal to the visual.
  • Complex calculator results — the results card includes multiple numbers in a grid. Screen-reader users hear them sequentially. If the linear order is confusing, please tell us.
  • Third-party content — ads served by Google AdSense and embedded video from YouTube are not under our direct accessibility control. We choose ad placements that don't overlap content and we lazy-load embeds so they don't interfere with focus order.

Browsers and assistive technology we test with

  • Recent versions of Chrome, Firefox, Safari, and Edge on desktop and mobile
  • VoiceOver on macOS and iOS
  • NVDA on Windows
  • 200 % browser zoom
  • Keyboard-only navigation

How to report an accessibility problem

If you encounter a barrier, please write to [email protected] and include:

  • The URL where you found the problem
  • What you were trying to do
  • What happened instead
  • The assistive technology you were using (if any), and its version

We aim to respond within 5 business days and to fix confirmed accessibility bugs within 14 days, depending on complexity. Critical barriers (a calculator that can't be used at all with a keyboard, for example) are prioritised same-day.

Compliance and standards

The site targets WCAG 2.2 Level AA. We are not formally audited, and we make no claim of complete compliance — accessibility is a continuous process. We follow the published WCAG 2.2 Quick Reference when developing and reviewing pages.

✦

Accessibility is everyone's craft. Thanks for helping us improve.

WCAG 2.2 AA compliance

We design and build this site to conform with the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA. WCAG 2.2 AA is the international standard for web accessibility and covers four key principles: perceivable (content can be presented in ways users can perceive), operable (interface components and navigation must be operable), understandable (information and operation must be understandable), and robust (content must be robust enough to be interpreted by assistive technologies).

Specific WCAG 2.2 AA criteria we meet include: 1.1.1 Non-text Content (all meaningful images have descriptive alt text); 1.4.3 Contrast Minimum (text contrast ratio at least 4.5:1 against background); 1.4.10 Reflow (content reflows for mobile and zoomed viewports); 1.4.12 Text Spacing (text remains readable when users adjust line height and spacing); 2.1.1 Keyboard (all functionality available via keyboard alone); 2.4.4 Link Purpose (link text describes destination); 2.4.7 Focus Visible (keyboard focus indicators are clearly visible); 3.1.1 Language (page language is declared); 3.3.1 Error Identification (form errors are identified and described); 4.1.2 Name, Role, Value (UI components are properly identified for assistive technology).

Keyboard navigation

All site functionality is accessible by keyboard alone, without requiring a mouse or touchscreen. Key keyboard shortcuts:

  • Tab — move forward to the next interactive element (link, button, form field).
  • Shift + Tab — move backward to the previous interactive element.
  • Enter — activate the focused link or button.
  • Space — activate the focused button or check/uncheck checkboxes.
  • Arrow keys — navigate within select menus, radio button groups, and similar grouped controls.
  • Escape — close any open modal or dropdown menu.

The site includes a visible focus indicator on every interactive element, so keyboard users can always see which element will activate when they press Enter or Space. We also provide "skip to main content" links at the top of every page to help keyboard users bypass repeated navigation.

Screen reader compatibility

We test the site with major screen readers including NVDA, JAWS, VoiceOver, and TalkBack. Articles use semantic HTML5 structure (heading hierarchy, lists, blockquotes, code blocks) so screen readers can announce content structure clearly. Calculators include accessible labels on every form field, descriptive button text, and live regions that announce results when calculations complete.

Decorative images use empty alt attributes so screen readers skip them. Meaningful images include descriptive alt text. Complex visualisations (tables, charts) include adjacent text descriptions of the underlying data. Mathematical formulas in articles are presented as text rather than rendered images so they can be read aloud by assistive technology.

Visual accessibility features

Text contrast meets or exceeds 4.5:1 for normal text and 3:1 for large text, against all background colours used on the site. Users can zoom the site up to 400% without loss of functionality or content. Text size can be increased via browser controls without breaking the layout. The site respects user system preferences for reduced motion (animations are simplified or eliminated when the operating system indicates this preference).

We do not rely on colour alone to convey information — every meaningful colour distinction is paired with text, icons, or patterns. Forms include text-based error messages, not just colour highlighting. Status indicators use both colour and text or icons.

Reporting accessibility issues

We take accessibility seriously and welcome reports of any issue that prevents you from using the site effectively. To report an accessibility issue, please contact us at [email protected] with: the URL of the affected page, a description of the issue, the assistive technology you were using (if applicable), and what task you were trying to complete. We commit to acknowledging accessibility reports within 2 business days and resolving issues that affect critical functionality (calculators, navigation, content reading) within 30 days.