Legal
Accessibility
I build accessibility into the tools I make for faculty and students, so this site owes the same thing. Here is the standard I hold it to, what I know is still short of it, and how to tell me.
The standard I build to
I build and check this site against the Web Content Accessibility Guidelines, version 2.1, Level AA. Where a 2.2 criterion was straightforward to meet, such as target size and the appearance of the focus indicator, I have met it as well.
That is a target and an ongoing effort rather than a certification. This site has not had a formal third-party audit, and I would rather say so here than imply one.
What is in place
- Text and interface colours are measured against their actual backgrounds on both the light pages and the dark sections, at 4.5 to 1 for body text and 3 to 1 for large text and control edges.
- Every control can be reached and operated from the keyboard, and the focus indicator is drawn on both the light and dark stages, including where a control sits on top of a photograph or a running application.
- A skip link is the first thing in the page and moves focus, not only the scroll position.
- Asking your browser or system for reduced motion collapses every animation, pin, scroll effect and generative canvas to a static equivalent, and replaces the header video with a still frame. Nothing is hidden behind an effect that never runs.
- The embedded applications sit in titled frames, and the keyboard can step past a frame rather than being caught inside it. Each one carries a visible link to open it in its own tab.
- Headings run in order, images carry alt text or are marked decorative, and the page renders complete with JavaScript switched off.
What I know is still short
These are the limitations I am aware of. The list is honest rather than flattering, and it is not a promise that it is exhaustive.
- The embedded applications are outside the accessibility of this site. They are mine, but they are separate applications on their own hosts, they are not audited as part of this page, and they can change when I deploy them. If one of them has a barrier, tell me and I will fix it in that application.
- Those frames do not load on narrower screens or when your browser asks for reduced data, and a screenshot stands in. The screenshot carries alt text, though a description of a tool is not the tool.
- The video behind the header is muted, decorative and has no captions, because it shows a workshop and carries no information the page does not also say in text.
- The generative canvases between sections are decorative, carry no content, and do not render at all under reduced motion.
- Screen reader testing has been done with VoiceOver on macOS. I have not tested with NVDA or JAWS.
- My resume is a PDF exported from Word, and I have not verified that it is tagged for a screen reader. If you need it in another format, ask me and I will send you one.
Telling me about a barrier
If something here blocked you, I want to know, and a short message is enough. Send me the address of the page, what you were trying to do and what got in the way, and the browser and any assistive technology you were using if you know them.
I will reply, and where I can fix it I will. If the fix is going to take a while and you came here for something specific, say what you needed and I will send it to you in a form you can use in the meantime.
This page is my own statement about this site. It is not legal advice, and it is not a conformance certification.