The 2016 International Day of Persons with Disabilities (IDPD), focuses on laying the foundation for a future of greater inclusion for persons with disabilities. In honor of IDPD, we invite all Office 365 customers to lay the foundation for a more inclusive digital environment by discovering and using accessibility capabilities built into Office 365.
Create accessible content with Office 365
Office 365 empowers you to communicate information to your colleagues and customers in a variety of ways: documents, presentations, spreadsheets, emails, chats, sways, notes, videos and more. As you communicate, it is important to meet the diverse needs of your audience. Making your content accessible ensures it can be used without barriers by people with varying levels of vision, hearing, cognition and mobility.
Q. How can I get help with accessibility issues?A. Visit the Office Accessibility Center to find support articles on creating accessible content with Office 365 applications on various platforms or on using Office 365 applications with specific assistive technologies. If you require further assistance, reach out to an accessibility specialist via the Enterprise Disability Answer Desk or Consumer Disability Answer Desk.
Curated by (Lifekludger)
Read full article at Source: Accessibility in Office 365—enabling greater digital inclusion – Office Blogs
Windows has used the Microsoft Active Accessibility (MSAA) API since Windows 98 to express buttons, menus, text, and other on-screen content to assistive technology. Assistive technology vendors have used the MSAA API (along with other app-specific APIs like the DOM in IE, the Office Object Model in Office, and even scraping video drivers) to make text and interfaces more accessible. These techniques have the disadvantage of varying wildly between different applications and documents, which leads to a fragmented and unreliable experience. As user interfaces, documents, and the web significantly increased in complexity, Microsoft introduced the more modern UI Automation (UIA) API in Windows Vista as the successor to MSAA.
UIA was designed to expose more information about the user interface and structured documents, improve performance, and be portable across platforms. Because UIA replaces a variety of potentially unreliable and non-interoperable techniques with a single API, it reduces software complexity, allows developers to express novel UI concepts more easily, and improves stability and user experience consistency between web and native apps, across all types of assistive technology.
In Microsoft Edge, we are thrilled to finally have the opportunity to make the transition from MSAA to UIA, alongside enormous complementary investments in rearchitecting our DOM implementation and rewriting the browser interface from scratch. The change to UIA is our largest investment in browser accessibility ever, and it lays the foundation for a more inclusive web experience for users who depend on assistive technology in Windows 10. Because EdgeHTML is used throughout Windows 10 (inside Universal Windows Apps, in Cortana, etc.), these benefits will have an impact beyond the browser. Users will also benefit from the evergreen nature of the EdgeHTML engine.
curated by (Lifekludger)
Read full article at Source: Accessibility: Towards a more inclusive web with Microsoft Edge and Windows 10