Accessibility Statement

Last updated August 13, 2026

Our commitment

79th Street Pharmacy is committed to making our website and our store usable by everyone, including people who use screen readers, keyboard navigation, magnification, captions, or other assistive technology. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and treat accessibility as ongoing work, not a one-time project.

What we have done on this website

  • Semantic headings and landmarks so screen readers can navigate page structure.
  • Text alternatives for meaningful images and icon-only controls.
  • Color contrast reviewed against WCAG AA minimums for body and supporting text.
  • Keyboard-operable navigation, menus, forms, and dialogs with visible focus states.
  • Responsive layouts that reflow at 200% zoom and on small screens.
  • Forms with visible labels and clear, text-based error messages.

In-store accessibility

  • Large-print prescription labels and medication information on request, free of charge.
  • Verbal counseling from a pharmacist for anyone who cannot read printed materials.
  • Free language assistance and interpretation - see our Notice of Nondiscrimination.
  • Free local delivery for patients who have difficulty traveling to the store.
  • Staff assistance at the counter for anyone who needs it.

Known limitations

Some third-party content embedded on our site - such as review widgets and social feeds - is controlled by outside vendors and may not fully meet WCAG 2.1 AA. Where a third-party component creates a barrier, we will provide the same information or service to you directly by phone or in person.

Report a barrier

If any part of this website or our store is difficult for you to use, tell us and we will help you personally and work to fix it. We aim to respond within two business days.

Phone: (646) 370-5978
Email: 79thstrx@gmail.com
In person: 215 W 79th Street, New York, NY 10024

Please tell us the page address, what you were trying to do, and the assistive technology or browser you were using so we can reproduce the issue.