- Home
- Accessibility Statement
Accessibility Statement
We want this website to be usable by everyone, including people who browse with a keyboard, a screen reader, magnification or reduced motion enabled.
Last updated: September 1, 2026 · Effective date: September 1, 2026
This document applies to orlandoseocompany.net and to services provided by Orlando SEO Company. If you have questions about anything here, contact [email protected] — we would rather explain it than have you guess.
Our commitment
Orlando SEO Company is committed to making orlandoseocompany.net accessible to the widest possible audience, regardless of ability or technology. We treat accessibility as part of doing the work properly, not as a compliance afterthought — and because accessible markup and search-friendly markup overlap substantially, it is also good SEO.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We consider this website substantially conformant, with the known exceptions listed below.
Measures we have taken
- Semantic structure: proper landmark regions, a single descriptive H1 per page, and a heading hierarchy that matches the visual outline.
- Keyboard access: every interactive control — navigation, accordions, tabs, sliders, forms, the mobile drawer — is reachable and operable with a keyboard, with a visible focus indicator.
- Skip link: a “Skip to main content” link is the first focusable element on every page.
- Colour contrast: body text, headings and interactive elements are tested to meet or exceed the 4.5:1 (normal text) and 3:1 (large text and UI components) ratios.
- Text alternatives: meaningful images have descriptive alt text; decorative graphics and icons are hidden from assistive technology.
- Forms: every field has a programmatically associated label, required fields are marked in text as well as colour, and validation errors are announced, described in words and linked to the field concerned.
- Reduced motion: animations, parallax effects and auto-advancing carousels are disabled when your system requests reduced motion.
- Resizable text: layouts use relative units and remain usable at 200% zoom without horizontal scrolling at standard widths.
- Responsive design: content reflows to a single column on small screens with adequate tap target sizes.
- No motion or sound traps: nothing autoplays with sound, and no content flashes more than three times per second.
How we test
Accessibility is checked at three points: during development, before publishing a new template, and in a quarterly review of the live site.
- Automated: axe DevTools and WAVE across representative page templates.
- Manual keyboard testing: every page traversed by keyboard alone, confirming focus order, visible focus and no keyboard traps.
- Screen reader spot checks: VoiceOver on macOS and iOS, NVDA on Windows.
- Zoom and reflow: tested at 200% and 400% zoom and at 320 CSS pixels width.
- Preference testing: reduced motion, increased contrast and dark mode system settings.
Automated tools catch perhaps a third of real accessibility problems, which is why manual testing is part of the process rather than an optional extra.
Known limitations
We prefer to publish these rather than claim perfection:
- Case study graphs. The Search Console screenshots in our case studies are images of data. We describe the key figures in adjacent text and KPI blocks so the information is available without viewing the image, but the graphs themselves are not fully described.
- Third-party libraries. The slider and lightbox components we use are keyboard operable but their ARIA implementation is not entirely under our control. We review updates as they are released.
- Older articles. Some earlier content may contain tables or lists that are less cleanly structured than our current standard. We fix these as we revise each page.
- PDF downloads. Where we provide a PDF, it may not be fully tagged for accessibility. Ask us and we will provide the content in HTML or another accessible format.
Compatibility
This website is designed to work with recent versions of Chrome, Edge, Firefox and Safari on Windows, macOS, iOS and Android, in combination with current assistive technologies. Functionality may be reduced in browsers more than three major versions old, or where JavaScript is disabled — in that case content and navigation remain available, but interactive features such as filtering and accordions will not operate.
Feedback and reporting a barrier
If you encounter a barrier on this website, please tell us. Describe the page, what you were trying to do, and the browser and assistive technology you were using if you know it.
Email: [email protected]
Telephone: (929)-566-4655
Post: 121 S Orange Ave, Suite 1500, Orlando, FL 32801
We aim to acknowledge accessibility reports within 2 business days and to respond with a fix or a timeline within 10 business days. If a fix will take longer, we will offer the information or service in an alternative format in the meantime.
Formal approach and review
This statement was prepared on September 1, 2026 following internal review against WCAG 2.2 Level AA. It is reviewed at least annually, and whenever we launch a significant new template or feature. We have not yet commissioned a third-party accessibility audit; when we do, we will publish the summary findings here.
Need something clarified?
We are happy to explain any part of this document in plain language, or to provide it in an alternative format on request.