Accessibility Statement

Last updated: September 2026

I believe everyone should have equal access to information, including recipes, cooking resources, and the joy that comes from sharing food.

Accessibility matters to me. I want "FeastwithSafiya" to be a place where as many people as possible can find, understand, and enjoy my recipes, regardless of how they access the web.

I’m committed to learning, listening, testing, and continually improving the accessibility of "FeastwithSafiya".

My commitment

This blog contains many years of recipes and content. Some of my older posts were created before I had the accessibility knowledge and experience I have today. As a result, some legacy content may not fully follow current web accessibility best practices or the Web Content Accessibility Guidelines (WCAG).

I recognize that these barriers can make a real difference to someone's experience. A heading that isn't structured correctly, an image without meaningful alternative text, or a page that is difficult to navigate can prevent someone from accessing information that others can take for granted.

I don't want accessibility barriers to stand in the way of someone enjoying one of my recipes.

I am progressively reviewing older content and making improvements where I can. I also continue to deepen my knowledge and experience in web accessibility, including through accessibility testing and certification, so I can better identify and address barriers.

What I'm working to improve

As I review and update content, I pay attention to areas including:

  • Clear and logical heading structure
  • Meaningful alternative text for images
  • Descriptive and understandable links
  • Readability and content organization
  • Color contrast and visual presentation
  • Lists, tables, and other content structures
  • Keyboard accessibility where I have control over the implementation

My goal is to work toward WCAG 2.2 Level AA and to incorporate accessibility into how I create and maintain content. Not simply treat it as a one-time project.

Technology and third-party services

My food blog "FeastwithSafiya" uses a content management system, themes, plugins, and other services developed and maintained by third parties. Some functionality, embedded content, or technical accessibility issues may therefore be outside my direct control.

When I identify an issue within my control, I will make reasonable efforts to address it. Where an issue relates to a third-party component, I will explore available solutions and, where practical, work with the provider on alternatives.

I don't want the limitations of technology to be an excuse for ignoring accessibility. Even when I cannot immediately fix a technical issue, I want to understand it, acknowledge it, and look for ways to improve the experience.

I will review accessibility feedback and, where possible, work to address reported barriers.

An ongoing commitment

Accessibility isn't a destination or a checkbox. It's an ongoing commitment to learning, testing, listening, and doing better.

I know "FeastwithSafiya" may not be perfect today, particularly when it comes to older content. But being aware of that is not where the commitment ends.

I want to keep improving. I also want people with disabilities to feel welcome here and to know that their experience matters. If something on this site makes it harder for you to access a recipe, please tell me. Your feedback can help me make this website better for you and for others.

Tell me when something isn't working

You know your experience better than I do. If you encounter something on "FeastwithSafiya" that makes a recipe difficult to access, navigate, read, understand, or use, I would genuinely like to hear from you.

You don't need to know the technical terminology or identify a WCAG success criterion. Simply telling me what happened and what made the experience difficult is valuable.

If possible, please include the page where you experienced the issue and a brief description of what happened. If you know the browser, device, or assistive technology you were using, that information can also be helpful, but you don't need to provide technical details to contact me.

Thank you for helping me make this space more accessible and inclusive.