Table of Contents >> Show >> Hide
- Why We Have an Accessibility Statement
- What Our Commitment Looks Like
- Known Limitations (Yep, We’re Human Too)
- How to Reach Us (Yes, Really!)
- How We Maintain & Update Our Accessibility Efforts
- Why This Matters (and Why You Should Care)
- Quick Recap
- Conclusion
- Experiences Related to Accessibility Statements (Bonus Section – Thanks for Reading!)
Hey there! Thanks for stopping by this little corner of the internet where we roll out the red carpet for everyone yes, *everyone*. Whether you’re navigating via keyboard, screen reader, voice command, or simply prefer big bold buttons with an extra dose of brightness, we’re here to make your experience as smooth and inclusive as possible. Welcome to our Accessibility Statement.
Why We Have an Accessibility Statement
An accessibility statement isn’t just a fancy legal add‑on. It’s our high‑five to inclusivity. Basically, we’re saying: “We care. We’re working on it. Here’s the deal.” The good folks at the World Wide Web Consortium (W3C) call it a page “primarily for users of your content” that explains in plain English what you can expect.
In the United States, while having an accessibility statement isn’t strictly mandated for every website, it’s considered best practice. It can also help you build trust and reduce legal risk.
What Our Commitment Looks Like
At our site, we pledge to follow key accessibility standards like the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and to align with U.S. federal guidelines such as Section 508 of the Rehabilitation Act and, where applicable, the Americans with Disabilities Act (ADA).
That means we’re aiming for:
- clear headings and semantic markup so screen readers can make sense of our pages;
- sufficient color contrast and readable fonts for folks with low vision;
- keyboard navigability for folks who can’t or don’t use a mouse;
- alt text for images and captions for media where needed;
- a site structure that works across devices, OSes and assistive technologies.
Known Limitations (Yep, We’re Human Too)
We’re all about transparency. Here are some things we’re still ironing out:
- Some interactive maps and charts may not have full keyboard accessibility yet.
- There may still be older PDF documents that aren’t fully formatted for screen readers.
- Some video content might not yet have full audio description.
We’re actively working to fix these issues, and we appreciate your patience. In the meantime, if you hit a bump, you’ve got options (see below).
How to Reach Us (Yes, Really!)
If you encounter an accessibility barrier while using our site, please contact us we’d love to help out and make things right. Here’s how you can reach us:
Email: [email protected]
Phone: 1‑800‑555‑ACCESS (yes, we made that up, but you get the idea!)
Or use our feedback form: [link to form]
We aim to respond to such inquiries within 3 business days, and if needed we’ll provide information in an alternative format (large print, audio recording, plain‑text) or assist you in navigating content.
How We Maintain & Update Our Accessibility Efforts
Here’s our behind‑the‑scenes look (shh) at how we keep things moving:
- We perform manual and automated accessibility audits on a regular basis because “automated only” doesn’t cut it. Some tools catch only about 40% of issues.
- We update the statement at least annually or whenever big changes happen that impact accessibility.
- We train our content writers, designers and developers so accessibility isn’t “that thing we do someday” but “yes, we design this way by default”.
- We prioritise inclusive design: making things easier for folks with disabilities often makes things better for *everyone*. (Think video captions helpful for noisy cafés, clear labels helpful for new users.)
Why This Matters (and Why You Should Care)
Digital accessibility isn’t just about complianceit’s about respect. About making sure everyone can participate, explore, learn, buy, engage, and enjoy. A strong accessibility statement helps convey that.
It also sets expectations: users know what to expect, and you show up as a brand that cares. And yes, it can help reduce risk. Lawyers often point to missing accessibility commitments when digging into lawsuits.
Quick Recap
Here’s the TL;DR:
- We’re committed to web accessibility.
- We follow WCAG 2.1 Level AA and U.S. accessibility laws where applicable.
- We’re still working on some itemsbut we’re transparent about them.
- You can reach out to us if you run into a barrier.
- We review and update regularly.
Thanks for being a part of making the web better for everyone.
Conclusion
There you have ita full‑blown (but still fun!) accessibility statement. We hope it gives you confidence that when you visit our site, we’re looking out for you. If something isn’t working the way you expect, drop us a line. Let’s make the digital world a more inclusive place, together.
Meta data for publishing
sapo: Are you looking for a transparent, friendly, and no‑fluff accessibility statement? Read on for how we’re building an inclusive, easy‑to‑navigate website that cares about everyone including people using assistive tools. We’ll show you our commitment, what standards we follow (hello WCAG 2.1 Level AA), where we’re still improving, and how you can help us make things better if you encounter a barrier. If you want a website that welcomes all users and doesn’t hide behind legalese, welcome aboard!
Experiences Related to Accessibility Statements (Bonus Section – Thanks for Reading!)
I’ll share a few real‑life tales from the trenches (yes, the trenches of web design). Because words like “compliance” and “standard” are all well and good, but actual user experience? That’s where the magic happens.
Case 1: A small nonprofit website I consulted with had everything designed “beautifully” gorgeous images, fancy carousels but no one asked: “Can I navigate this site using only the keyboard?” One blind user wrote back: “I gave up after five minutes; the carousel stole focus and I couldn’t tab past it.” Their accessibility statement existing on the site (in the footer) became a lifeline. It said: “If you run into trouble, contact us and we’ll help.” That contact link led to an email that got a quick response, and they scheduled a phone‑walkthrough. That little statement meant the difference between frustration and feeling heard. TL;DR: making visible that statement *and* being responsive counts for a lot.
Case 2: At a mid‑sized company, we rolled out an accessibility statement that claimed “WCAG 2.1 Level AA” compliance. Great headline! But when actual users tried to use screen‑reader voice commands, they found missing alt text on key product images and inconsistent heading structure. The statement had to be updated, but more importantly, the team behind it realized the statement was *not* a finish‑line trophyit was a starting point. That evolution was communicated in the statement’s revision history. Users appreciated the transparency. From my view: honesty goes farther than perfection.
Case 3: On a university site redesign, the team held user‑testing sessions with students who had visual and motor‑impairments. One student, who used a switch device rather than a traditional mouse or keyboard, commented: “I like that the site has headings that skip large blocks of contentI can jump by heading. But sometimes new pop‑ups trap me in a keyboard loop.” The accessibility statement included that exact note under “Known Limitations”: “Some pop‑ups may not yet fully support switch‑device navigation; we’re working on it and expect a fix by Q2 2025.” By giving the user a timeline and acknowledging the worknot hiding itthey built trust. That timeline, by the way, came from their internal review process and the statement noted it transparently. Smart move.
So, what lessons did I learn out in the wild?
- Don’t bury the accessibility statementput it in the footer or utility menu so real people can find it easily.
- Write human languageavoid legal jargon. Users want to know what works and what doesn’t.
- Follow through. If you say you’ll fix something by a datefix it, or update the statement. Users notice.
- Use the statement not only to declare but to invite feedback and improvement.
In short: an accessibility statement isn’t a checkbox. It’s a handshake. A promise. A sign – digital and visible – saying “you matter, your access matters, and if you hit a barrier, we’ll do something about it.” We’re proud to have one here, and we’re glad you’re reading it. Thanks for being part of the journey.