Skip to main content
MAMAM

Accessibility Statement

Last updated: March 7, 2026

Our Commitment

MAMAM aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We believe cooking and saving should be accessible to everyone, and we work to make this website usable with assistive technologies including screen readers, keyboard navigation, and voice control.

This site includes the following accessibility features:

  • Skip to main content link for keyboard users
  • Semantic HTML landmarks (header, main, footer, nav)
  • aria-label attributes on navigation regions and interactive elements
  • aria-current="page" on active navigation links
  • Mobile navigation implemented as an accessible dialog element
  • <time datetime> elements on all published dates
  • Visible focus rings on all interactive elements
  • Animations respect prefers-reduced-motion

Known Exceptions

We are aware of the following accessibility gaps and are working to address them:

1. Savings chart image in blog post (WCAG 1.1.1, Level A)

The blog post "How Cooking at Home Saved Me $3,000 This Year" includes a savings chart image (savings-chart-placeholder.png) that currently has inadequate alt text. The image conveys savings data that is not available in text form. We plan to replace this image with a text-equivalent data visualization or descriptive alt text in a future update.

2. Entrance animation visibility on direct deep links (WCAG 2.2.2, Level A)

Scroll-triggered entrance animations on below-fold sections initialize elements at opacity: 0 before checking prefers-reduced-motion. If a user navigates directly to a URL fragment pointing to a below-fold section (for example, #features), the IntersectionObserver threshold may not be met and the content could remain invisible. Users who prefer reduced motion or who navigate via anchor links may be affected. We plan to fix the initialization order in a future update.

3. Code blocks not keyboard-scrollable on narrow viewports (WCAG 2.1.1, Level A)

Code block elements (<pre>) in blog posts overflow horizontally on narrow viewports. This overflow region is not reachable via keyboard alone (Tab key does not focus the scrollable container). Users relying solely on keyboard navigation cannot access the full content of wide code blocks on mobile. We plan to add tabindex="0" to scrollable code blocks in a future update.

Contact Us

If you experience accessibility barriers on this site or have feedback on how we can improve, please contact us at support@mamamfood.com . We aim to respond within 5 business days.

This statement was prepared on March 7, 2026. It will be reviewed and updated as we make improvements to the site.