accessibility statement
Accessibility statement
This site targets WCAG 2.2 Level AA. What that means in practice, what has been tested, what has not, and how to tell us if you hit a problem.
Published because a site that talks about doing technical work properly should be able to show its own.
What has been built in
- Semantic structure. Real landmarks, one H1 per page, headings nested without skipped levels, and lists marked up as lists.
- Keyboard access. Every interactive element is reachable and operable by keyboard, with a visible focus ring — a 3px outline with 2px offset, applied consistently and never removed.
- Skip link. The first focusable element on every page jumps to the main content.
- Contrast. All body text meets or exceeds 4.5:1 against its background; large text exceeds 3:1. Ratios are recorded in the design documentation rather than assumed.
- Reduced motion. Everything that animates is disabled under
prefers-reduced-motion. No content depends on motion to be understood. - Reflow. The site works down to 320px with no horizontal scrolling. Wide tables scroll inside their own focusable container rather than forcing the page sideways.
- Text resizing. Text scales to 200% without loss of content or function, because the layout is built in relative units.
- Alt text. Images describe function. Purely decorative elements are hidden from assistive technology rather than given filler descriptions.
Known limitations
Stated rather than omitted, because an accessibility statement that claims perfection is not credible.
- Comparison tables. Several pages carry tables wider than a phone screen. They scroll horizontally inside a focusable region with an accessible name, which is the standard approach, but reading a wide table on a small screen remains harder than reading prose.
- Automated testing only, so far. The site has been checked with automated tooling and manual keyboard testing. It has not yet been tested with a screen reader by someone who uses one daily. That is a real gap and it is worth more than any automated pass.
- The sticky contact bar. On mobile, a contact bar appears after scrolling. It is dismissible and respects safe-area insets, but it does occupy screen space until dismissed.
Testing approach
Automated checks run against the built output. Manual keyboard navigation is checked on every interactive component: the mobile menu, the FAQ disclosures, the table scroll regions and every link and button.
Colors were selected against contrast requirements during design rather than corrected afterwards — the pass-state green was darkened specifically to clear 4.5:1 for body text.
Reporting a problem
If something on this site does not work for you, email the address in the footer. Include the page, what you were trying to do, and what browser or assistive technology you were using if you know it.
Accessibility reports get answered in the same window as everything else, and they get fixed rather than logged. If you cannot use email, message on WhatsApp instead.
Standard and scope
This statement covers seomigrationservices.us and every page on it. The target is WCAG 2.2 Level AA.
It was last reviewed on the date shown below. It is reviewed whenever a new page type or interactive component ships, rather than on a fixed schedule that would drift out of step with the site.