Back to Page
Accessibility
If you have any trouble browsing the site or accessing the content, please email us at info@norwood.dev.
Our commitment
We’re committed to building a robust, inclusive, and accessible website for all audiences. We strive to meet level AA standards from the Web Content Accessibility Guidelines (WCAG) 2.1.
Right now, our sites meet the majority of the standards and are substantially compliant with the AA standards. We’re working to bridge any remaining gaps by updating the website to ensure accessibility. There’s more for us to do, and we’ll continue updating this page as we make improvements.
Site features
Our goal is to give everyone the same levels of access and ease of use.
- Each page on this site has semantic regions for the navigation, main content, and footer so you can move around quickly. There’s also a “Skip to main content” link on every page.
- Stories begin with an h1 heading, and we’ve done our best to ensure headings follow a logical order.
- You should be able to zoom up to 300% without any issues.
- Design elements have been updated to improve color contrast and navigability.
- We support captions in our video players, and we’ve improved how videos work with screen readers.
- Advertisements should have accessible labels. We don’t hide content if you use an ad blocker. We also encourage advertising partners to include captions for sponsored videos.
- Newsletter subscription forms and social sharing menus are more useable. If you share a story that has images with alt text, we send the text alternatives over to Facebook and Twitter as well.
How we test the platform
Along with testing in modern browsers, we use VoiceOver in Chrome and Safari to review our sites. In the near future, we will test any changes or improvements with NVDA and VoiceOver. We’ll continue updating this page as we make improvements.
Contact us
If you have any feedback or questions about accessibility, we’d love to hear from you: info@norwood.dev. Please include details about the kind of assistive technology you’re using (e.g., VoiceOver on iOS).