OMBU is committed to designing, building, authoring, and testing websites & applications that provide high-quality experiences with as few barriers as possible for as many people as possible.
We’ve written this statement in February 2020 to talk about the accessibility of
ombu.dev, the website you’re currently reading. Specifically, we’d like to describe:
- Things you should be able to do on this website
- Our conformance with technical accessibility standards
- Areas of the website that are not fully accessible
- How we evaluated this website
- How to report accessibility problems
Things you should be able to do on this website
While interacting with the web pages here, we expect that you should be able to:
- Use any major operating system and web browser released within the last 5 years.
- Navigate the entire website with only a keyboard.
- Access all of the website’s content with a screen reader.
- Zoom in up to 400%.
Our conformance with technical accessibility standards
OMBU’s ongoing goal is to achieve and maintain conformance with the Web Content Accessibility Guidelines version 2.1 (WCAG) AA technical standard. We have embraced this goal as part of our company culture, and invoked it explicitly during the definition, design, development, authoring, testing, and deployment of this website.
Beyond conformance with technical standards, we have also aspired to follow some best practices:
- Content has been carefully authored with semantic intent.
- Moving elements (e.g., parallax) will respect the user’s “
prefers reduced motion” setting, when present.
- Intentional use of landmarks for navigation by screen readers and other assistive technology.
- Lazy loading of images to reduce bandwidth consumption and improve performance.
The website itself is built with the following features and technologies:
- Responsive images
- Parallax effects
- Modal content
Areas of the website that are not fully accessible
We are already aware of a few areas which require accessibility fixes & improvements.
- Text headings do not always follow a logical hierarchy.
- Focus may not always change as expected.
- Screen readers may pronounce some text strangely.
If any issues similar to those above prevent you from accessing content on our website, please get in touch.
How we evaluated this website
In November of 2019, we completed an internal audit of the website, guided by the WCAG-EM (Web Content Accessibility Guidelines Evaluation Methodology) version 1.0. Because the website is relatively simple, we were able to include every page in the scope of the audit (versus a reduced set of sample pages). The audit incorporated the following tools & processes:
- Visual inspection
- Markup inspection
- Color contrast analysis
- Browser zoom
- Keyboard navigation
- Screen reader testing with VoiceOver in Mac OS and iOS
- WebAIM WAVE automated tests
- Google Lighthouse automated tests
- axe Pro automated and guided manual tests
The audit revealed 86 WCAG 2.1 conformance failures at the A and AA levels. We prioritized those failures according to perceived likelihood and severity, then resolved the top twenty. Please feel free to review the issues we discovered, at which we continue to chip away.
How to report accessibility problems
If you encounter any issues while using this website, or have an inquiry related to accessibility, we’d be grateful to hear from you. Please email us at firstname.lastname@example.org. We will aim to respond within two business days.