Our Commitment to
Digital Accessibility.
The web should be usable by everyone. That is not a nice to have. It is a baseline requirement. Here is exactly what we do to make sure our website works for people of all abilities.
Why This Matters to Us
We build websites for a living. We optimize content for search engines, AI assistants, and human readers. But none of that matters if the content is not accessible to people who use the web differently than we do.
Roughly 15% of the world's population lives with some form of disability. That is over a billion people. Some use screen readers. Some navigate with just a keyboard. Some need high contrast or larger text. Some process information differently and benefit from clear structure and plain language.
When we build outline.ad, we think about all of these people. Not because the law requires it (although in many jurisdictions it does), but because building an inaccessible website in 2026 is like building a shop with no door. Technically functional for some, completely useless for others.
We make websites for a living. If we built one that a significant chunk of people could not use, that would be professionally embarrassing and morally questionable. So we do not do that.
The Standards We Follow
Outline Technologies strives to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These are the international standards that define how to make web content accessible. Level AA is the standard most governments and organizations recognize as the benchmark for accessibility compliance.
WCAG is built on four principles. All web content should be:
WCAG is basically a checklist that says: can people see it, use it, understand it, and will it keep working in the future? If yes to all four, you are doing it right.
What We Actively Do
Accessibility is not a box we check once and forget. It is a set of practices baked into every page we build. Here is the specific list of measures we implement:
3.1 Semantic HTML
We use proper HTML elements for their intended purpose. Headings are actual heading tags in correct hierarchical order. Navigation uses nav elements. Lists use list elements. Buttons are buttons and links are links. This sounds obvious but a shocking number of websites use div and span for everything, which makes them invisible to screen readers.
3.2 Keyboard Navigation
Every interactive element on our website is accessible via keyboard. You can tab through navigation, activate buttons with Enter or Space, close modals with Escape, and navigate the entire site without ever touching a mouse. We test this manually because automated tools often miss keyboard traps that real users encounter.
3.3 Color Contrast
All text on our website meets the WCAG AA minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text. Our primary text uses light colors on our dark background with contrast ratios well above the minimum. We specifically test our red brand color against dark backgrounds to ensure it meets requirements, and use lighter variants where contrast would otherwise be insufficient.
3.4 Text Alternatives
Every non decorative image has meaningful alt text that describes the content and function of the image, not just its appearance. Decorative images are marked with empty alt attributes so screen readers skip them. Icons that convey meaning have ARIA labels. Data visualizations include text descriptions of the data they represent.
3.5 Focus Indicators
When you tab through our website, every focused element has a visible focus indicator. We do not use outline:none without providing an alternative focus style. Our focus indicators are designed to be visible against both light and dark backgrounds and meet minimum size requirements.
3.6 Form Accessibility
All form fields have associated labels that describe what the field is for. Error messages are specific and helpful, explaining what went wrong and how to fix it. Required fields are marked clearly. We do not rely solely on color to indicate errors. Form validation provides real time feedback using ARIA live regions so screen reader users are informed of changes.
3.7 Responsive and Flexible Design
Our website works across all screen sizes and devices. Content reflows at larger text sizes without requiring horizontal scrolling. Users can zoom to 200% without losing content or functionality. We support both portrait and landscape orientations without content being cut off.
3.8 Motion and Animation
We use subtle animations to enhance the user experience, but we respect the prefers-reduced-motion media query. Users who have indicated they prefer reduced motion in their system settings will see a version of our site with minimal or no animation. We never use flashing content that could trigger photosensitive seizures.
3.9 ARIA Implementation
We use ARIA (Accessible Rich Internet Applications) attributes where native HTML semantics are insufficient. This includes ARIA labels for icon-only buttons, ARIA expanded states for collapsible sections, ARIA live regions for dynamic content updates, and ARIA landmark roles to help screen reader users navigate the page structure efficiently.
We do the boring structural work that most people never see but that makes the difference between a website that works for everyone and a website that works for some people and frustrates everyone else.
How We Test
Accessibility is only as good as the testing behind it. We use a multi layered approach:
We do not just run one automated scan and call it a day. We actually tab through the site, listen to it with a screen reader, and check that nothing is broken. It takes longer. It is worth it.
Known Limitations
We strive for full WCAG AA compliance but we are transparent about areas where we are still improving:
- Some third party embedded content (such as external widgets or integrations) may not fully meet our accessibility standards. We work with vendors to improve compliance where possible.
- Our 3D canvas animation on the homepage may not be accessible to all users. It is purely decorative and does not convey content. The site is fully functional without it.
- Older blog content may have accessibility gaps that we are gradually updating.
We are not perfect. A few things are still being worked on. We would rather be honest about the gaps than pretend they do not exist.
Our Ongoing Commitment
Accessibility is not a project with a start and end date. It is an ongoing commitment. Here is what we do to maintain and improve accessibility over time:
- Every new page and component goes through accessibility review before it ships.
- We run automated accessibility audits as part of our development process.
- We stay current with updates to WCAG guidelines and emerging best practices.
- We prioritize accessibility bug fixes alongside performance and security fixes.
- We invest in learning: our team regularly studies accessibility research and participates in the accessibility community.
We treat accessibility the same way we treat security and performance: as something that is never done and always needs attention.
Feedback and Contact
We genuinely want to hear from you if you encounter any accessibility barriers on our website. Whether it is a screen reader announcing something incorrectly, a button that cannot be reached by keyboard, text that is too small, or any other issue that prevents you from using our site effectively.
Here is how to reach us:
Accessibility Feedback
Email: [email protected]
Subject line: Accessibility Feedback
Response time: within 2 business days
When reporting an issue, it helps us if you can include: the page URL, a description of what happened, what device and browser you were using, and what assistive technology you were using (if any). But do not worry about formatting a perfect bug report. Any feedback is helpful.
If something on our site does not work for you, please tell us. We will not get defensive. We will fix it. That is literally the point of this page.
This accessibility statement was last reviewed and updated on April 1, 2026.
We review this statement quarterly to ensure it accurately reflects our current practices.
Found an Accessibility Issue?
We take every report seriously. Tell us what is not working and we will prioritize the fix.
Report an Issue