Accessibility statement | Strategic Meetings Management

Our commitment

This site is operated by Eureka Events Ltd. We want it to be usable by as many people as possible, including anyone using a screen reader, navigating by keyboard alone, relying on magnification or high contrast, or browsing with animation reduced.

It is mostly text and diagrams — explanatory pages, guides and two short forms — so the questions that matter are well-understood ones: clear structure, readable text, forms that behave, and nothing that traps a keyboard.

What has been done

These are specific things built into the site rather than aspirations:

Semantic HTML. Real headings in a logical order, real lists, real tables and landmark regions, so assistive technology can present the structure rather than a wall of text.
A skip link. The first thing a keyboard user reaches on every page is a link straight past the navigation to the main content.
Keyboard operation. Navigation, menus, in-page contents links and both forms work without a mouse, in a sensible order.
Visible focus. Whatever has keyboard focus is clearly outlined, on form fields and buttons included. Focus styling has not been removed anywhere.
Labelled form fields. Every field has a real label, hints are linked to the field they describe, and validation messages are associated with their field and announced rather than shown only in colour.
Colour contrast. Text and interface colours were chosen against the WCAG 2.2 AA contrast thresholds.
Responsive layouts. Pages reflow from wide screens to small phones without horizontal scrolling, and stay usable when text is enlarged.
Tables that reflow. Data tables restack as labelled cards on narrow screens instead of forcing a sideways scroll.
Reduced motion respected. Where the operating system asks for reduced motion, animation and transitions are suppressed.
No auto-playing media. Nothing starts on its own and nothing flashes.
No meaning carried by colour alone. Where colour distinguishes something, a label or text equivalent carries the same information.

What we do not claim

We are not claiming conformance. The site has been built with WCAG 2.2 level AA as the target standard, but that target has not been independently verified.

No formal third-party accessibility audit has been carried out. No testing with a representative range of assistive technologies and real users has been commissioned. Until both have happened, a claim of full or partial conformance would not be evidenced, so we are not making one.

There is a meaningful difference between building to a standard and meeting it, and organisations that assess suppliers on accessibility are entitled to see that difference stated plainly rather than have it blurred by a conformance badge.

Known limitations

The operator must complete this section once testing has taken place. It should list each known problem, the WCAG 2.2 success criterion it fails, what that means in practice for someone using the site, and when we expect it to be fixed — or, where it will not be, why.

Areas most likely to need entries include the SVG diagrams and whether their text alternatives convey what the picture does, the in-page contents component, the interactive readiness assessment, and any third-party content embedded in future.

An empty list here means work not yet done, not a site without problems.

How to report a problem

If something on this site is difficult or impossible to use, please tell us. Reports from people who hit the problem are more useful than any checklist.

Email hello@strategicmeetingsmanagement.co.uk, telephone 020 8102 1105, or use the form on our contact page. It helps if you can say which page you were on, what you were trying to do, what happened instead, and what you were using — browser, device and any assistive technology — but tell us even if you cannot supply all of that.

If you need information from this site in a different format, ask. We can usually supply a page as plain text, large print or an accessible document, and we would rather do that than have you go without the content.

How quickly we respond

Acknowledgement — within two working days of receiving your report.
A substantive reply — within ten working days, telling you what we have found and what we intend to do.
A fix, where one is straightforward — as part of the next routine release rather than held for a scheduled review.
An alternative format request — supplied within ten working days wherever we reasonably can.

Where something will take longer, we will say so and tell you when to expect it rather than letting the report go quiet. These commitments must be confirmed by the operator as ones the business can genuinely meet before this page is published.

Preparation of this statement

This statement was prepared on the basis of how the site was built, reviewed against the WCAG 2.2 AA success criteria by the team that built it. No external auditor has reviewed it. It will be updated when the site changes materially or when an audit is carried out, whichever comes first, and the date at the top shows the last review.

If any of this does not match your experience of using the site, we would like to hear it. The quickest route is the form on our contact page.