top of page

Accessibility Statement for Papi Tacos & Churros

This is an accessibility statement from Papi Tacos & Churros.

Measures to support accessibility

Papi Tacos & Churros takes the following measures to ensure accessibility of Papi Tacos & Churros:

  • Include accessibility throughout our internal policies.

  • Integrate accessibility into our procurement practices.

  • Appoint an accessibility officer and/or ombudsperson.

  • Employ formal accessibility quality assurance methods.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Papi Tacos & Churros is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Feedback

We welcome your feedback on the accessibility of Papi Tacos & Churros. Please let us know if you encounter accessibility barriers on Papi Tacos & Churros:

  • On Instagram @papitacoschurros

We try to respond to feedback within 24 hours.

Technical specifications

Accessibility of Papi Tacos & Churros relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • CSS

  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Limitations and alternatives

Despite our best efforts to ensure accessibility of Papi Tacos & Churros , there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations for Papi Tacos & Churros:

  1. Homepage video: Uploaded video is promotional and shows our food.

Assessment approach

Papi Tacos & Churros assessed the accessibility of Papi Tacos & Churros by the following approaches:

  • Self-evaluation

Date

This statement was created on 2 June 2022 using the W3C Accessibility Statement Generator Tool.

bottom of page