Accessibility Statement

The 7 Brews Menu is committed to making this site usable by as many people as possible, regardless of disability, device or assistive technology. That commitment carries particular weight here: our allergen guide and nutrition tables hold information people rely on for health reasons, and an inaccessible allergen table is not an inconvenience but a real exclusion.

We treat accessibility as part of editorial quality rather than a compliance afterthought. A page that a screen-reader user cannot navigate is a page that does not work, in the same way that a page with a wrong calorie count does not work.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. We design and build against those success criteria and treat them as the standard for new work.

These are things we have actively built in, not aspirations:

• Semantic HTML. Real headings in a logical order, real lists, real tables with proper header cells and scope attributes, and landmark regions so navigation, main content and footer are distinguishable.
• Keyboard operability. Interactive elements are reachable and operable by keyboard, with a visible focus indicator on every focusable element rather than a suppressed outline.
• Content before interaction. Menu guides, prices and nutrition tables are server-rendered HTML. Reading the core content does not depend on client-side scripting.
• Text alternatives. Meaningful images carry descriptive alternative text; decorative graphics are hidden from assistive technology so they do not add noise.
• Colour is never the only signal. Warnings, allergen flags and status indicators pair colour with text or an icon.
• Contrast. Body text and interface elements are designed to meet AA contrast ratios against their backgrounds.
• Reduced motion. Animations respect the prefers-reduced-motion setting and are disabled when you have asked your system for less movement.
• Resizable text and reflow. Layouts use relative units and reflow to a single column, so zooming to 200% or more does not require horizontal scrolling to read a paragraph.
• Descriptive link text. Links describe their destination instead of saying "click here", which matters when a screen reader lists links out of context.
• Labelled form controls. Every input on our contact form has a properly associated label, and required fields are indicated in text.
• Print styles. Policy and guide pages print cleanly, which helps anyone who prefers paper or a larger physical format.

Third-party advertising

Ad markup is injected by an external network. We control placement, not the contents, and some creatives will not meet the standards we apply to our own markup. Mitigation: ads never sit inside a reading flow you must pass through, and they never obscure content or block keyboard navigation.

Interactive maps

The map component on location pages is third-party and its keyboard and screen-reader support is imperfect. Mitigation: every address, and where available every phone number and set of hours, is presented as text on the page, so no information exists only inside the map.

Complex data tables on small screens

Wide comparison tables scroll horizontally on narrow viewports, which is harder to work with when magnified. Mitigation: scroll regions are focusable and labelled; we are progressively adding stacked layouts.

The drink customiser

The most complex interface on the site, with many dependent options. It is keyboard operable, but the announcement of dynamic updates has not been fully validated with screen readers.

Older PDF guides

Some downloadable PDFs may lack full tagging for reading order. Mitigation: every PDF's content is also available as an HTML page, which is the accessible route.

Reader-submitted images

Photographs of menu boards may carry less detailed alternative text than our own graphics. Mitigation: any price or item shown in a submitted photo is transcribed into our text tables.

We do not consider these acceptable indefinitely. Section 10 sets out what we are working on.

Our current approach, described accurately:

• Self-evaluation against the WCAG 2.2 Level AA success criteria during development.
• Automated testing with standard tooling to catch contrast failures, missing labels, missing alternative text and structural problems.
• Manual keyboard testing. Navigating pages and tools using only a keyboard.
• Zoom and reflow testing at 200% and above, and at narrow viewport widths.
• Reader reports, which have found real problems that no tool flagged.

What we have not done:

• Commissioned an independent third-party accessibility audit.
• Completed systematic testing across the full range of screen readers and platform combinations.
• Conducted usability testing with disabled participants. the most valuable method, and the one we have not yet been able to arrange.

Automated tools reliably detect only a minority of accessibility issues. We treat a clean automated result as a floor, not a pass.

The site is built on standard semantic HTML, which is the foundation assistive technology depends on, and should therefore work with current versions of common combinations such as NVDA or JAWS with Windows browsers, VoiceOver on macOS and iOS, and TalkBack on Android, as well as voice-control and magnification software.

We describe this as "should work" rather than "is certified", because we have not completed systematic testing across those combinations. If you use assistive technology and something on this site does not work, that is exactly the report we most want. see section 9.

• Reduce motion: enable the reduced-motion setting in your operating system and our animations will not play.
• Zoom freely: use browser zoom (Ctrl or Cmd with + / −). Pages reflow to a single column instead of forcing horizontal scrolling.
• Print or save as PDF: our policy pages carry print styles and a print button, which strips navigation and ads for a clean read.
• Use reader mode: our semantic markup works well with browser reading modes if you prefer a simplified view.
• Keyboard shortcuts: Tab and Shift + Tab move between interactive elements, Enter or Space activates them, and arrow keys scroll wide tables once focused.
• Prefer text to maps: on location pages, the text address block carries the same information as the map.

If any part of this site is difficult or impossible for you to use, please tell us. We treat these reports as bugs with priority, not as suggestions.

1. Email the7brewsmenu@gmail.com with "Accessibility" in the subject line, or use the contact form.
2. Tell us what you can. The page URL, what you were trying to do, what happened instead, and. If you are comfortable sharing it, your browser and assistive technology. Any one of these helps; you do not need all of them.
3. We acknowledge within 2 business days, with a real reply from a person.
4. We fix or explain. Straightforward issues are usually fixed within days. For anything larger, we tell you the plan and the expected timeframe rather than leaving you waiting.
5. If it is a third-party component we cannot fix directly, we will say so plainly, raise it with the provider, and offer an alternative route to the information you needed.

If you need information from this site in a different format, a table read out, a figure explained, a page in plain text. Ask and we will send it. There is no process to follow and no form to fill in.

Our current accessibility priorities, in order:

1. Screen-reader validation of the allergen guide and calculators, because those carry the highest-stakes information on the site.
2. Stacked mobile layouts for wide comparison tables, removing the horizontal-scroll requirement.
3. Announcement of dynamic updates in the drink customiser, so calculated totals are conveyed as they change.
4. Alternative-text review across older reader-submitted images.
5. Tagged, accessible PDF regeneration for downloadable guides.
6. Independent review when resources allow, since self-assessment has limits we recognise.

A reported barrier moves to the front of this list. Real reports beat our own prioritisation, because they describe problems people are actually hitting.

Accessibility feedback

the7brewsmenu@gmail.com. Subject line "Accessibility"

Contact form

https://the7brewsmenu.com/contact

Acknowledgement

Within 2 business days

Standard we target

WCAG 2.2 Level AA

Statement status

Partially conformant, self-assessed. Reviewed at least every six months.

Related

Editorial Policy. Writing for everyone