While the tweet is good news, indicating that the Australian Federal government will be moving to WCAG 2.1, there was initially some confusion with the announcement. Given there are only 12 Success Criteria in WCAG 2.1 Level AA, the tweet inferred that the Federal government would be moving to Level AAA to implement all 17 Success Criteria. If true, this would have been a major departure from existing government policy.
To clarify this issue, I sent a reply to the DTA’s tweet, checking if they were indeed planning to implement all 17 Success Criteria. In response, the DTA stated:
“Hi @scotthollier, we apologise for the delay in responding. There are no plans to move to AAA, but as we explore the updates to WCAG 2.1 we’re issuing new best practice advice to help agencies understand the changes.”
This suggests that the new Federal government requirement described by the Digital Service Standard is likely to be based on a WCAG 2.1 Level AA conformance, incorporating the 12 largely mobile-focused new Success Criteria.
If you are subscribed to Microsoft Office 365, you may have noticed an alert appearing recently when launching an Office application such as Word or PowerPoint. The message is about a new update to the built-in document accessibility checker. In Microsoft’s What’s New In Office 365 page, the update is described as follows:
“One-click fixes for accessibility issues: The Accessibility Checker is better than ever with updated support for international standards and handy recommendations to make your documents more accessible.”
Given that many people aren’t aware that Microsoft have had an accessibility checker tucked away in Office for some time now, let alone how to use it, I thought it’d be a good time to pull together the common questions I’m asked about it.
What is the Accessibility Checker?
The Microsoft Accessibility Checker is a feature included in Microsoft Office that allows users to check the accessibility of their documents. When the check is used, it provides a list of potential accessibility issues with suggestions on how to address them. The user is then able to fix the issues to make the document more accessible to people with disabilities.
Which versions of Microsoft Office have the Checker?
The accessibility checker was first introduced in Office 2010.However the feature was difficult to find in earlier versions so many people did not know it was there. This has been improved with Office 365. The feature is currently available in the Windows and Mac versions of Office.
Which Office applications have the checker?
The checker is currently available in Word, Excel, PowerPoint and more recently Outlook. This means you can check documents, spreadsheets, slides and e-mail for accessibility issues and follow the recommendations to fix them.
Does the accessibility checker conform with WCAG?
Given that Office is an authoring tool rather than a website, a more applicable standard would be its compliance to the Authoring Tool Accessibility Guidelines (ATAG) 2.0. ATAG essentially looks at whether a tool can be used by a person with a disability, and whether that tool can produce accessible content based on WCAG. In both cases, the answer for Office on Windows is broadly yes, but people with disabilities have reported issues using Office on Mac, iOS and Android due to incompatibilities with assistive technologies. The Checker itself though is available on Office for Windows and Office for Mac. As such, Office for Mac still remains broadly compatible with the second part of ATAG 2.0.
While ATAG is the more applicable standard when discussing authoring tools, WCAG still plays an important role. As such, the accessibility requirements for document formats such as Word and PowerPoint will sound very familiar to people when compared with WCAG: images need alternative text, videos need captions, tables need headings and documents need to be structured correctly using styles – just to name a few. The accessibility checker is useful in that it can check a document for issues that are in common with WCAG along with additional advice related to Microsoft-specific features.
Review your results. You’ll see a list of errors, warnings, and tips with how-to-fix recommendations for each.
If you are using an older version of Office such as 2010 or 2013, here’s how you can find and use the Checker in Word, Excel or PowerPoint:
Click File > Info.
Select the Check for Issues button. Tip: To the right of the Check for Issues button, under the Inspect heading, is a list of any potential issues.
In the Check for Issues drop-down menu, select Check Accessibility.
The Accessibility Checker task pane appears next to your content and shows the inspection results.
To see information on why and how to fix an issue, under Inspection Results, select an issue. Results appear under Additional Information, and you’re directed to the inaccessible content in your file.
Is the latest Checker update important?
The recent update to the accessibility checker makes the interface much easier to cross-check and fix accessibility issues with your Word, Excel, PowerPoint or outlook document. However, the more important benefit to using the latest Office 365 version is that it is now able to provide guidance on more issues. If you are regularly providing documents to people with disabilities, it is strongly recommended that you update to Office 2016 or Office 365 with the latest updates to maximise the effectiveness of the Accessibility Checker.
In an e-mail to the WAI Interest Group (WAI-IG), fellow editors Janina Sajka, Accessible Platform Architectures WG Chair and Michael Cooper, Accessibility Guidelines WG W3C Staff Contact, announced that:
“The Accessible Platform Architectures Working Group has published aWorking Draft of a revision to Inaccessibility of CAPTCHA at:https://www.w3.org/TR/turingtest/ Inaccessibility of CAPTCHA has been a Working Group Note since 2005. It describes problems with common approaches to distinguish human users of web sites from robots, and examines a number of potential solutions. Since the last publication, the abilities of robots to defeat CAPTCHAs has increased, and new technologies to authenticate human users have come available. This update brings the document up to date with thesenew realities. It is published as Working Draft to gather public review,after which it is expected to be republished as a Working Group Note.”
As an invited expert for the W3C WAI APA Research Questions Task Force (RQTF), it’s been a privilege to work with Janina and Michael on updating the note alongside the hard work of all the RQTF members. This is the first time I’ve been involved in the W3C editorial process and the experience has been very rewarding.
With the first draft complete, the Note is open for public comment so that additional improvements to the advice can be included. Additional information about this publication can be found in the CAPTCHA Note blog post.
While the growth of the video games industry remains the envy of many, it is its projected growth that continues to amaze. This is due in part to the large number of devices that we use and our desire to play video games on all of them. From the more traditional video game console connected to our television through to our computer workstation, mobile phone and the emerging wearable market, it’s become clear that if we have an electronic device, we strive to figure out a way to put a game on it. As the popularity of virtual reality and augmented reality continues to filter into the mainstream, it too is becoming a gaming platform that continues to grow in popularity. Even the relatively new category of digital assistant smartspeakers in the home such as the Amazon Echo now have audio-based games available on demand.
Yet it is perhaps with some irony that for people with disabilities, the classic video games I enjoyed as a child with a vision impairment -with their high contrast colour scheme, primitive sound effects, large blocky pixel graphics and predictable gameplay strategies – may have unintentionally represented a time of gameplay accessibility that has seemingly declined since the classic video game era. While there are notable exceptions where developers have worked hard to include accessibility, it is generally deemed to be an exception rather than the rule.
Fortnite and Minecraft: easy to play, hard to find accessibility information
With that in mind, let’s consider what accessibility features are included in the current worldwide smash Fortnite Battle Royale, and one of the games that previously held the title of world gaming dominance, Minecraft. For this I’ve enlisted my 10-year-old son who is a master of both along with a bit of online research.
One of the first things I discovered is how difficult it is to find a simple overview of the accessibility features in these games despite their popularity. While the information is out there, it is surprisingly challenging to locate a concise summary, especially when trying to get a comparison across different platforms. This is arguably an issue in itself. However, with perseverance comes reward, and in Fortnite Battle Royale my son and I were able to track down its accessibility features which included colour correction options, some control mapping and captions for the introductory video.
Minecraft was a bit easier in terms of finding information possibly due to the game having been around much longer. There also appear to be ongoing updates to its accessibility such as a recent text-to-speech option being added for in-game chat.
There are good news stories though – enter Microsoft
Although the implementation of accessibility features in popular games is ad-hoc at best, there are many examples of big gaming companies trying to improve this space. In addition to a number of accessible gaming titles, the spotlight on best practice turned to Microsoft recently with its announcement of its Xbox Adaptive Controller (XAC). Developed by Microsoft in collaboration with AbleGamers, Warfighter Engaged, SpecialEffect, Craig Hospital and the Cerebral Palsy Foundation, the controller was designed to include two oversized programmable buttons, 19 3.5mm input jacks and two USB ports, allowing disabled gamers to easily connect special joysticks, switches, and any other tools they may need.
While the initiative of the XAC is a great one, an accessible controller is only as good as what the software allows it to do and in this regard there’s still no guarantee that the Xbox or PC games released will be compatible with it or provide any accessibility features at all.
The need for standards
To ensure that games are accessible, there are essentially two critical things that need to occur: firstly, people with disabilities need to have accessibility features provided in the gaming platform. Secondly, games need to be designed in a way that supports such features. To provide dependable guidance on this, it is necessary for game developers to have an internationally recognised standard.
However, despite the popularity of gaming across a range of electronic devices, there has not been the same desire to develop internationally-recognised standards in this space as there has been for web content more broadly. With the third iteration of the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) celebrating its recent 2.1 release, the lack of gaming support is becoming more notable by comparison.
As such, the not-for-profit organisation AbleGamers has created a resource titled Includificationwhich highlights how developers can ensure that their games meet basic accessibility requirements with broad categories of mobility, hearing, vision and cognitive guidance.
Structured in a similar way to WCAG with three implementation levels, the mobility-related guidance focuses on the need for alternative configurations, camera controls, and remappable keys. Additional requirements focus on the provision of customisable user interface elements, save points, adjustments to input settings and speed settings.
In regards to hearing, the core focus is on the provision of closed captions and the ability to adjust the font and size of such captions, along with the removal of ambient game noise. For vision the focus is primarily on the ability to adjust the colour font, with a specific reference to the inclusion of a high contrast marker for in-game enemy tracking. There is also consideration for the provision of text-to-speech output such as compatibility with screen readers.
In regards to addressing cognitive issues, AbleGamers recommends that game tutorials are clearly provided, speed adjustment settings are provided, training modes are available and there should be a clear indication of in-game enemies.
In addition to the AbleGamers Includification, a second separate initiative by industry professionals has created guidelines simply known as the Game Accessibility Guidelines living document. Featuring a similar structure to the Includification guidelines there are three implementation levels with a focus on general, motor, cognitive, vision, hearing and speech requirements. While many of the points are similar to the Includification guidelines, there are some important additional recommendations such as the need to label packaging and online materials at point of sale with information on the game’s accessibility features.
We have the guidance but not the solution
Given there’s two comprehensive documents that explain how to make games accessible, let’s look again at how Fortnite Battle Royale and Minecraft stack up. Both games do contain some accessibility features so at least we can see that thought has been given to the issue. Yet in both cases the games fall way short of the recommendations and there’s no easy way to determine in-store if a game is accessible or not. The problem is that despite the best intentions of Able Gamers and the merit of their guidance on accessible gaming, the Includification guidelines are not a standard, and as a result there is no specific legislative or policy framework that requires their implementation. Until an official international standard is released, it will continue to be up to the industry to decide how accessibility is implemented, and to what degree that process occurs.
Let’s make the next gaming hit an accessible one
To achieve a genuine and ongoing solution, I’d like to join in the chorus of calls to gaming companies and standards bodies to engage with organisations such as AbleGamers to find ways to make their guidelines an enforceable standard. The XAC has demonstrated that such a collaboration is possible and what it can yield so there’s no reason this can’t take place.
As a legally blind person it would be awesome if I could team up with my son in Fortnite Battel Royale but due to my vision our ability to play games together remains firmly locked in the 8-bit era. It’s a shame as it wouldn’t take much customisation to make the modern gaming experience accessible to me. The time has come for accessibility in gaming to be as comprehensive and predictable as the likelihood of a new game sweeping the world. Hopefully on that occasion I and everyone else that would like to play can join in too.
The Google Podcasts app is designed to make it easier for Android users to search and subscribe to podcasts, a feature which has worked well on Apple iOS devices but has largely eluded Android users to date since Google abandoned its Listen experiment in 2012.
While the Android platform can provide podcasts via third-party apps along with some podcast features in other Google apps, the new standalone Podcasts app aims to provide a simpler experience with a promise to introduce an important accessibility feature – the ability to have podcasts auto-transcribed.
Greatly decreasing the friction from search results to an actual mobile listening experience, thus operationalizing searches as a true top of the funnel;
AI-assisted features like quick transcription, greater in-episode searchability, automatic visual subtitling across multiple languages, and content-indexing, which will presumably give audiences more control over the judgment and navigating of a listening experience (and, also presumably, put some speech-to-text transcription companies out of business);
Cross-device syncing, which allows users to easily transition between listening on a smartphone or through a smart speaker;
Direct monetization features, like the possibility of a “donate” button.
For people who are Deaf or hearing impaired, the potential inclusion of an auto-transcription feature into the Podcasts app would be highly beneficial in providing access to a wealth of audio-based online content. While similar Google initiatives such as auto-captioning on YouTube have been met with a mixed reception due to quality issues, the professional audio quality of most podcasts is likely to make the auto-transcription services more useful and accurate.
The Google Podcasts app can be downloaded now from the Google Play Store. There are currently no plans for an Apple iOS release.