Current position
Accessibility status
The site is designed toward WCAG 2.2 Level AA, but I do not present it as independently audited or formally certified. Browser, device and assistive-technology combinations can behave differently, so accessibility work remains ongoing.
The aim is straightforward: important content and actions should remain understandable, operable and visible without relying on a particular input method, colour alone or unnecessary animation.
Implemented
What the site currently supports
- Skip navigation: a skip link moves keyboard users directly to the main content.
- Semantic structure: pages use headings, landmarks, navigation labels and meaningful link text.
- Keyboard operation: primary navigation, forms and accessibility controls are keyboard operable.
- Visible focus: interactive elements receive a strong focus indicator, including a high-contrast treatment.
- Touch targets: principal controls are designed around at least 44px target sizing.
- Reduced motion: system-level reduced-motion preferences are respected and a manual reduced-motion option is available.
- High contrast: the accessibility control switches the current design system to a simplified black-and-white high-contrast palette with visible borders and focus states.
- Text scaling: the accessibility menu can increase or decrease the site's base text size.
- Optional OpenDyslexic typeface: users can switch to an alternative reading font if they personally find it easier to use.
- Consistent presentation: the portfolio now uses one stable visual theme across the site, reducing unnecessary display-state complexity.
- Mobile form sizing: form controls use a 16px minimum text size on narrow screens to avoid unwanted browser zoom behaviour.
- Forced-colours support: the current design includes fallback behaviour for operating-system high-contrast and forced-colour modes.
Design approach
Accessibility without a separate version of the site
The core site is intended to work with screen readers and other assistive technologies through standard HTML semantics. A separate “screen reader mode” is not required for accessible markup, so accessibility improvements are being focused on the underlying structure instead of presenting assistive technology users with a different version of the content.
Similarly, reading aids such as alternative fonts are offered as personal preferences rather than being described as universal accessibility solutions.
Known limitations
What still needs ongoing checking
- Visual contrast should continue to be checked whenever colours or components are changed.
- Responsive layouts should continue to be tested at browser zoom levels above 100%, not only at standard mobile and desktop widths.
- Keyboard focus order and mobile-menu behaviour should be rechecked whenever navigation is changed.
- Third-party services, including the contact-form submission service, may have behaviour outside this site's direct control.
- Assistive-technology behaviour can vary between browser and screen-reader combinations, so user feedback remains valuable.
Feedback
Report an accessibility problem
If something on the site is difficult to read, understand, navigate or operate, please contact me and include the page, device or browser involved if possible. Specific accessibility feedback will be used to improve the site.
Reference