[CATO] Help with testing Chromebooks for accessibility

Fri Jun 2 09:52:55 PDT 2023

Hi Zach,

I personally have very little experience with Chromebooks and they were not used often by students at TCC while I was there either.

This morning I sent an email to KC Merchant, who is the Digital Equity Program Supervisor at OSPI to see if he has any insight to share from the k-12 perspective. I included you in that message. Hope we hear from him!

Monica

[Title: SBCTC logo - Description: Compass]

Monica M. Olsson (she/her/hers)

Policy Associate – Accessible IT Coordinator

Washington State Board for Community and Technical Colleges

•Email: molsson at sbctc.edu<mailto:molsson at sbctc.edu> • Phone: 360-704-3922

The power of the Web is in its universality.
Access by everyone regardless of disability is an essential aspect.

Tim Berners-Lee, W3C Director and inventor of the World Wide Web

[cid:58a1abd0-ceb0-4950-a188-30301bf93d22]<https://outlook.office.com/bookwithme/user/321a279c65664c04a18fa34a96e959ab@sbctc.edu?anonymous&ep=signature>                Book time to meet with me<https://outlook.office.com/bookwithme/user/321a279c65664c04a18fa34a96e959ab@sbctc.edu?anonymous&ep=signature>
________________________________
From: CATO <cato-bounces at lists.ctc.edu> on behalf of Fauth, Bryan via CATO <cato at lists.ctc.edu>
Sent: Thursday, June 1, 2023 3:11 PM
To: Distribution List for the Committee for Accessible Technology Oversight <cato at lists.ctc.edu>
Cc: Fauth, Bryan <bfauth at cascadia.edu>
Subject: Re: [CATO] Help with testing Chromebooks for accessibility

[Sent from outside SBCTC]

Hi Zach,

That is definitely a lot to deal with! Cascadia does loan out Chromebooks to students. I believe it is only a small amount, most of the laptops we have available for students are PCs. Would you like me to forward this to my IT folks?

Best,

Bryan Fauth, M.S.

Director of Accessibility & Student Support Services

Preferred Pronouns: he/him/his

Phone: 425.352.8261

Email: bfauth at cascadia.edu

Student Accessibility Services Webpage<https://www.cascadia.edu/advising/accessibility.aspx>

[cid:image001.png at 01CFE88C.BD3FE360]

Image: Cascadia College Logo

The information contained in this e-mail message may be privileged, confidential, and protected from disclosure.  If you are not the intended recipient, any dissemination, distribution or copying of the contents of this message is strictly prohibited. If you think you received this message in error, please delete the message and e-mail the sender at bfauth at cascadia.edu<mailto:bfauth at cascadia.edu>

From: CATO <cato-bounces at lists.ctc.edu> On Behalf Of Lattin, Zachary via CATO
Sent: Wednesday, May 31, 2023 10:30 AM
To: cato at lists.ctc.edu
Cc: Lattin, Zachary <ZLattin at clark.edu>
Subject: [CATO] Help with testing Chromebooks for accessibility

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you validate the sender and know the content is safe. If you are unsure, contact the Help Desk at 2-8228 or email helpdesk at cascadia.edu<mailto:helpdesk at cascadia.edu>.

Good morning CATO,

Do you have time to help me (and all of us,) out?  Want to get your hands dirty with some assistive technology?

I am being asked to evaluate Chromebooks for use in  Clark College's IT infrastructure.  I am feeling a lot of pressure, especially given Chromebooks' history of being inaccessible and given the scope of what an actually thorough and professional evaluation like this involves.  Because Chromebook accessibility or lack thereof impacts all of us, I figured I would ask CATO for help.  At my CIO"s recommendation, I recently reached out to several institutions who use Chromebooks and it seems those institutions were unaware of or didn't test for accessibility before adopting Chromebooks.  Here is a rough outline of how I plan to go about this testing:

  *   Research existing Chromebook accessibility documentation and find recent user stories from AT users who regularly use the devices
  *   Verify that all built-in assistive technologies are compatible with Google suite, and adequate and functional for a user in 2023
  *   Test out screen magnification and make sure it is adequate
  *   Test switch access and insure compatibility with common hardware switches
  *   Test voice-control (Dragon-like functionality) and insure that user experience is consistent.  Test with device mic and some common headset mics.
  *   Verify that using Chromevox is comparable to using a screen-reader like Jaws or NVDA and verify that the Google Suite is functionally accessible with Chromevox
  *   Verify claims that braille support (including UEB and Nemeth support) has been improved and works consistently across the Google suite of apps.  Verify that braille support works with common braille display hardware.
  *   Finalize an assistive technology training plan for AT users who have Chromebooks and wish to be trained to access Clark resources with them.
  *   Align all of the above with Revised Sec. 508 functional accessibility requirements or with WCAG wherever applicable

Here are a couple of asterisks:

  *   Clark is not considering the arm architectured Chromebooks, only the Intel I5s and i7s
  *   At this time Clark is not interested in touchscreen functionality

I haven't brought this up with CATO leadership or asked to have it on the agenda or anything, just feeling stressed and asking for some support.  I could use any help at all with this!  I'd be glad to chat about it at the June CATO meeting though.

Thank you,

--Zach

Campus IT Accessibility Coordinator and Assistive Technology Specialist

IT Services

Phone (call or text): (360) 992-2016

Email: zlattin at clark.edu<mailto:zlattin at clark.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ctc.edu/pipermail/cato_lists.ctc.edu/attachments/20230602/4e0ed01c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-Title_ SBC.png
Type: image/png
Size: 22672 bytes
Desc: Outlook-Title_ SBC.png
URL: <http://lists.ctc.edu/pipermail/cato_lists.ctc.edu/attachments/20230602/4e0ed01c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-gugjnphj.png
Type: image/png
Size: 528 bytes
Desc: Outlook-gugjnphj.png
URL: <http://lists.ctc.edu/pipermail/cato_lists.ctc.edu/attachments/20230602/4e0ed01c/attachment-0003.png>