This site, and the meetings we run.

This website

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

What that means in how this site is built:

• Semantic HTML with landmark regions and a single, logical heading hierarchy on every page
• A skip-to-content link that becomes visible on keyboard focus
• Complete keyboard operation, with a visible focus indicator on every interactive element
• Navigation that works without JavaScript — the site functions fully with scripting disabled
• Body text meeting AA contrast; the clay accent is reserved for large text, links, and interface elements rather than body copy, and grey for captions only
• Information never conveyed by colour alone; status in tables is stated in words
• Touch targets of at least 44 by 44 pixels
• Reflow to a single column without horizontal scrolling down to 320 pixels wide, and usable at 200% and 400% zoom
• Wide tables scroll within their own container so the page itself never scrolls sideways
• prefers-reduced-motion respected; the site uses essentially no motion in any case
• Text resizable through browser settings without loss of content or function

How far we have got. The site is built to the target above and we test it as we build. We have not yet commissioned an independent audit, so we describe this as the standard we are working to rather than a certified conformance claim. When an external assessment is completed we will publish its date, its findings, and any exceptions here.

Community engagement

Participation, not just the website

A website that meets AA is worth little if the meeting is upstairs with no lift. For any engagement we run, we commit to:

• Physically accessible meeting locations, with accessible parking and entry
• Materials available in large print on request
• Interpretation or translation where there is need in the community, arranged on request in advance
• A telephone route for anyone who would rather speak than write
• Paper submission accepted at every stage, logged identically to email
• Meeting times chosen so that people who work during the day can attend
• Notice given far enough ahead to arrange transport or care
• Summaries written in plain language rather than in the vocabulary of the application

Participation is never conditioned on having internet access, an email address, or a smartphone.

Feedback

Tell us where we have fallen short

If any part of this site or of an engagement we run creates a barrier for you, contactbernard@hostcommunitypartners.com and describe what happened. Include the page or the meeting and what you were trying to do.

We will acknowledge, tell you what we can fix and by when, and provide the information you were seeking in another format in the meantime. If something prevented you from taking part in a meeting, we will fix it before the next one.

Or telephone 404-862-5615 if you would rather speak than write.