My name is Larry Waldman -- I am a Program Manager on the Office User Experience team and have been working in this role to make Office more accessible for almost 5 years. When users of Office hear that Microsoft has many people working specifically to make our products more accessible to people with disabilities, many express surprise. With such a broad customer base, we recognize the importance of considering accessibility impact in every feature we build. For example, check out this article I wrote about Accessibility and the Ribbon in Office 2007.
Upon starting our research for the 2010 release, we knew it was important to continue our accessibility focus (see Microsoft Accessibility for more info) and ensure that Office 2010 is the most accessible version of Office ever. Not only are accessibility improvements garnering increasing attention from governments, but accessibility improvements provide broad usability improvements and as such are becoming a key area of focus for the software industry in general. With that in mind, we planned Office 2010 with two key accessibility pillars:
Providing detail on all of Office 2010’s accessibility improvements can’t be done in a single blog post, so I’m going to focus today’s discussion on Office 2010’s new document Accessibility Checker feature. I’ll end the post with a few high level bullets of other accessibility features that we might discuss in the future.
While user interface accessibility has been well understood for years, the accessibility of Office document content is a burgeoning new area. In particular, we’ve seen many requests from companies and governments who have been wondering how to help their employees create accessible content. To solve this problem in Office 2010 we created a document Accessibility Checker (like a spell checker, but for accessibility issues) as a core feature of Word, Excel, and PowerPoint.
We started by examining the most common accessibility problems in Office documents and bucketing them in terms of their severity – we ended up with three categories:
Based on these three categories, we came up with a set of issues our checker looks for (described in more detail below) – when presented to the user, they are bucketed into “Errors”, “Warnings”, and “Tips” – these buckets correspond to the above three descriptions.
One of our key principles for Office 2010’s accessibility checker was to make the feature available out of the box for all users – in a way that’s integrated with the authoring workflow. Rather than force users to remember to run the accessibility checker before sending a document, we integrated accessibility results directly into the Backstage view. Anytime you click the File tab and view the Info place, accessibility information will be provided under the Prepare for Sharing header. Prepare for Sharing is described more generally in this Backstage view blog post, but this is the place in the UI where authors go to ensure their file is ready to be shared with other readers; they can check for hidden information, metadata, and now accessibility issues.
To receive more detailed information (including what issues were found, why they are issues, and step-by-step instructions as to how to fix each one), users can click ‘Check for Issues’ and then click “Check Accessibility”.
This will close the Backstage View and open a task pane so you can interactively find and fix the issues in your document. In addition to the screenshot below I’ve provided a detailed textual description of how to use the checker and how its UI is represented to screen readers.
The task pane has two main UI sections.
The top section is a tree view control (with each tree item navigable via arrow keys). Each “violation type” (missing alt text, no table header row, repeated blank characters, etc…) is an item that is collapsible.
When showing, each violation type contains one or more violations – these are represented to screen readers as children of the parent “tree items”. Each leaf is key focusable. For example, if you have two pictures that are missing alt text, they will be two violations under the “Missing Alt Text” node – each can be selected. When a violation is selected, the document will scroll to and select the problematic content.
Where possible we try to name each violation with a meaningful name (for example “Picture 1”) – And in PowerPoint or Excel you’ll find that we also try to provide what slide/sheet the object is on. Note – the violation types are grouped into “Errors”, “Warnings”, and “Tips” – These headers separate the tree items in the view, but they are not collapsible themselves. The group headers are also not key focusable.
When you select an issue in the top part of the pane, the bottom of the task describes how and why to fix it. Just above this bottom section is an “expand/collapse chevron” that allows a user to collapse the bottom pane.
All of the text in the bottom pane section is represented to a screen reader as one big pane with static text. When focus is on the pane, it can be scrolled using ctrl+up/down and pageUp/pageDown. Finally, there is some explanatory text and a more info link at the bottom of the pane if users need more help.
When Office 2010 ships there will be full documentation provided that details each violation the checker will scan for. In the meantime, here is a quick list of what we check for in each Office application – you can download the Beta and try out the Accessibility Checker with your files to see more details for the issues your content has. The top box for each application contains Errors, the middle contains Warnings, and the bottom contains Tips.
While we’ve tried to include as many accessibility issues as we can for Office 2010, we do recognize that there are still accessibility issues we don't yet check for. If you have a particular issue that didn’t make it into this release, please feel free to leave us a comment on this post and let us know things you’d like us to consider for the next version.
As part of our documentation process we’ve provided Assistive Technology Vendors with details about how they can use the Office accessibility platform (including our Object Model) to ensure they optimally read back Office content for their users.
For organizations that are concerned about compliance for employees, we’ve provided several group policy settings that can be used to customize exactly which accessibility violations are checked. Administrators can also increase the visibility and emphasis of the Prepare for Sharing information when there are errors or warnings. Finally, IT departments can leverage Office 2010’s UI extensibility to enforce a workflow that requires users to run the checker – this will help many corporations reduce the risk of employees creating inaccessible content and increase the amount of accessible information available to people with disabilities.
While this post has drilled deeply into the new document accessibility checker, here are a few other highlights we’ll be considering blogging about in the future. Feel free to leave comments and we’ll be sure to drill into what you’re most interested in.
The release Office 2010 is groundbreaking on many levels. Not only are we delivering features to users that provide a great accessibility experience across the PC, the Web, and the Phone, but we have continued to enhance our platform interoperability and commitment to AT Vendors. Hopefully this look at accessibility is useful – please let us know via the comments if you have questions or would like more information on a particular topic.
Larry Waldman, Program Manager, Microsoft Office
Update: Nick Simons just blogged about accessibility and the Office Web Apps. Check it out at http://blogs.msdn.com/officewebapps/archive/2010/01/18/9949907.aspx.
Another update: Diana Kimball just published a quick blog about accessibility and PowerPoint. Check it out at http://blogs.msdn.com/powerpoint/archive/2010/01/26/behind-the-scenes-accessibility-in-powerpoint-2010.aspx.
Outlook has locked up completley since I installed Office 2010 a couple iof days ago. Suggestions?
@David R. - This is not the appropriate location for general tech support. I suggest you start with a more appropriate location like the Office 2010 Technet forums at http://social.technet.microsoft.com/Forums/en/category/office2010. Thanks.
I am pleased to hear that this is on the minds of the people at Microsoft as Windows is the most popular platform for visually impaired users.
One question I do have however is, why is accessibility not important on your version of Office for the Mac? Office 2008 for Mac seems stripped of the things suck as alt tags and link title elements that are found in Office 2007. Many educational institutions who create content for course work use a Mac equipped with Microsoft Office. Either this is a major oversight, or an unethical approach to marketing.
@Saqib – Thank Saqib. Please feel free to send us your findings directly if you like. There is an “email” link at the top of this blog you can use to do so.
@Mike B. - The Mac Office team has been working to improve accessibility support in Office 2008 and the next version of Office. We cannot get everything done in this release, but do plan on continuing to improve accessibility support in future versions as well.
I still remain completely amazed at the amount of effort being spent adding esoteric new features while at the same time abandoning the vast majority of millions of users who just want to be able create simple documents. I find the ribbon interface extremely frustrating to use, I DO NOT want to have to learn a whole new interface, and Microsoft doesn't seem to give a damn.
@Rick: From a UI and UX perspective, I think the ribbon is a lot better design - a game changer so to say.
You can read more about the story of the ribbon, and the design decision at:
I have found the search function in say Control Panel very useful when looking for control panel functions. Perhaps the ribbon in office 2010 can have an integrated search feature that will assist users locating the function they wish to use. Generally I find that I can easily locate 80% of the required functionality, but the remaining 20% is a major time waster and distracts from the efficiency generated by the office product suite. Unsure if this is feasible, but would be awesome if it could be done.
@Michael Camiolo: As Larry mentions above, this isn't a good location for bug reports. I'd recommend the forums at http://social.technet.microsoft.com/Forums/en/category/office2010 to more consistently get a response.
On the other hand, I happen to be the developer on the "Paste Options" feature that you're referring to. Thank you for the detailed repro steps! I can confirm that this is a known issue, and I am no longer seeing it in more recent builds.
I have instaled mS office 2010 profesional plus beta.
and I was vary glad with it improvements. however, theres one big proglem with equations. Wen I write documet with them and then print, on a printet paper equations is flat and marged and unreadable. is there a way to slaw this problem in my computer, or its programical error ? this happens in oll offce productswhere equations cen be used. (Sorry for my english grammar, because I am not from english speaking country.
The problem mentioned about colorblindness and having colorblind testers is valid for red-green but I'm green-brown colorblind anyway. It's not the spelling/grammar underscores I have problems with. It is the lack of color or shade gradient between the active window/panel/dialog box and the rest. So I have closed the wrong one many times and it is getting worse with Windows 7.
A few questions:
Any information on what Office 2010’s built-in Save as Accessible PDF supports for the tagged PDF rendered compared to Adobe Acrobat word plug-in?
Are there any plans to make a Save as DAISY for PowerPoint this would be a great way to deliver accessible slides to users?
Where would be the best place to post bugs that users are experiencing with the current Save as DAISY tool with Word 2010?
When attempting to use the accessibility checker in beta Word 2010 it will not work with word 2007 docx or doc files but does not give the user any information as to why this is. Will this be fixed in the final version of Word 2010?
@Sam -- Thanks for your questions. We'll be following up over the next few days.
With respect to your question about file formats, the accessibility checker will work with Open XML files or ODF files, but not when the application is in compatibility mode for an older file format (as would be the case when working with a Word 2007 docx). This is because we want users to focus on the latest formats with the most accessibility features. If saving into an older format, we cannot guarentee that all accessibility features would be preserved. If you like, you can convert your document to the latest version, run the accessibility checker, and then save to an older version (leveraging the Office Compatibility Checker (and other features) as you like to try to mitigate information loss). I hope this helps.
Larry Waldman [MSFT]
I would like to whether Word 2010 will be able to use Windows Live Mail as an email client ? We were unable to use Windows live Mail with Word 2007 from the Office Button>>Send option. If it does not it should atleast work with the click to run option as the Office is being used from Virtual Q drive in that case..
Thanks and regards