DOCSLIB.ORG

Google Accessibility Conformance Report: Chrome OS Version 84

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Google Accessibility Conformance Report: Chrome OS Version 84 Google Accessibility Conformance Report Revised Section 508 Edition (Based on VPAT® Version 2.4) Name of Product/Version: Chrome OS version 84 Report Date: 9/1/2020 Product Description: Chrome OS is the operating system that runs on Chromebooks Contact Information: [email protected] Notes: Chrome OS is an operating system with the Google Chrome browser built-in that allows users to browse the web. This document makes no claims of conformance for any third-party content that users access through the web or through any app stores supported by Chrome OS. The scope of this VPAT is limited to the Chrome OS software and does not apply directly to hardware devices. Please refer to the VPAT for the specific Chromebook models for additional details. The scope of this document asserts conformance for these core Chrome OS features: 1. Onboarding and account creation 2. App Launcher 3. Notification Center 4. Settings 5. Files 6. Chrome Browser __________________________________ “Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI) Page 1 of 16 The following features are considered experimental and are not available on all Chrome OS devices, and are therefore outside of the scope of this document: 1. Google Play Store 2. Linux shell Evaluation Methods Used: This evaluation was conducted by the American Foundation for the Blind using expert usability testers and accessibility engineers to thoroughly evaluate checkpoint. Applicable Standards/Guidelines This report covers the degree of conformance for the following accessibility standard/guidelines: Standard/Guideline Included In Report Web Content Accessibility Guidelines 2.0 Level A (Yes) Level AA (Yes) Level AAA (No) Revised Section 508 standards published January 18, 2017 and corrected January 22, (Yes) 2018 Terms The terms used in the Conformance Level information are defined as follows: • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation. • Supported with Exceptions: Some functionality of the product does not meet the criterion. • Not Supported: The majority of product functionality does not meet the criterion. • Not Applicable: The criterion is not relevant to the product. • Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA. Page 2 of 16 WCAG 2.0 Report Tables 1 and 2 also document conformance with Revised Section 508: • Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing • Chapter 6 – 602.3 Electronic Support Documentation Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements. Page 3 of 16 Table 1: Success Criteria, Level A Criteria Conformance Level Remarks and Explanations 1.1.1 Non-text Content (Level A) Software (Chrome OS): Chrome OS supports alternative Also applies to: Web Content (Chrome Supports text in all areas of the user interface except the Revised Section 508 Browser): Support Docs: Supports following: • 501 (Web)(Software) Software (Chrome OS): • The Files app has an unlabeled button in each • 504.2 (Authoring Tool) Partially Supports header of the files table that resize the column. • 602.3 (Support Docs) 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): Not • 504.2 (Authoring Tool) Applicable • 602.3 (Support Docs) 1.2.2 Captions (Prerecorded) (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) Software (Chrome OS): Chrome OS supports 1.3.1 Info and Relationships (Level A) appropriate info and relationships in all areas of the Web Content (Chrome Also applies to: user interface except the following: Browser): Supports Revised Section 508 • In the Search Engine configuration screen, the Support Docs: Supports • 501 (Web)(Software) table headers are not properly associated with Software (Chrome OS): • 504.2 (Authoring Tool) the table Partially Supports • 602.3 (Support Docs) • In the Files app, the word “search” appears three times after search button on the Action Page 4 of 16 Criteria Conformance Level Remarks and Explanations menu with no direct relationship to the search field. 1.3.2 Meaningful Sequence (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 1.3.3 Sensory Characteristics (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 1.4.1 Use of Color (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 1.4.2 Audio Control (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 2.1.1 Keyboard (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) Page 5 of 16 Criteria Conformance Level Remarks and Explanations 2.1.2 No Keyboard Trap (Level A) Software (Chrome OS): Chrome OS contains no Web Content (Chrome Also applies to: keyboard traps in any areas of the user interface except Browser): Supports Revised Section 508 the following: Support Docs: Supports • 501 (Web)(Software) • In the notification center, there is a keyboard Software (Chrome OS): • 504.2 (Authoring Tool) trap when the notification content scrolls. Partially Supports • 602.3 (Support Docs) 2.2.1 Timing Adjustable (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): Not • 504.2 (Authoring Tool) Applicable • 602.3 (Support Docs) 2.2.2 Pause, Stop, Hide (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): Not • 504.2 (Authoring Tool) Applicable • 602.3 (Support Docs) 2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): Not • 504.2 (Authoring Tool) Applicable • 602.3 (Support Docs) 2.4.1 Bypass Blocks (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) – Does not apply to non-web software Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) – Does not apply to non-web docs Web Content (Chrome 2.4.2 Page Titled (Level A) Browser): Supports Also applies to: Support Docs: Supports Revised Section 508 Software (Chrome OS): • 501 (Web)(Software) Supports Page 6 of 16 Criteria Conformance Level Remarks and Explanations • 504.2 (Authoring Tool) • 602.3 (Support Docs) 2.4.3 Focus Order (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 2.4.4 Link Purpose (In Context) (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 3.1.1 Language of Page (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 3.2.1 On Focus (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) 3.2.2 On Input (Level A) Also applies to: Web Content (Chrome Supports Revised Section 508 Browser): Support Docs: Supports • 501 (Web)(Software) Software (Chrome OS): • 504.2 (Authoring Tool) Supports • 602.3 (Support Docs) Page 7 of 16 Criteria Conformance Level Remarks and Explanations Software (Chrome OS): Chrome OS supports 3.3.1 Error Identification (Level A) appropriate info and relationships in all areas of the Also applies to: Web Content (Chrome Supports user interface except the following: Revised Section 508 Browser): Support Docs: Supports • In settings, the passphrase sync input field does • 501 (Web)(Software) Software (Chrome OS): not properly expose error messages to the • 504.2 (Authoring Tool) Partially Supports
Load more

Recommended publications
  • Accessible Cell Phones
    September, 2014 Accessible Cell Phones It can be challenging for individuals with vision loss to find a cell phone that addresses preferences for functionality and accessibility. Some prefer a simple, easy-to-use cell phone that isn’t expensive or complicated while others prefer their phone have a variety of applications. It is important to match needs and capabilities to a cell phone with the features and applications needed by the user. In regard to the accessibility of the cell phone, options to consider are: • access to the status of your phone, such as time, date, signal and battery strength; • options to access and manage your contacts; • type of keypad or touch screen features • screen reader and magnification options (built in or by installation of additional screen-access software); • quality of the display (options for font enlargement and backlighting adjustment). Due to the ever-changing technology in regard to cell phones, new models frequently come on the market. A wide variety of features on today’s cell phones allow them to be used as web browsers, for email, multimedia messaging and much more. Section 255 of the Communications Act, as amended by the Telecommunications Act of 1996, requires that cell phone manufacturers and service providers do all that is “readily achievable” to make each product or service accessible. iPhone The iPhone is an Apple product. The VoiceOver screen reader is a standard feature of the phone. Utilizing a touch screen, a virtual keyboard and voice control called SIRI the iPhone can do email, web browsing, and text messaging, as well as function as a telephone.
    [Show full text]
  • ABC's of Ios: a Voiceover Manual for Toddlers and Beyond!
    . ABC’s of iOS: A VoiceOver Manual for Toddlers and Beyond! A collaboration between Diane Brauner Educational Assistive Technology Consultant COMS and CNIB Foundation. Copyright © 2018 CNIB. All rights reserved, including the right to reproduce this manual or portions thereof in any form whatsoever without permission. For information, contact [email protected]. Diane Brauner Diane is an educational accessibility consultant collaborating with various educational groups and app developers. She splits her time between managing the Perkins eLearning website, Paths to Technology, presenting workshops on a national level and working on accessibility-related projects. Diane’s personal mission is to support developers and educators in creating and teaching accessible educational tools which enable students with visual impairments to flourish in the 21st century classroom. Diane has 25+ years as a Certified Orientation and Mobility Specialist (COMS), working primarily with preschool and school-age students. She also holds a Bachelor of Science in Rehabilitation and Elementary Education with certificates in Deaf and Severely Hard of Hearing and Visual Impairments. CNIB Celebrating 100 years in 2018, the CNIB Foundation is a non-profit organization driven to change what it is to be blind today. We work with the sight loss community in a number of ways, providing programs and powerful advocacy that empower people impacted by blindness to live their dreams and tear down barriers to inclusion. Through community consultations and in our day to
    [Show full text]
  • Best Practices for Developing for Chromebook Tablets
    1 Best practices for developing for Chromebook tablets The goal of this guide is to share some best practices for developing Android and web apps for Chromebook tablets. With the help of educators and developers around the globe, we’ve learned some tips and tricks along the way and want to share those with you and your team. Chromebook tablets come in many different shapes and sizes and run all sorts of software—from traditional websites to extensions, progressive web apps, and Android apps. In many ways, Chromebook tablets operate the same as a traditional Chromebook. The operating system is largely the same. They’re managed the same and run the same apps. Educators tell us that the smaller and lighter form of the tablet and no built-in mouse or keyboard changes how they and students use the device. For example: ● Many schools use tablets in early elementary, special education, and media classes where entering text, typing, and testing are less prevalent. ● Tablets are more conducive to handwriting notes, reading, filming, photography, and touchscreen apps than traditional laptops. ● Some schools prefer to use Android apps with tablets (because they’re designed for touchscreens) instead of using websites (usually designed for a mouse). This guide aims to help you adapt your apps to support these differences. Best practice 1: Google Drive integration One of the things that has made Chromebooks and Chromebook tablets so successful in schools over the years is that students can sign in to any device and access their files anywhere, anytime—such is the nature of the web! Android apps tend to work a little differently because they run natively (offline).
    [Show full text]
  • VPAT™ for Apple Ipad Pro (12.9-Inch)
    VPAT™ for Apple iPad Pro (12.9-inch) The following Voluntary Product Accessibility information refers to the Apple iPad Pro (12.9-inch) running iOS 9 or later. For more information on the accessibility features of the iPad Pro and to learn more about iPad Pro features, visit http://www.apple.com/ipad- pro and http://www.apple.com/accessibility iPad Pro (12.9-inch) referred to as iPad Pro below. VPAT™ Voluntary Product Accessibility Template Summary Table Criteria Supporting Features Remarks and Explanations Section 1194.21 Software Applications and Operating Systems Not applicable Section 1194.22 Web-based Internet Information and Applications Not applicable Does not apply—accessibility features consistent Section 1194.23 Telecommunications Products Please refer to the attached VPAT with standards nonetheless noted below. Section 1194.24 Video and Multi-media Products Not applicable Does not apply—accessibility features consistent Section 1194.25 Self-Contained, Closed Products Please refer to the attached VPAT with standards nonetheless noted below. Section 1194.26 Desktop and Portable Computers Not applicable Section 1194.31 Functional Performance Criteria Please refer to the attached VPAT Section 1194.41 Information, Documentation and Support Please refer to the attached VPAT iPad Pro (12.9-inch) VPAT (10.2015) Page 1 of 9 Section 1194.23 Telecommunications products – Detail Criteria Supporting Features Remarks and Explanations (a) Telecommunications products or systems which Not applicable provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non-acoustic connection point for TTYs. Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use.
    [Show full text]
  • Lexia Core5 Tech Reqs
    EXPANDED Lexia Customer Support SYSTEM 21 LEVELS [email protected] US: 800-507-2772; Outside US: 978-405-6231 System Requirements Web Version: www.lexiacore5.com For all browsers and platforms REQUIREMENTS Operating Systems and Browsers • Headsets (recommended) 1024x768 screen resolution (recommended) MacOS • • 10.12+ • 4 GB RAM (recommended), 2 GB (minimum) • Chrome 64+, Safari 10+, Firefox 62+ • Javascript must be enabled Persistent Internet connection (required) Windows • • Windows 7+ • Bandwidth: A typical student consumes 15MB of • Chrome 64+, Edge 44+, Firefox 62+ bandwidth per 5-min block (average rate ~0.4 Mbps). A classroom of 25 students consumes 750MB of band- Google Chrome OS width per 30-min session (average rate ~3.33 Mbps). 74+ • Bandwidth need is typically higher just after students • Chromebook, Chromebook Touchscreen log in and decreases after a few minutes of use. A 6MB download occurs upon logging into the Core5 product. iPad Version • iPad 4+, iPad Mini 3+, iPad Air+, iPad Pro (iOS 10+) • 1.9 GB storage space (1.65 GB for initial download) • Persistent Internet connection (minimal bandwidth is used) myLexia.com (the educator website) myLexia for iOS Chrome 64+, Edge 44+, Firefox 62+, Safari 11+ • iPhone, and iPod Touch with iOS 11.0+ • Apple Watch with watchOS 4.0+ Whitelisting, Firewall, Proxies, Content Filtering—Allow Access https://*.mylexia.com http://www.lexiacore5.com .salesforceliveagent.com (required only to use myLexia Support Chat) Note: Thin clients, Citrix, Terminal Services/Remote Desktop, virtual machines, and other remote access or PC-sharing systems are not supported. P-C5-21-SYS-0919 © 2019 Lexia Learning, a Rosetta Stone Company.
    [Show full text]
  • Chromebooks + Chromecast in the Classroom
    CHROMEBOOKS + CHROMECAST IN THE CLASSROOM As more Chromebook™ models enter the market, it’s becoming harder for schools to choose the best one to meet their needs. Which one has the power to run the latest online educational content such as Kno™ online textbooks and BioDigital Human™? Which one offers the best visual experience when using Chromecast™ in the classroom? Each model delivers a different experience for teachers teaching and students learning in the classroom. Here in the Principled Technologies labs, we put on our teacher hats and looked at an Intel® Core™ i3 processor-powered Chromebook and an ARM® processor-based Chromebook. We performed tasks a science teacher might include while giving a lesson in the classroom, such as using a Kno online textbook and looking at different 3D anatomy models in BioDigital Human. We measured aspects of user experience that would matter to students and teachers—time to complete tasks and frame rate. Which Chromebook is the better choice for teaching in the classroom? We found that the Intel Core i3 processor-powered Chromebook outperformed the ARM processor-based Chromebook across the board, delivering up to 250.0 percent more frames per second than the ARM processor-based Chromebook when using BioDigital Human with Chromecast. The Intel Core i3 processor-powered Chromebook also took just over half the time to complete a series of tasks, including opening BioDigital Human over 22 seconds faster than the ARM processor-based Chromebook. OCTOBER 2014 A PRINCIPLED TECHNOLOGIES TEST REPORT Commissioned by Intel Corp. WHICH PROCESSOR IS IN YOUR CHROMEBOOK? There are many different Chromebooks on the market.
    [Show full text]
  • How to Setup Your New Chromebook
    How to setup your new Chromebook Turn on Chromebook, allow it to power up. This is the first screen. Click “ Let’s Go” Select your WIFI network, enter your WIFI password (If requested), Select “ Next” 2 Read thru Google Chrome OS Terms (Choose the System security setting, yes or no) then Click “ Accept and Continue” The Chromebook will check for latest updates 3 Sign in with your Gmail Account and select “Next” or Click “More Options” and select “Create Account” SKIP if you have entered a Gmail Account already Type in your first and last name than select “Next” 4 SKIP if you have entered a Gmail Account already Enter birthday and the gender you identify with then select “Next” SKIP if you have entered a Gmail Account already Chose one of the three (3) options to create your new Gmail address then select “Next” 5 SKIP if you have entered a Gmail Account already Create an unique password than select “Next” SKIP if you have entered a Gmail Account already Add a phone number, if you choose. Scroll to bottom of the page 6 SKIP if you have entered a Gmail Account already Select one of the three: “More Options”, “Skip” or “Yes I’m in” SKIP if you have entered a Gmail Account already Review the information you entered and select “Next” 7 Allow Chromebook to finish creating your new account. Select Google options and select “Accept and continue” 8 Read thru Google Play apps and services and select “More” Read thru Google Play apps and services and select “Accept” 9 If you entered a previous Gmail account, it will as you if you want to install any associated apps, otherwise it will say The list of Apps cannot be loaded.
    [Show full text]
  • Adriane-Manual – Wikibooks
    Adriane-Manual – Wikibooks Adriane-Manual Notes to this wikibook Target group: Users of the ADRIANE (http://knopper.net/knoppix-adriane /)-Systems as well as people who want to install the system, configure or provide training to. Learning: The user should be enabled, to use the system independently and without sighted assistance and to work productively with the installed programs and services. This book is a "reference book" for a user in which he takes aid to individual tasks. The technician will get instructions for the installation and configuration of the system, so that he can configure it to meet the needs of the user. Trainers should be enabled to understand easily and to explain the system to users so that they can learn how to use it in a short time without help. Contact: Klaus Knopper Are Co authors currently wanted? Yes, in prior consultation with the contact person to coordinate the writing of individual chapters, please. Guidelines for co authors: see above. A clear distinction would be desirable between 'technical part' and 'User part'. Topic description The user part of the book deals with the use of programs that are included with Adriane, as well as the operation of the screen reader. The technical part explains the installation and configuration of Adriane, especially the connection of Braille lines, set-up of internet access, configuration of the mail program etc. Inhaltsverzeichnis 1 Introduction 2 Working with Adriane 2.1 Start and help 2.2 Individual menu system 2.3 Voice output functions 2.4 Programs in Adriane 2.4.1
    [Show full text]
  • Vizlens: a Robust and Interactive Screen Reader for Interfaces in The
    VizLens: A Robust and Interactive Screen Reader for Interfaces in the Real World Anhong Guo1, Xiang ‘Anthony’ Chen1, Haoran Qi2, Samuel White1, Suman Ghosh1, Chieko Asakawa3, Jeffrey P. Bigham1 1Human-Computer Interaction Institute, 2Mechanical Engineering Department, 3Robotics Institute Carnegie Mellon University, 5000 Forbes Ave, Pittsburgh, PA 15213 fanhongg, xiangche, chiekoa, jbighamg @cs.cmu.edu, fhaoranq, samw, sumangg @andrew.cmu.edu ABSTRACT INTRODUCTION The world is full of physical interfaces that are inaccessible The world is full of inaccessible physical interfaces. Mi­ to blind people, from microwaves and information kiosks to crowaves, toasters and coffee machines help us prepare food; thermostats and checkout terminals. Blind people cannot in­ printers, fax machines, and copiers help us work; and check­ dependently use such devices without at least first learning out terminals, public kiosks, and remote controls help us live their layout, and usually only after labeling them with sighted our lives. Despite their importance, few are self-voicing or assistance. We introduce VizLens —an accessible mobile ap­ have tactile labels. As a result, blind people cannot easily use plication and supporting backend that can robustly and inter­ them. Generally, blind people rely on sighted assistance ei­ actively help blind people use nearly any interface they en­ ther to use the interface or to label it with tactile markings. counter. VizLens users capture a photo of an inaccessible Tactile markings often cannot be added to interfaces on pub­ interface and send it to multiple crowd workers, who work lic devices, such as those in an office kitchenette or check­ in parallel to quickly label and describe elements of the inter­ out kiosk at the grocery store, and static labels cannot make face to make subsequent computer vision easier.
    [Show full text]
  • Chrome OS Based Devices in the Enterprise
    White Paper Client Virtualization Enterprise Mobility Chrome OS based devices in the Enterprise 2015 Edition Executive Summary According to IDC, 4.6 million Chromebooks were sold in 2014, roughly twice as many as in 2013. And Chromebook sales are expected to reach 14.4 million units by 2017 according to Gartner¹. Most of the Chromebooks are currently sold into the U.S. education sector. The adoption of Chrome OS devices in the Enterprise is by far slower. This might be related to concerns regarding application availability, manageability & security and the complexity of adopting yet another platform to the IT infrastructure. There may also exist reservations in regard to hosting business data in the public cloud. But Chrome OS devices may also be used for accessing non-public cloud based applications & data and even legacy apps. The latter has been recently enabled by joint ventures of Google & VMware and Citrix who announced Chrome OS support for their application and desktop virtualization technologies. Having the ability to access Windows applications from a Chrome OS Client significantly increases the versatility of those devices. Business customers now basically have three ways of utilizing Chrome OS (see also table 1). Google Chrome Apps for Business, Android Apps and Web Apps This is the “classical” Google solution Chrome OS clients can run three for business. Utilizing Google Apps for different kinds of applications: Web Business and other Web applications, apps, which run in the Chrome web like salesforce.com for example browser and typically only work when provides businesses with a cloud connected to the Internet, Chrome based working environment that suits apps, which are stored on the device many companies’ IT requirements and and can often be used in offline mode scales from a few users up to 10.000’s and more recently also Android Apps.
    [Show full text]
  • Enabling TLS 1.2 in Major Browsers
    Enabling TLS 1.2 in Major Browsers Table of Contents Updating Microsoft Internet Explorer ...................................................................................................................................................... 2 Enabling or Disabling TLS Protocols in Internet Explorer .................................................................................................................... 2 Updating Mozilla Firefox ........................................................................................................................................................................... 3 Enabling or Disabling TLS Protocols in Firefox .................................................................................................................................... 4 Updating Google Chrome ......................................................................................................................................................................... 5 Enabling or Disabling TLS Protocols in Chrome .................................................................................................................................. 5 Updating Apple Safari ............................................................................................................................................................................... 7 Enabling or Disabling TLS Protocols in Apple Safari ............................................................................................................................ 7 Appendix
    [Show full text]
  • VERSE: Bridging Screen Readers and Voice Assistants for Enhanced
    VERSE: Bridging Screen Readers and Voice Assistants for Enhanced Eyes-Free Web Search Alexandra Vtyurina∗ Adam Fourney Meredith Ringel Morris University of Waterloo Microsoft Research Microsoft Research Waterloo, Ontario, Canada Redmond, WA, USA Redmond, WA, USA [email protected] [email protected] [email protected] Leah Findlater Ryen W. White University of Washington Microsoft Research Seattle, WA, USA Redmond, WA, USA [email protected] [email protected] ABSTRACT INTRODUCTION People with visual impairments often rely on screen readers People with visual impairments are often early adopters of when interacting with computer systems. Increasingly, these audio-based interfaces, with screen readers being a prime individuals also make extensive use of voice-based virtual example. Screen readers work by transforming the visual assistants (VAs). We conducted a survey of 53 people who are content in a graphical user interface into audio by vocalizing legally blind to identify the strengths and weaknesses of both on-screen text. To this end, they are an important accessibility technologies, and the unmet opportunities at their intersection. tool for blind computer users – so much so that every major We learned that virtual assistants are convenient and accessible, operating system includes screen reader functionality (e.g., but lack the ability to deeply engage with content (e.g., read VoiceOver1, TalkBack2, Narrator3), and there is a strong mar- beyond the frst few sentences of an article), and the ability ket for third-party offerings (e.g., JAWS4, NVDA5). Despite to get a quick overview of the landscape (e.g., list alternative their importance, screen readers have many limitations.
    [Show full text]