Paatti's Kitchen

Accessibility Statement

Last reviewed: May 2, 2026

Paatti’s Kitchen is committed to being usable by the widest possible audience, including readers who use assistive technology such as screen readers, keyboard-only navigation, screen magnifiers, voice control, and refreshable braille displays.

Our conformance target

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard referenced by the U.S. Department of Justice for ADA Title III compliance and adopted by the European Accessibility Act, the UK Public Sector Bodies Accessibility Regulations, and most other major accessibility laws.

What we have done

The Site has been designed and reviewed against WCAG 2.1 AA with the following measures in place:

  • Keyboard navigation. Every interactive element — header navigation, category dropdown, mobile menu, search field, footer links, recipe pages — is reachable and operable with the Tab, Shift-Tab, Enter, Space, and arrow keys. A “Skip to content” link is the first focusable element on every page so keyboard users can bypass the sticky header.
  • Visible focus. All interactive elements show a clear focus ring when reached by keyboard.
  • Semantic structure. Pages use real <header>, <nav>, <main>, <article>, and <footer> landmarks, headings in a logical order, lists for lists, and <time> for dates so screen readers can navigate and announce content correctly.
  • Color and contrast. Body text, links, recipe-card text, and pagination controls meet or exceed the 4.5:1 contrast ratio WCAG requires for normal text. Active navigation and current pagination state are indicated by more than color alone (an underline, an aria-current attribute, and a stronger weight).
  • Reduced motion. Card-hover and image-zoom animations honor the operating-system “reduce motion” setting.
  • Responsive layout. Pages are usable down to a 320 px viewport without horizontal scrolling, which also benefits users who magnify their browser.
  • Structured recipes. Each recipe is published as Schema.org Recipe data in addition to readable HTML, so recipe apps and assistive tools can present ingredients and steps in their preferred format.

Known limitations

Accessibility is an ongoing process and we are aware of areas that are not yet fully compliant:

  • Image alt text on legacy recipe posts. This site was migrated from a long-running WordPress blog. Many older recipe images carry alt text that was auto-generated from the post title rather than written specifically for the image (for example “Authentic Sambar Recipe” rather than “A bowl of sambar with curry leaves and a swirl of ghee”). We are improving these on a rolling basis as posts are updated. Newer recipes published since the redesign use descriptive, hand-written alt text.
  • Search interface. The on-site search is provided by Pagefind, an independent open-source library. Its keyboard and screen-reader behavior is generally good but is maintained by a third party rather than by us, so we cannot guarantee perfect conformance for every interaction within the search widget.
  • Embedded advertising. The Site is supported by Google AdSense, which inserts ad units we do not directly control. The accessibility of any individual ad is the responsibility of its advertiser; if you encounter an ad that is unusable with assistive technology, please tell us and we will raise it with Google.

Compatibility

Paatti’s Kitchen is designed to work with the latest two major versions of:

  • Browsers: Chrome, Edge, Firefox, Safari (desktop and iOS), Samsung Internet (Android).
  • Screen readers: VoiceOver (macOS, iOS), NVDA and JAWS (Windows on Chrome, Edge, or Firefox), and TalkBack (Android).

Older browsers, browsers in unusual configurations, or assistive technologies older than two major versions may experience reduced fidelity but should still provide access to the underlying content.

Reporting a problem

If something on the Site is hard to use, breaks with your screen reader, has poor contrast, or otherwise creates a barrier, please tell us. We treat these reports as priority bugs.

Email: [email protected]

When you write, it is helpful (but not required) to include:

  • The page URL where you encountered the problem.
  • A short description of what happened and what you expected.
  • Your operating system, browser, and assistive technology, if you know them — for example “VoiceOver on iOS 18 in Safari” or “NVDA 2024.4 on Windows 11 in Firefox.”

We aim to respond to accessibility reports within five working days and to fix verifiable barriers within thirty working days. Where a fix takes longer (for example, retroactively rewriting alt text across thousands of legacy images), we will tell you the plan and the expected completion timeline.

Formal complaints

If you are not satisfied with our response to an accessibility complaint, you may also contact the relevant authority for your jurisdiction. In the United States, that is the Department of Justice Civil Rights Division. In the European Union and the United Kingdom, your national equality or data-protection authority handles complaints under the European Accessibility Act and equivalent national laws.

Reviewing this statement

This statement is reviewed at least annually and after any major redesign of the Site. The “Last reviewed” date at the top of the page is updated each time it is reviewed, whether or not the content changes.