Accessibility

Built to be readable by everyone

Accessibility is treated as an engineering requirement here, in the same way it is on client platforms.

Standard

This site targets WCAG 2.2 Level AA. Content is server-rendered as semantic HTML so it works without JavaScript, with assistive technology, and for search and AI crawlers alike.

Measures in place

A single H1 per page with an ordered heading hierarchy; landmark elements for header, navigation, main and footer; visible keyboard focus; text contrast that meets AA against the surface it sits on; form fields with associated labels and error messages announced to screen readers; and no motion that cannot be ignored.

Known limitations

Architecture diagrams are currently text-based rather than annotated visuals. Third-party scheduling embeds are not yet in place; when added, they will be reviewed for keyboard and screen-reader support before publication.

Reporting a barrier

If any part of this site is difficult to use, email diasjordan@gmail.com with the page and what happened. Reports are read personally and fixed as a priority, and I will supply the content in another format in the meantime.