Perceivable information
Text, structure, images, colour and media should communicate meaning in more than one visual form wherever practical.
Access belongs in the design
Accessibility Statement
Andrew Barnes aims to make the English andrewbarnes.org website usable by as many people as reasonably possible, including people who use assistive technologies.
Accessibility is an ongoing responsibility across content, navigation, forms, booking journeys, Shop functions and connected third-party services.
The starting point
Accessibility Statement in plain language.
Accessibility means being able to find information, understand it, navigate the interface and complete the task without avoidable barriers.
The aim is not merely to pass an automated scan. Accessibility also depends on clear language, predictable interaction, real keyboard use, assistive-technology testing and a workable response when someone encounters a barrier.
Core commitments
Clarity before complexity.
The target is the Web Content Accessibility Guidelines 2.2 at Level AA. The practical work combines semantic code, visual design, keyboard and assistive-technology testing, and correction when real barriers are found.
Keyboard access
Navigation, controls, forms and disclosures should remain usable without requiring a mouse or precise pointer movement.
Readable presentation
Content should reflow, preserve contrast and remain understandable when text is enlarged or viewed on a smaller screen.
Clear interaction
Labels, instructions, focus states and error messages should make forms and choices easier to understand and correct.
Motion with restraint
Animation should not be essential to understanding, and reduced-motion preferences should be respected where motion is used.
Ongoing review
Accessibility is maintained through automated checks, manual testing, real feedback and correction as the website changes.
Complete details
What this means in practice.
Open each section for the full wording. The shorter summary is there to help you find the part that matters without reading every clause first.
01Navigation and keyboard useThe structure should remain understandable and operable without a mouse.
Pages use headings, landmarks, skip links, descriptive link text and consistent navigation so people can move through the site with a keyboard or assistive technology. Interactive controls should show a visible focus state and follow a logical reading and tab order.
Menus, disclosures, forms, buttons and links are intended to work with standard keyboard commands. A control that requires dragging, hovering or a precise gesture should also provide a practical alternative.
02Text, colour, zoom and responsive layoutContent should remain readable across screen sizes and common enlargement settings.
The visual system uses high-contrast text, restrained colour, flexible spacing and responsive layouts. Meaning should not depend on colour alone, and text should reflow without forcing two-directional scrolling at common mobile and zoom settings.
Browser zoom, text enlargement, high-contrast preferences and custom display settings can produce different results. If a section overlaps, disappears or becomes unreadable, report the page and the settings in use so the barrier can be reproduced.
03Images, diagrams, audio and videoMeaningful non-text content should have an equivalent description or alternative.
Informative images are intended to have useful alternative text. Decorative images should be ignored by screen readers. Complex anatomy charts, relationship maps and teaching diagrams may require a longer text explanation because a short label cannot carry their full educational meaning.
New recorded media should include captions, transcripts or another suitable alternative where speech or sound carries meaning. Legacy or third-party media is reviewed progressively, and an alternative can be requested when it is not yet available.
04Forms, errors and transactional journeysEnquiries, registration, checkout and account tasks should explain what is required.
Form fields should have programmatic labels, understandable instructions and errors that identify both the problem and how to correct it. Required agreement, privacy and consent choices should not rely on preselected options or colour alone.
Booking, payment, Shop and practitioner-account journeys may move between the website and connected Wix or payment services. These higher-risk journeys are included in launch testing, with an alternative contact route available if a third-party control prevents completion.
05Motion, timing and cognitive accessibilityThe site should not demand speed, memory or tolerance of unnecessary motion.
Decorative movement should respect reduced-motion settings and should not block access to content. Essential tasks should avoid unnecessary time limits, unexpected context changes and instructions that depend only on remembering information from an earlier step.
Plain headings, short summaries, progressive disclosure and consistent page patterns are used to make long or sensitive material easier to navigate without stripping away necessary nuance.
06Third-party content and current review areasSome connected services are not fully controlled by Andrew, but barriers still matter.
Wix booking and commerce interfaces, payment pages, embedded media, downloadable documents and other external services may not always match the accessibility of the main website. Andrew cannot change every third-party interface directly, but can raise issues, provide a reasonable alternative or reconsider a provider where a serious barrier persists.
Current whole-site review includes keyboard operation, visible focus, screen-reader names and announcements, form errors, colour contrast, 200% and 400% zoom, reduced motion, touch targets, mobile overflow, Safari, iPhone and other current browsers. Confirmed barriers will be prioritised according to their effect on access.
07Requesting help or an alternative formatTell us what you were trying to do, and we will work from the practical barrier.
You do not need to identify a diagnosis or quote an accessibility standard. It is useful to include the page address, the task you were trying to complete, what happened, and your browser, device or assistive technology if you are comfortable sharing that information.
You may ask for content in another reasonably available format or for help completing a website task. Requests are considered in good faith, with privacy, urgency, the nature of the material and the practical effort required taken into account.
How this fits together
A target, a test, and an honest status.
The website’s target is WCAG 2.2 Level AA. This statement records a continuing commitment and testing standard; it is not a claim that every page and every connected third-party service has passed a formal conformance audit.
The main English site is being reviewed across desktop and mobile, keyboard and screen-reader use, zoom, contrast, forms, reduced motion and transactional journeys. New content and features should be checked before release and rechecked after substantial changes.
Third-party booking, payment, media and document interfaces remain part of the visitor’s real journey even when their code sits outside Andrew’s direct control. Where a barrier cannot be corrected promptly, a reasonable alternative route should be offered.
Contact and support
You can ask in ordinary language.
If something is difficult to see, hear, understand or operate, tell us what page you were using and what you were trying to do. You can also request a reasonably available alternative format. Accessibility feedback is read as a practical request for improvement, not as a complaint about the person reporting it.