Our commitment
I aim to make this website usable by as many people as possible, including people who use assistive technologies, navigate by keyboard, use magnification or require reduced motion. This includes people who are disabled or neurodivergent, have temporary impairments, or use different devices and browsers.
I am continually improving the accessibility of this site and consider accessibility throughout content, design and development work. This includes using semantic HTML, clear language, accessible interaction patterns and testing with a combination of automated and manual methods.
If something does not work for you, or you need information in another format, please get in touch using the feedback and contact details.
Scope and third-party content
This statement covers the content and interface controlled by Ryan J. M. Laird on https://rjmlaird.co.uk, including public pages, articles, project pages, resources, contact routes and legal notices published within it. Separate websites, applications and subdomains may have their own accessibility statements.
It does not automatically cover:
- External websites.
- Third-party booking or payment services.
- Embedded media platforms.
- External documents.
- Linked applications.
- Other subdomains or separate digital products.
- Client, partner or publisher websites.
The booking portal at https://booking.rjmlaird.co.uk is a separate service and may have its own accessibility information. Those services may have their own statements and support arrangements. Where I control a linked subdomain or application, I will aim to publish a separate statement or clearly identify its accessibility status. If a third-party service is creating a barrier to accessing my work or making an enquiry, contact me and I will try to offer a suitable alternative route.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for improving the accessibility of web content. WCAG 2.2 defines three conformance levels: A, AA and AAA.
This website is partially conformant with WCAG 2.2 Level AA.
Partially conformant means that some parts of the website may not fully conform to the applicable accessibility standard. This status reflects the current state of testing and does not mean that every page or interaction has been assessed comprehensively.
I will update this statement when significant changes are made, when new testing identifies an issue or when known issues have been resolved. A conformance claim should reflect recent testing and should identify known limitations clearly.
Measures supporting accessibility
I take the following measures to support accessibility:
- Include accessibility requirements in planning, design and development.
- Use semantic HTML and meaningful document structure.
- Review accessibility during code review and content review.
- Test keyboard navigation and visible focus states.
- Test interactive components with assistive technologies where practical.
- Use automated testing to identify potential accessibility issues.
- Track known issues and improvements in the relevant project repository.
- Welcome accessibility feedback and use it to improve the site.
- Consider accessibility when selecting third-party services, embeds and media.
Accessibility is an ongoing responsibility rather than a one-time compliance exercise. Automated tools can identify some problems, but they cannot determine whether every interaction, explanation or piece of content works well for every person. I also aim to use clear language, explain specialist terms where useful and structure long content into manageable sections.
Accessibility features
The website is designed to include the following features where relevant:
- A skip link to bypass repeated navigation and move directly to the main content.
- Semantic HTML elements, including header, nav, main, section and footer.
- A logical heading hierarchy.
- Descriptive page titles and link text.
- Keyboard access to interactive elements.
- Visible focus indicators.
- Appropriate landmark regions for assistive technology navigation.
- Responsive layouts for different screen sizes and orientations.
- Support for user preferences such as reduced motion where applicable.
- Text alternatives for informative images.
- Decorative images marked so they are not unnecessarily announced.
- Accessible labels and descriptions for form controls.
- Clear identification of form errors and required fields.
- Appropriate language attributes to support pronunciation.
- Accessible colour contrast for text and essential interface elements.
- Content that remains usable when text is enlarged.
- Accessible handling of menus, disclosures, tabs and other interactive components where present.
- Screen-reader labels for controls whose purpose is not clear from visible text.
- Links to transcripts, captions or alternative formats where those are available.
Not every feature is present on every page. Some content may depend on third-party services or embedded technologies whose accessibility I cannot fully control.
Keyboard and assistive technology support
The website is intended to support keyboard-only navigation without requiring a mouse or other pointing device, and to work with current mainstream browsers and assistive technologies such as screen readers, screen magnifiers, browser zoom, reading tools and voice-control software.
Where interactive components are used, I aim to provide:
- Logical focus order.
- Visible focus styles.
- Keyboard-operable controls.
- Appropriate names, roles and states.
- Sensible focus management when menus, dialogs or other temporary interfaces open and close.
- Escape-key support where it is appropriate for dismissible interfaces.
Support may vary according to the browser, operating system, assistive technology and device being used. The website does not require JavaScript for basic page reading and navigation wherever that can reasonably be avoided, although some enhanced interactions may depend on JavaScript.
If you experience a problem with a particular browser, device or assistive technology, please include those details when reporting it. This makes the problem easier to reproduce.
Known limitations
I am aware that accessibility can vary across pages, content types and third-party services. Where a barrier is known, I aim to describe it, explain the impact and provide an alternative where possible. If you encounter a barrier that is not listed here, please contact me so that I can investigate it.
| Area | Potential limitation | Alternative or support | Planned action |
|---|---|---|---|
| Older content | Some older articles, images, embedded media or archived project pages may not have complete or sufficiently descriptive alternative text, or meet the same standard as newer content. | Contact me to request a plain-text summary, an image description or specific information from the page. | Review significant archived content when it is updated, promoted or requested. |
| Diagrams, charts and maps | Project and research material may include complex diagrams, charts, maps, astronomy imagery or technical terminology that is difficult to represent in a short text alternative. | Request a written explanation, data table, longer description or alternative format. | Add explanatory text, captions, summaries and data alternatives where practical and useful. |
| Audio and video | Some media may not yet have captions, transcripts or equivalent text alternatives. | Request a transcript, summary or alternative route to the information. | Add captions and transcripts to frequently used media as it is published or updated. |
| Third-party services | Booking, payment, video, social-media, map, form or newsletter tools are controlled by third parties and may not meet the same accessibility standard. | Contact me for another way to enquire, book, receive information or complete the task. | Prefer accessible providers where practical and review embedded tools when alternatives exist. |
| Documents and downloads | Some documents, downloadable files or externally hosted resources, particularly older PDFs, slides and spreadsheets, may not be fully accessible. | Request the information in HTML, plain text, an accessible document format or another reasonable format. | Review frequently used downloads and provide accessible alternatives where practical. |
| Experimental tools and lab projects | Experimental tools, apps or lab projects may be under development and may have known interaction or compatibility limitations. | Contact me for the underlying information or results in another format. | Record known issues and fix them according to impact and technical feasibility. |
| Assistive technology coverage | Some pages may not yet have been manually tested with every major screen reader and browser combination. | Report the problem, including your browser, device and assistive technology, and I will work with you to find another route. | Extend manual testing across the combinations listed in the assessment approach. |
Known issues may also be recorded in the relevant public project repository, where that is appropriate and does not expose private or security-sensitive information.
Content and formats
If you cannot access something on this website because of its format, content, design or technical implementation, you can ask for help or an alternative version. Depending on the material, I may be able to provide:
- A plain-text or HTML version of information.
- A text-only summary of a page, article, image, diagram or chart.
- A larger-print, higher-contrast or simplified version of content.
- A structured text version of a downloadable document.
- A data table or written explanation for a chart or visualisation.
- A transcript, summary or alternative route for audio or video content.
- An alternative way to make an enquiry, arrange a conversation or access a service.
Please describe what you are trying to access and the format that would be most useful. This helps me respond more effectively.
Feedback and contact
I welcome feedback about the accessibility of this website.
Please contact me if:
- You cannot access information or functionality.
- A page is difficult to navigate using a keyboard or assistive technology.
- An image, video, document or chart does not have a suitable alternative.
- A form produces an unclear or inaccessible error.
- You need information in an alternative format.
- You have a suggestion for improving accessibility.
How to contact me
Ryan J. M. Laird
contact@mail.rjmlaird.co.uk
Other ways to give feedback: - Email accessibility feedback — report an accessibility barrier or request content in another format.
- GitHub accessibility issues — report a reproducible accessibility issue.
- Contact form — describe the barrier you encountered or request an alternative format.
What to include
When reporting a problem, it is helpful to include:
- The page URL.
- A description of the barrier.
- The device, browser or assistive technology being used, if known.
- Any steps needed to reproduce the problem.
- The format or support that would help you access the information.
Response time
I will acknowledge accessibility feedback within 2 business days where possible and will aim to provide an initial response or practical alternative within 10 business days.
Some requests may take longer where the content is complex, supplied by a third party, requires specialist conversion or needs to be recreated. If so, I will explain the next step and expected timescale.
Technical information
The accessibility of this website relies on the following technologies:
- HTML.
- CSS.
- JavaScript, where needed for enhanced interactions.
- WAI-ARIA, used only where native HTML does not provide the required semantics.
- SVG, images, audio, video and other media formats where used.
- Modern web browsers and assistive technologies.
The site is built with Astro. The technology used to generate a page does not itself guarantee accessibility; the accessibility of the resulting content and interface is what matters.
WCAG conformance depends on using technologies in an accessibility-supported way, and on making information or functionality available through an accessible method where a particular technology is not accessible.
Assessment approach
I assess accessibility through a combination of:
- Self-evaluation by the site maintainer.
- Automated testing with tools such as axe, Lighthouse and WAVE.
- Keyboard-only navigation.
- Browser zoom and text enlargement checks.
- Responsive testing across different viewport sizes.
- Manual inspection of headings, landmarks, labels, links and focus order.
- Screen-reader testing with tools such as VoiceOver, NVDA or other available assistive technologies.
- Review of colour contrast and non-text contrast.
- Testing of forms, menus, dialogs, tabs and other interactive components.
- Community feedback and accessibility audits where available.
Automated testing is used as an aid rather than as proof of full accessibility. W3C recommends that an accessibility statement include practical information about known limitations, testing environments and the ways accessibility has been assessed.
- Assessed by: Self-assessment by Ryan J. M. Laird
- Last tested: 2026-10-14
- Tested combinations: - Safari on macOS with VoiceOver
- Firefox on macOS with keyboard-only navigation
- Chrome on macOS with keyboard-only navigation
Escalating a concern
This is an independent professional website and is not presented as a public-sector website or mobile application for the purposes of the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
If you have raised an accessibility concern and do not believe it has been addressed appropriately, please contact me again with the details and the support you need. I will review the matter and try to find a reasonable solution.
You may also wish to seek independent advice about your rights under applicable equality, consumer, education or other relevant law. This statement does not limit any rights you may have under law.
Changes to this statement
I may update this statement when:
-
The website or its technology changes.
-
New accessibility testing is completed.
-
A known limitation is resolved.
-
A significant new feature or content type is published.
-
Feedback identifies a material accessibility issue.
-
Statement created: 14 October 2026
-
Last reviewed: 14 October 2026
-
Next review: 14 October 2027