Legal
Accessibility
This statement covers wmichaelhsu.co. We want this site usable by everyone, including people who browse with a keyboard, a screen reader, magnification, or reduced motion. Last reviewed .
The standard we aim for
We target WCAG 2.1 Level AA. That is the benchmark U.S. courts and the Department of Justice point to when they apply the Americans with Disabilities Act to websites, and it is the same bar as EN 301 549 in the EU. We treat it as a floor, not a finish line.
What is built in
Every page starts with a skip-to-content link. Headings run in order, so screen reader users can navigate by structure instead of reading top to bottom. Every form field has a real label, and errors are announced, not just colored. Interactive elements show a visible focus ring, and the whole site is operable by keyboard alone. Images that carry meaning have text alternatives; images that are pure decoration are hidden from assistive technology so they do not add noise. We honor your operating system setting for reduced motion. Body text meets or exceeds the AA contrast ratio, and text resizes to 200% without breaking the layout.
Known limitations
Being straight with you is more useful than a clean claim. As of the last review:
- Form field borders are a light hairline that does not yet meet the 3:1 contrast ratio WCAG asks for on the edges of a control. The fields are still clearly labeled and show a strong focus ring when selected. This is on the list to fix.
- Some embedded third-party content, such as video players and scheduling widgets, is outside our control. Where an embed blocks you, email us and we will get you the same information another way.
- Long-form articles have not each been individually checked for reading-order edge cases. If one reads out of order for you, tell us which one.
Tell us if something blocks you
If any part of this site is hard or impossible to use, email hi@xhack.co. Tell us the page, what you were trying to do, and what you browse with if you know it. We aim to reply within 5 business days, and we will give you the information or complete the task with you while we fix the underlying problem.
This is not a formality. A barrier you hit is a bug report we cannot generate on our own, and it is the fastest way this site gets better.
How we test
We test with keyboard-only navigation, automated checks in the build, and manual review against the WCAG 2.1 AA criteria. Automated tools catch roughly a third of real issues, so the manual pass is the one that counts.