Accessibility Statement

This site is dedicated to providing an accessible experience that is perceivable, operable, understandable, and robust to all users.

To do this, it aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at a AAA level. WCAG defines the minimum requirements for designers and developers to improve accessibility for people with disabilities.

Feedback

I welcome your feedback on the accessibility of this site. Please let me know if you encounter accessibility barriers via:

• Email
• GitHub issues

I aim to respond to feedback within 2 business days.

Compatibility with browsers and assistive technology

This site is designed to be compatible with the greatest range of assistive technologies. The following environments are tested as part of the development process:

• Safari + VoiceOver (macOS)
• Safari + VoiceOver (iOS)
• Chrome + VoiceOver (macOS)
• Windows + NVDA
• Safari + Voice Control (macOS)

Technical specifications

The accessibility of this site relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• WAI-ARIA
• CSS

These technologies are relied upon for conformance with the accessibility standards used.

Limitations and alternatives

Despite my best efforts to ensure accessibility of this site, there may be some limitations. The following is a description of known limitations and potential solutions:

• Profile logos in YouTube video embeds do not have a role. There is no known solution. Waiting for the third-party to resolve this issue.

Assessment approach

I assess the accessibility of this site through the following approaches:

• Self-evaluation using manual testing and assistive technology
• Automated accessibility audits (e.g. Axe, Lighthouse)
• Feedback from users with disabilities
• Conformance checks against WCAG 2.2 AAA

This statement was last updated on April 17, 2025.