Accessibility Statement

I want everyone to be able to read what I write here, whatever device, browser, or assistive technology they use. This statement sets out the standard I aim for, the steps I have taken to get there, the limitations I currently know about, and how to reach me if something gets in your way.

My commitment

I build and maintain troykelly.com myself, as an individual. Accessibility is something I care about and design for from the start, not something bolted on afterwards. My goal is a site that works well with keyboards, screen readers, magnification, and reduced-motion or high-contrast preferences, and that stays readable when text is resized or the layout is reflowed.

I cannot promise perfection — no site is ever finished, and I am one person — but I can promise that I treat accessibility barriers as defects worth fixing, and that I will keep improving the site over time.

The standard I aim for

I aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.2 AA is the widely accepted benchmark for accessible websites and covers content being perceivable, operable, understandable, and robust.

In Australia, the Disability Discrimination Act 1992 (Cth) makes it unlawful to discriminate against people with disability, and the Australian Human Rights Commission points to the WCAG standard as the practical benchmark for accessible online services. I use WCAG 2.2 AA as my target for that reason. This statement describes what I am working towards and how I am doing; it is not a claim of full conformance, nor an admission of non-compliance.

Measures taken

The following are built into how the site is made:

• Semantic HTML. Pages are structured with meaningful headings, lists, and landmark elements so that browsers and assistive technologies can present the content in a logical order and let you navigate by structure.
• Keyboard navigability. Interactive controls are reachable and operable with a keyboard, and I aim to keep a visible focus indicator so you can always see where you are.
• Colour and contrast. The site’s colours, type, and spacing come from a single set of design tokens that I tune for legible colour contrast, rather than being chosen ad hoc page by page.
• Self-hosted fonts, no third-party font service. All fonts are bundled and served from this site itself — there is no Google Fonts or other third-party font content delivery network. This keeps type rendering predictable and avoids a dependency that could delay or break text display.
• Readable, low-distraction pages. On my own pages the reading experience is deliberately simple: no pop-ups, no auto-playing audio, no advertising, and no tracking overlays getting between you and the words. (Embedded third-party players are a separate matter — see “Known limitations” below.)

Known limitations

I would rather be honest than make a blanket claim of conformance. Areas I am aware of and working on include:

• Site-wide “skip to content” link and a single main landmark. A consistent “skip to content” link and one clearly marked main landmark on every page are being rolled out and are not yet in place everywhere. Until that work lands, screen-reader and keyboard users may not have a uniform way to jump straight past the site navigation to the main content on every page.
• Embedded third-party media. Some articles embed video or audio from providers such as YouTube, Vimeo, or SoundCloud. Those embedded players are built and controlled by the provider, and their accessibility is outside my control. Where an embed is central to a post, I aim to describe its content in the surrounding text.

If you hit a barrier that is not listed here, please tell me — see below. Real reports from real people are the most useful thing I can get.

Date last reviewed

I last reviewed the accessibility of this site on 23 October 2026. I review it periodically and after significant changes, and I update this statement when the position changes.

Feedback and assistance

If any part of troykelly.com is difficult to use, if something does not work with your assistive technology, or if you need a page or its content in a different accessible format, please email me at troy@troykelly.com.

To help me fix the problem quickly, it helps if you can tell me the page address (URL), what you were trying to do, and the browser or assistive technology you were using — but please get in touch even if you cannot provide all of that.

I read every message myself and I will do my best to respond promptly, to help you get the information you were after, and to fix the underlying issue so the next person does not meet the same barrier.