Accessibility statement
Last reviewed October 31, 2026.
Adam Ginsberg wants everyone to be able to use adamjayginsberg.com, including people who use a screen reader, a keyboard instead of a mouse, voice control, screen magnification or captions.
This statement covers adamjayginsberg.com and its project pages.
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C.
Where we are today
adamjayginsberg.com partially conforms to WCAG 2.2 Level AA. That means most of it meets the standard and some parts don't yet. The gaps we know about:
- The contact section embeds a Google Map. Its controls come from Google and may not fully meet the standard.
- The contact form doesn't send from the page. It opens your own email app with your message filled in, so you can also email the address below directly.
- The header line types and retypes itself in a loop, and sections fade in as you scroll. Both stop when your device asks for reduced motion, but the typing loop has no pause button yet.
- We have not yet finished a full manual review with every major screen reader, so some problems may remain.
What we do about it
- We run automated WCAG 2.2 AA checks on our pages and fix what they find.
- We check new features with a keyboard and a screen reader before we release them.
- We fix problems in the code itself. We don't use accessibility overlay widgets.
Tell us about a problem
If something on adamjayginsberg.com doesn't work for you, email adamjgins@gmail.com. Tell us the page or screen and what went wrong. We reply within 5 business days. While we fix it, we'll help you get the information or finish the task another way.
Technical details
adamjayginsberg.com uses HTML, CSS and JavaScript and is built to work with current versions of the major browsers and screen readers (VoiceOver, NVDA, JAWS, TalkBack).