Accessibility audits lead to better websites
We are accessibility experts. In addition to making sure the sites we build conform to WCAG 2.1 AA standards, we also help existing sites reach better conformance with audits, development support, and expert advice.
Strathcona County is a municipality located in central Alberta. Its website had recently been redesigned, but it hadn’t been optimized to conform to the Web Content Accessibility Guidelines (WCAG) 2.0.
Committed to regular accessibility checks and a transparent audit and remediation process, Strathcona County called upon Mugo Web to conduct a thorough website accessibility audit and to prepare an audit report to share with its constituents.
While Strathcona County’s new site was fairly well laid out for accessibility, a few key components proved problematic.
First, its mobile menu was not at all accessible, preventing people with disabilities from accessing the site via mobile device.
Secondly, the site was also using image alt tags inconsistently. Alt tags are a critical element of web accessibility for people with visual impairments.
Finally, many of the site’s buttons and links had been implemented using non-traditional coding methods. But screen readers couldn’t recognize them, preventing users with disabilities from accessing key functions via screen reader.
Mugo’s web accessibility expert Dave Fearnley conducted the web accessibility audit for Strathcona and produced a comprehensive accessibility audit report detailing recommendations on how to address the issues that were identified.
For example, regarding the structural issue with Strathcona’s functional elements, such as buttons and links, Fearnley says, “we identified the problem areas and demonstrated how to change the source code as opposed to changing the content.”
Fearnley’s report also provided details on how to make the mobile menu accessible. “You need to be able to tab through every item on the menu, Fearnley says. “All the functions that you can do with a mouse have to be possible with the keyboard as well, as that is how many people with accessibility issues will experience the site.”
Finally, the report covered alt-tag accessibility, which was inconsistent on the Strathcona County website. “Sometimes they were missing, sometimes they were there, sometimes they were incorrect,” Fearnley says.
Strathcona County began implementing changes to its site immediately after reviewing the report. And they’ve been entirely transparent about it with their audience. “They’ve posted a public version of the report to ensure transparency with the process,” Fearnley says. “Communicating that you’re trying to improve accessibility is really important because it’s very difficult to say that you’re finished and that your site is completely accessible. Communicating how you’re trying to address guidelines is so important for someone who is having difficulty with the site.”
With clients that include nonprofits and government-funded institutions, Foundation Center, a New York City-based non-profit organization that works to facilitate philanthropy, faces stringent web accessibility requirements.
Foundation Center engaged Mugo Web to conduct a web accessibility audit to ensure its grant prospect research application conformed to the Web Content Accessibility Guidelines (WCAG) 2.0.
The Center had a new web design in the works for its Foundation Directory Online, and wanted it to be reviewed for conformity with the Web Content Accessibility Guidelines (WCAG) 2.0. “As a nonprofit serving other nonprofits, accessibility is important to us,” says Renee Westmoreland, Managing Director of Web Design and Development at Foundation Center. “Also, we offer our product in public libraries and institutions that receive government funding and therefore have strict accessibility requirements.”
After attending a Mugo Web and eZ Systems web accessibility webinar, the Center called on Mugo to conduct a web accessibility audit.
The Foundation Center’s new directory design relied on a palette of bright colours alongside heavy use of bright white text, a fairly modern design scheme which is problematic when it comes to web accessibility. WCAG 2.0 specifies the minimum amount of colour contrast needed to ensure maximum legibility for people with low vision.
The directory also uses a lot of forms and widgets, as well as graphs and interactive graphics, content that doesn’t tend to lend itself well to accessibility unless it’s designed that way from the outset.
Mugo’s web accessibility expert Dave Fearnley conducted the web accessibility audit for Foundation Center and produced a comprehensive accessibility audit report detailing recommendations on how to address the issues that were identified.
Fearnley noted a number of sections of the site which had non-conforming components such as interactive graphics. “Foundation Center decided to provide a text alternative instead of having the itemized audit of those sections,” Fearnley says. “If the client has a section that will be particularly problematic, and that’s something we identify early, then they can choose which way to go. Text alternatives are fine; some things simply can’t be made accessible if they’re a purely visual tool, unless the designer was thinking of accessibility from the beginning.”
Fearnley also recommended changes to the site’s colour palette, a challenging proposition given the colour palette was based on corporate colours. “You have to work around not going right back to the drawing board,” Fearnley says. “That’s why it’s best to get on top of accessibility at the beginning of a web project.”
Foundation Center is working to implement changes to address the issues identified in the audit document. “Some changes have been deployed and we continue to work through the list,” Westmoreland says. “The audit results provided very good detail, and working with Mugo Web was a pleasure. They are very knowledgeable.”
CAPTCHA is an essential need on online forms, but to be blunt, the UX sucks. Without the implementation tips (helpfully detailed below), Google’s otherwise reliable reCAPTCHA service implemented “as-is” doesn’t actually provide any browser validation. The user will have to wait for it to make a time-consuming round trip to the server. It’s a problem for anyone and becomes compounded for users with accessibility needs.
Mugo partner since 2024
Delaware County Libraries is a regional library system in Pennsylvania, USA.
Mugo partner since 2024
Dymax is a developer and manufacturer of broad-spectrum light-curable adhesives.
Mugo partner since 2024
Hibu provides digital marketing solutions to local businesses across the US.
Links are among a website's most valuable components. They connect (that’s what the word “link” means, after all) different pages and resources, helping site visitors find the content they are looking for. Well-planned and formatted links are like a detailed, intuitive treasure map that sends visitors to the right destination.
Links are also critical for making your website accessible to visitors with visual or other impairments. A link that lacks important information can prevent some visitors from accessing all the treasures a website holds. Or even worse, it can send users to completely undesirable content and discourage them from exploring all your site has to offer.
In this post, I’ll discuss how to present links in various contexts, clearly explaining how they can create and inform powerful relationships between different pages and assets.
Amazon Web Services (AWS) EC2 has the reputation of being a pricey option for cloud-based hosting and compute resources. Certainly, that was our initial impression here at Mugo Web years ago when we began standardizing our hosting and site management business on a single cloud platform.
However, we quickly discovered that AWS is actually quite affordable. In fact, our monthly costs for a virtual machine using 8GB of RAM, at 100% usage, is predictably lower with AWS than with other virtualized or traditional data centers. That’s without aggressively tuning our resource usage, which is often the focus of how to optimize AWS pricing.
In this post, I’ll show you how AWS can be a cost-effective option for professionally managed websites. I’ll also take a quick look at some of the additional savings tactics you can employ to get more value from your decision to run on AWS.
In this blog post I am going to talk about several security best practices, particularly for configuring AWS Access Keys. Some of these practices are based on a project that we inherited which was compromised by hackers. Best practices are often learned from mistakes; and when the mistakes are someone else's, so much the better!
If you were used to the Open Source version of eZ Publish, you are probably familiar with the eZ Flow extension, which allows editors to build pages visually specifying the components based on a Layout, Zones, and Blocks system. Users that have migrated to the Ibexa OSS might have noticed that there is no such system available, only the Ibexa Page Builder, which is restricted to the Enterprise version.
At Mugo, we love to contribute to the Open Source community. After identifying this need, we decided to create a prototype for an alternative to the eZ Flow extensions for Ibexa OSS. With that in mind, we created the Mugo Page Bundle as a simple way to build page layouts.
Mugo Web
Unit 205, 332 Columbia Street
New Westminster, BC
V3L 1A6, Canada
Phone: 604-637-6396
E-mail: hi@mugo.ca
