Accessibility: Everybody deserves a fair shot at the pizza.

Contact Us
Emotional Support Pizza™ Pizza • Wings • Questionable Coping Mechanisms
Pickup Delivery
Accessibility

Pizza Should Be Easier To Reach.

This sample accessibility statement describes the goal of providing a restaurant website that can be used by as many people as reasonably possible.

→ Need Assistance Contact Us Tell the restaurant if you encounter an accessibility barrier or need help using the website. → Looking For Food Browse Menu Because eventually this should lead back to pizza.
Template Notice

Review This Before Launch.

Emotional Support Pizza™ is a fictional restaurant used to demonstrate this website template. The final website owner must review the completed website and replace this sample statement with information that accurately reflects the real business.

01
“Does installing this template automatically make every final website accessible?”
No Accessibility depends on the final content, customizations, integrations, images, forms, ordering tools, third-party services, and ongoing maintenance.
02
“Should the finished website be tested?”
Yes The website owner should review and test the final site after replacing sample content and after making substantial changes.
03
“Can third-party services affect accessibility?”
They Can Ordering systems, payment interfaces, maps, rewards tools, forms, and other external services may have accessibility characteristics of their own.
Our Goal

Useful To More People.

The goal is straightforward: make important restaurant information and website functions understandable, perceivable, and reasonably usable across different ways of interacting with the web.

01
Keyboard Use
Navigation Important links, buttons, navigation controls, and interactive features should be usable without requiring a mouse whenever reasonably possible.
02
Clear Structure
Organization Pages should use meaningful headings, landmarks, labels, links, and content structure so information is easier to understand and navigate.
03
Visible Focus
Orientation Keyboard users should be able to identify which interactive control currently has focus.
04
Readable Content
Legibility Text, controls, labels, and important information should maintain useful contrast, readable sizing, and clear presentation.
05
Responsive Layout
Different Screens Content should remain usable across desktop, tablet, and mobile layouts without requiring unreasonable horizontal scrolling.
06
Understandable Controls
Clear Actions Buttons, links, forms, and interactive elements should communicate what they do before somebody activates them.
Images & Media

Pretty Pictures Still Need Context.

Restaurant websites are visual. Important information should not depend exclusively on being able to see an image.

01
Informative Images
Text Alternatives Images that communicate meaningful information should receive appropriate text alternatives when needed.
02
Decorative Images
Avoid Noise Decorative photography should not create unnecessary information for assistive technologies when it does not add meaning.
03
Text Inside Images
Use Carefully Important restaurant information should generally remain available as real page text rather than existing only inside an image.
Forms & Ordering

Forms Should Not Fight Back.

Contact, ordering, catering, account, and checkout interfaces should provide understandable instructions and feedback.

01
Labels
Identify Inputs Form controls should have understandable labels or instructions so users know what information is being requested.
02
Errors
Explain The Problem When a form cannot be submitted, error information should help users understand what needs attention whenever possible.
03
Status Messages
Confirm What Happened Important confirmation, success, failure, and order-status information should be presented clearly to the user.
Third-Party Services

Sometimes The Pizza Leaves This Website.

The final restaurant may use outside platforms for ordering, payments, maps, delivery, rewards, reservations, or other services.

01
External Platforms
Separate Systems Third-party services may be designed, maintained, and controlled by companies other than the restaurant.
02
Review Integrations
Before Launch The final website owner should review accessibility when adding or replacing embedded tools, widgets, forms, payment systems, and external ordering services.
03
Need Help?
Contact The Restaurant If an external service creates a barrier, customers should have a reasonable way to contact the restaurant for assistance.
Accessibility Assistance

Tell Us What Went Wrong.

If you cannot access information, complete an action, or use part of the website, contact the restaurant and describe the problem.

→ Report A Barrier Contact Restaurant Tell us which page or feature caused difficulty and what you were trying to do. → Restaurant Information Locations Find sample hours, service information, pickup, and delivery details.
Accessibility Feedback

Specific Is Extremely Helpful.

When reporting an accessibility issue, useful details make investigation easier.

01
Which Page?
Location Tell the restaurant which page, form, button, menu, or feature you were using.
02
What Happened?
Describe The Barrier Explain what prevented you from reading, navigating, understanding, or completing the intended action.
03
What Were You Trying To Do?
Desired Result Tell us whether you were trying to order, read the menu, find restaurant information, contact the business, or perform another task.
Ongoing Review

Websites Change. Check Them Again.

Accessibility is not something the final website owner should review once and then forget.

01
New Content
Review It New pages, images, promotions, menu changes, and other content should continue using accessible patterns.
02
New Technology
Test It New plugins, ordering systems, forms, embeds, integrations, or interactive components can introduce new barriers.
03
Customer Feedback
Use It Accessibility reports from real users can identify issues that automated checks and development testing may miss.
Statement Details

Replace The Sample Details.

The final restaurant owner should update this statement after the finished website and its real services have been reviewed.

01 Statement Date Replace Before Launch Add the date the final accessibility statement was reviewed or updated.
02 Assistance Contact Add Real Contact Details Provide the restaurant's real method for accessibility questions and assistance requests.
Need Assistance?

Tell A Human.

If something on the website prevents you from getting the information or service you need, contact the restaurant.

Contact Us View FAQ