Accessibility
I want everyone to be able to use this site. Here is what I did, what I have not checked, and how to tell me about a problem.
Last updated 16 October 2026.
What I aim for
I build to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. That is the standard most laws and buyers ask for.
What is in place
- You can use every page with a keyboard alone. A skip link jumps past the menu to the main content.
- Where your keyboard is on a page, the link or button changes: it gets an underline or a heavier border. Nothing relies on colour alone.
- Text and buttons have enough contrast against their background. I check the colours by their numbers, not by eye.
- Headings are in order, so a screen reader can jump from section to section.
- Images that carry meaning have a text description. Pictures that only decorate are hidden from screen readers.
- Pages work from a 320 pixel wide phone up to a wide desktop, and when you zoom the text.
- If your device is set to reduce motion, the animations stay off and the page shows its final state.
What I have not done
I check every page with automated tests and by keyboard. An outside accessibility audit has not been done yet. Some company logos are pictures supplied by others, and I describe them only by company name. My resume is a separate page on Notion, which I do not control, so it may not meet the same standard. If it gets in your way, email hello@ayoosota.com and I will send you the details another way.
Tell me about a problem
If something on this site is hard to use, email hello@ayoosota.com. Say which page, what you were trying to do, and the device or tool you use if you are happy to share it. I aim to reply within 5 business days and to fix real problems quickly.