\n\n\n\n
Key Points and Actions<\/h2>\n\n\n\n
The webinar, presented by Carolyn Quintero (Manager of Web Accessibility on the University Web Strategy team at Boise State), focused on a proactive strategy to ensure all university data in Google Sheets is accessible, not just for external compliance, but for all users.<\/p>\n\n\n\n
Key Requirements & Deadlines<\/h3>\n\n\n\n\n- Legal Mandate:<\/strong> All digital content, including password-protected files in Google Drive, must meet WCAG 2.1 Level AA<\/strong> standards.<\/li>\n\n\n\n
- Compliance Deadline:<\/strong> The absolute deadline for achieving full compliance with the new guidelines is April 2027<\/strong>.<\/li>\n<\/ul>\n\n\n\n
The Three-Step Action Plan (Sheets Review)<\/h3>\n\n\n\n\n- Remove:<\/strong> Eliminate any outdated or unnecessary Google Sheets.<\/li>\n\n\n\n
- Replace:<\/strong> Convert necessary content into more accessible file formats if feasible.<\/li>\n\n\n\n
- Remediate:<\/strong> Use the Grackle for Google Sheets<\/strong> add-on to fix accessibility barriers in essential sheets.<\/li>\n<\/ol>\n\n\n\n
Key Remediation Actions<\/h3>\n\n\n\n\n- Structure:<\/strong> Properly format tables with headers, use descriptive sheet names, and give the document a proper title.<\/li>\n\n\n\n
- Visuals:<\/strong> Add alternative text<\/strong> to all charts and images, and use the contrast checker to ensure sufficient color contrast<\/strong>.<\/li>\n\n\n\n
- Content:<\/strong> Fix readability issues like fine print<\/strong> (text below 8-point font) and avoid merged cells<\/strong>.<\/li>\n<\/ul>\n\n\n\n
Final Takeaway<\/h3>\n\n\n\n
While automated tools like Grackle are essential, true accessibility requires human intervention<\/strong> (clear language, descriptive links, logical reading order) and proactively seeking feedback<\/strong> from users of assistive technology.<\/p>\n\n\n\n
\n\n\n\n<\/div>\n\n\n\nSummary and Annotated Outline<\/h2>\n\n\n\n
Carolyn Quintero, Manager of Web Accessibility on the University Web Strategy team, presented a webinar on making Google Sheets accessible using Grackle for Google Sheets. The session focused on ensuring data accessibility for all university community members as part of Boise State’s broader web strategy.<\/p>\n\n\n\n
Carolyn began by explaining the importance of accessibility beyond mere compliance, emphasizing that accessibility should work for both content creators and end users. She introduced additional campus resources including Christine Dobson (Digital Accessibility Compliance Officer) and Jeremy Harper (for faculty support with course materials).<\/p>\n\n\n\n
The presentation covered the legal requirements under Title II of the Americans with Disabilities Act, noting that new digital accessibility guidelines were published on April 24, 2024, with a compliance deadline of April 2027. These guidelines require all digital content to meet WCAG 2.1 Level AA standards, including password-protected content in systems like Google Drive.<\/p>\n\n\n\n
Carolyn outlined a decision framework for reviewing Google Sheets: remove outdated content, replace content with more accessible formats when possible, or remediate sheets that must remain in their current format. She then provided a detailed walkthrough of using Grackle for Google Sheets to identify and fix accessibility issues.<\/p>\n\n\n\n
The demonstration covered several key accessibility areas: fixing fine print (text below 8-point font), ensuring proper color contrast, adding alternative text to charts and images, properly formatting tables with headers, avoiding merged cells, using descriptive sheet names, and giving documents proper titles. Carolyn emphasized that while Grackle is a helpful tool, it requires human intervention to ensure true accessibility.<\/p>\n\n\n\n
The session concluded with additional considerations beyond automated checking, including making links descriptive, using clear language, ensuring logical reading order, and considering cognitive load. Carolyn encouraged proactively seeking feedback from users of assistive technology rather than waiting for complaints.<\/p>\n\n\n\nWant to jump to a specific section of the video? Here’s the Annotated Outline<\/summary>\n\n- Introduction & Housekeeping (0:00-1:30)<\/li>\n\n\n\n
- Speaker Introduction and Campus Resources (1:30-4:27)<\/li>\n\n\n\n
- Legal Requirements and Compliance Deadlines (4:27-7:37)<\/li>\n\n\n\n
- Decision Framework for Google Sheets (7:37-10:00)<\/li>\n\n\n\n
- Introduction to Grackle for Google Sheets (10:00-11:48)<\/li>\n\n\n\n
- Addressing Fine Print Issues (11:48-15:01)<\/li>\n\n\n\n
- Ensuring Color Contrast (15:01-20:38)<\/li>\n\n\n\n
- Adding Alternative Text to Charts and Images (20:38-26:17)<\/li>\n\n\n\n
- Formatting Tables for Accessibility (26:17-37:13)<\/li>\n\n\n\n
- Ensuring Descriptive Names (37:13-42:05)<\/li>\n\n\n\n
- Accessibility Beyond Automated Checking (42:05-45:26)<\/li>\n\n\n\n
- Q & A (45:26-end of webinar)<\/li>\n<\/ol>\n<\/details>\n\n\n\n
\n\n\n\n<\/div>\n\n\n\nFull Text Transcript<\/h2>\n\n\n\nExpand to access the full text transcript<\/summary>\nI. Introduction and Housekeeping<\/h3>\n\n\n\n
Welcome, everybody! Very excited to talk to you today about Grackle for Google Sheets, making your data accessible. So this is a crucial part of our broader university web strategy, and it’s all about ensuring that the data we create and share is usable by every member of our community.<\/p>\n\n\n\n
Housekeeping<\/h4>\n\n\n\n\n- First of all, please, if you haven’t already, mute your microphones. This will help limit background noise as we go through today.<\/li>\n\n\n\n
- We are recording this session. I will make it available on the Boise State Accessibility site on the on-demand webinars<\/a> page.<\/li>\n\n\n\n
- If you do have questions, we will try our best to answer them at the end of the session. I’ve tried to leave some time at the end, but if we run out of time. We will still answer your questions and include them on that page with the webinar recording.<\/li>\n\n\n\n
- So if you have questions, please add them to chat, and my wonderful assistant, Ciera Garechana, will, collect all those, and we will answer those at the end.<\/li>\n\n\n\n
- If you have any questions, or need assistance, you can also directly message her.<\/li>\n\n\n\n
- We also have a resource available on the Boise State Accessibility website specific for Grackle Sheets. So if you go to Boise State Accessibility on the Resources and Tutorials<\/a> page, you will find all of these resources and more. <\/li>\n<\/ul>\n\n\n\n
II. Presenter and Campus Support<\/h3>\n\n\n\n
My name is Carolyn Quintero, and I am the Manager of Web Accessibility on the University Web Strategy team. I’ve helped guide the institution’s digital compliance and inclusion efforts specifically for our public-facing web content since 2017. My educational background includes a Master of Arts in Technical Communication and a Bachelor of Arts in Communications, both earned at Boise State University. My approach to accessibility is not just compliance. I think of accessibility as a critical element, ensuring every step in the content process works for everyone. So it has to work for our content creators as well as our end users.<\/p>\n\n\n\n
Additional Campus Support<\/h4>\n\n\n\n
I’m not the only resource available on campus to help with this huge topic. We do have additional support available for campus in our Office of Compliance and Ethics.<\/p>\n\n\n\n
\n- Christine Dobson (Digital Accessibility Compliance Officer):<\/strong> Contact her at accessibility@boisestate.edu or 208-426-1256. This support is for questions about the new accessibility requirements, scheduling compliance staff to explain regulations and provide basic accessibility training. They can answer compliance questions, do software testing, and answer general accessibility questions.<\/li>\n\n\n\n
- Jeremy Harper (Community Engagement and Belonging):<\/strong> Contact them at belonging@boisestate.edu or 208-426-6156. This support is for faculty support with making course materials accessible, including requesting a course review.<\/li>\n<\/ul>\n\n\n\n
III. Legal Commitment and Compliance<\/h3>\n\n\n\n
Our commitment to accessibility is rooted in legal compliance, specifically Title II of the Americans with Disabilities Act<\/strong>.<\/p>\n\n\n\n\n- New Guidelines & Deadline:<\/strong> The new digital accessibility guidelines were published on April 24th of 2024<\/strong>. The deadline for meeting the WCAG 2.1 level AA standards<\/strong> is April 24th of 2026<\/strong>.<\/li>\n\n\n\n
- Scope:<\/strong> These guidelines require that all of our digital content<\/strong>\u2014including websites, apps, digital documents, presentations, and course materials\u2014must be accessible. This even covers content stored in password-protected systems, like My Boise State, Canvas, or specifically Google Drive.<\/li>\n<\/ul>\n\n\n\n
Shifting to the Anticipating Model<\/h4>\n\n\n\n\n- Current (Accommodating) Model:<\/strong> This model is much more reactive. A user has to report a barrier and request access. That can lead to time delays, frustration, and lost engagement. And in the worst case scenario, the barrier is never fixed.<\/li>\n\n\n\n
- Goal (Anticipating) Model:<\/strong> The anticipating model is proactive<\/strong>, where we empower ourselves to build for accessibility from the start. This leads to fewer delays, less mental effort for the user, and a higher likelihood of engagement. We want to remove those barriers before they ever even become an issue.<\/li>\n<\/ul>\n\n\n\n
IV. The Decision Framework: Remove, Replace, or Remediate<\/h3>\n\n\n\n
Our goal for this month is to review our Google Sheets<\/strong> and make a decision for each one. Think of your files as going into one of these three buckets:<\/p>\n\n\n\n\n- Remove:<\/strong> The question to ask is: Do we still need this sheet? Is the information current? Is the information accurate? The recommended action is to remove the link, unshare the sheet, and then archive as needed for your department.<\/li>\n\n\n\n
- Replace:<\/strong> The question to ask is: Is this the best format for this content? Could you move it to another format, like a web page, or maybe even a web form? The recommended action is to convert that content to the other format, remove that web link and archive as needed.<\/li>\n\n\n\n
- Remediate:<\/strong> The question to ask is: Do your users require the version of this sheet (e.g., a template, or required for their job)? The recommended action is to make a copy<\/strong> of your content, run Grackle Sheets, fix your issues, and then share that accessible version with your audience.<\/li>\n<\/ul>\n\n\n\n
V. Grackle Sheets: Remediation Walkthrough<\/h3>\n\n\n\n
Grackle Sheets is an accessibility checker for Google Sheets. Google Sheets does not have a native accessibility checker, so Grackle Sheets is a third-party add-on that is available within every single Google Sheet.<\/p>\n\n\n\n
\n- To Access:<\/strong> Open your sheet, go to Extensions > Grackle Sheets > Launch<\/strong>.<\/li>\n\n\n\n
- Report Categories:<\/strong> The report is broken into five categories: Sheets, Tables, Images, Charts, and Contents<\/strong>.<\/li>\n\n\n\n
- Recommended Workflow:<\/strong> It’s actually better to work backwards<\/strong> from that more granular view. Fix Contents<\/strong> first, then Charts\/Images<\/strong>, then Tables<\/strong>, and finally Sheets<\/strong>.<\/li>\n<\/ul>\n\n\n\n
1. Contents: Fine Print and Color Contrast<\/h4>\n\n\n\n\n- Fine Print:<\/strong> This is flagged when anything is below 8-point font<\/strong>. The fix is to change font size to 10 or higher<\/strong> (12-point is ideal). Tips to avoid this include simplifying your wording, using bullet points, widening your columns, or using the text wrapping tool. For complex notes, consider moving lengthy notes to their own sheet to allow for more space, or use descriptive cell notes<\/strong> for specific data points.<\/li>\n\n\n\n
- Color Contrast:<\/strong> The report checks for text that is not using a high contrast color. The recommended tool is to manually verify colors using the Color Contrast Checker<\/strong> at colourcontrast.cc<\/a>. Warning:<\/strong> Anytime you have color in your sheet, always do a manual review<\/strong>, because Grackle Sheets may not pull in conditional formatting colors. Tip:<\/strong> Do not use color alone<\/strong> to indicate a value or change. You have to provide something else, like a plus or minus sign, to accompany the color.<\/li>\n<\/ul>\n\n\n\n
2. Images and Charts (Alt Text)<\/h4>\n\n\n\n\n- Charts:<\/strong> Charts require an alternative text description<\/strong>. Alt Text Tips include stating the chart type and purpose, providing a good summary of the key takeaways<\/strong>, and you can also direct the user to the underlying data table. The Chart Editor Tool can be used to add accessibility features like horizontal and vertical axis titles, data labels, and adjusting colors\/patterns.<\/li>\n\n\n\n
- Images:<\/strong> If the image conveys information, be concise but descriptive<\/strong> and convey the context and function. If the image is purely decorative<\/strong> (eye candy) with no information shared, use the Grackle Sheets option to mark as an artifact<\/strong> to tell screen readers to skip this image.<\/li>\n<\/ul>\n\n\n\n
3. Tables<\/h4>\n\n\n\n\n- Headers:<\/strong> Tables must be programmatically tagged with headers. The fix is to convert your content to a Table<\/strong> using Format > Convert to Table<\/strong> (or Ctrl-Alt-T). Then, use Grackle Sheets to mark the table with a header row, header column, or both.<\/li>\n\n\n\n
- Merged\/Isolated Cells:<\/strong> Avoid merged or isolated cells, as they confuse non-visual navigation. The fix is to use the Unmerge tool in Grackle Sheets to quickly unmerge all cells.<\/li>\n\n\n\n
- Table Length:<\/strong> The check for “tables should not be too long” will require human review<\/strong>. If the table has a logical break, split it into smaller tables. Tips include keeping tables simple, using a single clear row of header cells, and do not merge or isolate cells.<\/li>\n<\/ul>\n\n\n\n
4. Sheets (Metadata and Structure)<\/h4>\n\n\n\n\n- Descriptive Naming (The Final Check):<\/strong> Manually check that your document has a descriptive title<\/strong> (not just “Copy of Untitled 1”). Change generic sheet names<\/strong> (Sheet 1, Sheet 2) to descriptive names (e.g., “Quarterly Sales,” “Contact Info”). Also, check that sheets are not empty and are not too large.<\/li>\n<\/ul>\n\n\n\n
VI. Compliance Beyond Automated Checkers<\/h3>\n\n\n\n
Accessibility checkers are a good starting point but require human intervention.<\/p>\n\n\n\n
\n- Links:<\/strong> Make links descriptive<\/strong> (e.g., not “click here”).<\/li>\n\n\n\n
- Language:<\/strong> Use clear, simple language<\/strong>. Check for readability.<\/li>\n\n\n\n
- Logical Reading Order:<\/strong> Use the Tab key<\/strong> to navigate the sheet. If you can’t access all information, or if the order is confusing, reorder the content.<\/li>\n\n\n\n
- Cognitive Load:<\/strong> Prioritize clarity and simplicity<\/strong>.<\/li>\n\n\n\n
- User Feedback:<\/strong> Proactively seek feedback<\/strong> from users of assistive technology (the Anticipation Model). Don’t wait for complaints.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nVII. Q&A Summary<\/h3>\n\n\n\n\n- All Content Required to be Accessible?<\/strong> All sheets, including those used only by employees, must be made accessible under the updated guidance. This is to support employees who require accessible content and to build good habits.<\/li>\n\n\n\n
- Boise State Brand Colors Accessible?<\/strong> All brand standard colors have been checked for contrast ratios. The website uses a specific digital orange. Some colors are labeled as print-only<\/strong> because they are not digitally accessible.<\/li>\n\n\n\n
- Chart Legends Location?<\/strong> There is no hard rule on placement, but follow chart conventions for readability (most are on the right-hand side).<\/li>\n\n\n\n
- How Long is Too Long for a Table?<\/strong> There is no hard and fast rule; the warning is a “pass with warning” requiring human review. Use your best judgment. If the table has a logical break, split it into smaller tables.<\/li>\n\n\n\n
- Heading Size on webpages?<\/strong> (Regarding a separate question on WordPress headings) I don’t have a specific answer for that one yet. You’re talking about, like, our heading size. I believe, and I don’t think there has been any discussion on changing that at the moment, but if you wanted to follow up with me separately, we could take a look at your project and see, is there something that we could do to maybe adjust the way it’s presented on the page, or maybe change using one of our different block themes? Or block styling that we have available to meet your needs, because I know we’ve got some constraints in our web designs, but we may be able to adjust it a little bit based on your specific needs.<\/li>\n<\/ul>\n<\/details>\n\n\n\n
\n\n\n\n
The Three-Step Action Plan (Sheets Review)<\/h3>\n\n\n\n\n- Remove:<\/strong> Eliminate any outdated or unnecessary Google Sheets.<\/li>\n\n\n\n
- Replace:<\/strong> Convert necessary content into more accessible file formats if feasible.<\/li>\n\n\n\n
- Remediate:<\/strong> Use the Grackle for Google Sheets<\/strong> add-on to fix accessibility barriers in essential sheets.<\/li>\n<\/ol>\n\n\n\n
Key Remediation Actions<\/h3>\n\n\n\n\n- Structure:<\/strong> Properly format tables with headers, use descriptive sheet names, and give the document a proper title.<\/li>\n\n\n\n
- Visuals:<\/strong> Add alternative text<\/strong> to all charts and images, and use the contrast checker to ensure sufficient color contrast<\/strong>.<\/li>\n\n\n\n
- Content:<\/strong> Fix readability issues like fine print<\/strong> (text below 8-point font) and avoid merged cells<\/strong>.<\/li>\n<\/ul>\n\n\n\n
Final Takeaway<\/h3>\n\n\n\n
While automated tools like Grackle are essential, true accessibility requires human intervention<\/strong> (clear language, descriptive links, logical reading order) and proactively seeking feedback<\/strong> from users of assistive technology.<\/p>\n\n\n\n
\n\n\n\n<\/div>\n\n\n\nSummary and Annotated Outline<\/h2>\n\n\n\n
Carolyn Quintero, Manager of Web Accessibility on the University Web Strategy team, presented a webinar on making Google Sheets accessible using Grackle for Google Sheets. The session focused on ensuring data accessibility for all university community members as part of Boise State’s broader web strategy.<\/p>\n\n\n\n
Carolyn began by explaining the importance of accessibility beyond mere compliance, emphasizing that accessibility should work for both content creators and end users. She introduced additional campus resources including Christine Dobson (Digital Accessibility Compliance Officer) and Jeremy Harper (for faculty support with course materials).<\/p>\n\n\n\n
The presentation covered the legal requirements under Title II of the Americans with Disabilities Act, noting that new digital accessibility guidelines were published on April 24, 2024, with a compliance deadline of April 2027. These guidelines require all digital content to meet WCAG 2.1 Level AA standards, including password-protected content in systems like Google Drive.<\/p>\n\n\n\n
Carolyn outlined a decision framework for reviewing Google Sheets: remove outdated content, replace content with more accessible formats when possible, or remediate sheets that must remain in their current format. She then provided a detailed walkthrough of using Grackle for Google Sheets to identify and fix accessibility issues.<\/p>\n\n\n\n
The demonstration covered several key accessibility areas: fixing fine print (text below 8-point font), ensuring proper color contrast, adding alternative text to charts and images, properly formatting tables with headers, avoiding merged cells, using descriptive sheet names, and giving documents proper titles. Carolyn emphasized that while Grackle is a helpful tool, it requires human intervention to ensure true accessibility.<\/p>\n\n\n\n
The session concluded with additional considerations beyond automated checking, including making links descriptive, using clear language, ensuring logical reading order, and considering cognitive load. Carolyn encouraged proactively seeking feedback from users of assistive technology rather than waiting for complaints.<\/p>\n\n\n\nWant to jump to a specific section of the video? Here’s the Annotated Outline<\/summary>\n\n- Introduction & Housekeeping (0:00-1:30)<\/li>\n\n\n\n
- Speaker Introduction and Campus Resources (1:30-4:27)<\/li>\n\n\n\n
- Legal Requirements and Compliance Deadlines (4:27-7:37)<\/li>\n\n\n\n
- Decision Framework for Google Sheets (7:37-10:00)<\/li>\n\n\n\n
- Introduction to Grackle for Google Sheets (10:00-11:48)<\/li>\n\n\n\n
- Addressing Fine Print Issues (11:48-15:01)<\/li>\n\n\n\n
- Ensuring Color Contrast (15:01-20:38)<\/li>\n\n\n\n
- Adding Alternative Text to Charts and Images (20:38-26:17)<\/li>\n\n\n\n
- Formatting Tables for Accessibility (26:17-37:13)<\/li>\n\n\n\n
- Ensuring Descriptive Names (37:13-42:05)<\/li>\n\n\n\n
- Accessibility Beyond Automated Checking (42:05-45:26)<\/li>\n\n\n\n
- Q & A (45:26-end of webinar)<\/li>\n<\/ol>\n<\/details>\n\n\n\n
\n\n\n\n<\/div>\n\n\n\nFull Text Transcript<\/h2>\n\n\n\nExpand to access the full text transcript<\/summary>\nI. Introduction and Housekeeping<\/h3>\n\n\n\n
Welcome, everybody! Very excited to talk to you today about Grackle for Google Sheets, making your data accessible. So this is a crucial part of our broader university web strategy, and it’s all about ensuring that the data we create and share is usable by every member of our community.<\/p>\n\n\n\n
Housekeeping<\/h4>\n\n\n\n\n- First of all, please, if you haven’t already, mute your microphones. This will help limit background noise as we go through today.<\/li>\n\n\n\n
- We are recording this session. I will make it available on the Boise State Accessibility site on the on-demand webinars<\/a> page.<\/li>\n\n\n\n
- If you do have questions, we will try our best to answer them at the end of the session. I’ve tried to leave some time at the end, but if we run out of time. We will still answer your questions and include them on that page with the webinar recording.<\/li>\n\n\n\n
- So if you have questions, please add them to chat, and my wonderful assistant, Ciera Garechana, will, collect all those, and we will answer those at the end.<\/li>\n\n\n\n
- If you have any questions, or need assistance, you can also directly message her.<\/li>\n\n\n\n
- We also have a resource available on the Boise State Accessibility website specific for Grackle Sheets. So if you go to Boise State Accessibility on the Resources and Tutorials<\/a> page, you will find all of these resources and more. <\/li>\n<\/ul>\n\n\n\n
II. Presenter and Campus Support<\/h3>\n\n\n\n
My name is Carolyn Quintero, and I am the Manager of Web Accessibility on the University Web Strategy team. I’ve helped guide the institution’s digital compliance and inclusion efforts specifically for our public-facing web content since 2017. My educational background includes a Master of Arts in Technical Communication and a Bachelor of Arts in Communications, both earned at Boise State University. My approach to accessibility is not just compliance. I think of accessibility as a critical element, ensuring every step in the content process works for everyone. So it has to work for our content creators as well as our end users.<\/p>\n\n\n\n
Additional Campus Support<\/h4>\n\n\n\n
I’m not the only resource available on campus to help with this huge topic. We do have additional support available for campus in our Office of Compliance and Ethics.<\/p>\n\n\n\n
\n- Christine Dobson (Digital Accessibility Compliance Officer):<\/strong> Contact her at accessibility@boisestate.edu or 208-426-1256. This support is for questions about the new accessibility requirements, scheduling compliance staff to explain regulations and provide basic accessibility training. They can answer compliance questions, do software testing, and answer general accessibility questions.<\/li>\n\n\n\n
- Jeremy Harper (Community Engagement and Belonging):<\/strong> Contact them at belonging@boisestate.edu or 208-426-6156. This support is for faculty support with making course materials accessible, including requesting a course review.<\/li>\n<\/ul>\n\n\n\n
III. Legal Commitment and Compliance<\/h3>\n\n\n\n
Our commitment to accessibility is rooted in legal compliance, specifically Title II of the Americans with Disabilities Act<\/strong>.<\/p>\n\n\n\n\n- New Guidelines & Deadline:<\/strong> The new digital accessibility guidelines were published on April 24th of 2024<\/strong>. The deadline for meeting the WCAG 2.1 level AA standards<\/strong> is April 24th of 2026<\/strong>.<\/li>\n\n\n\n
- Scope:<\/strong> These guidelines require that all of our digital content<\/strong>\u2014including websites, apps, digital documents, presentations, and course materials\u2014must be accessible. This even covers content stored in password-protected systems, like My Boise State, Canvas, or specifically Google Drive.<\/li>\n<\/ul>\n\n\n\n
Shifting to the Anticipating Model<\/h4>\n\n\n\n\n- Current (Accommodating) Model:<\/strong> This model is much more reactive. A user has to report a barrier and request access. That can lead to time delays, frustration, and lost engagement. And in the worst case scenario, the barrier is never fixed.<\/li>\n\n\n\n
- Goal (Anticipating) Model:<\/strong> The anticipating model is proactive<\/strong>, where we empower ourselves to build for accessibility from the start. This leads to fewer delays, less mental effort for the user, and a higher likelihood of engagement. We want to remove those barriers before they ever even become an issue.<\/li>\n<\/ul>\n\n\n\n
IV. The Decision Framework: Remove, Replace, or Remediate<\/h3>\n\n\n\n
Our goal for this month is to review our Google Sheets<\/strong> and make a decision for each one. Think of your files as going into one of these three buckets:<\/p>\n\n\n\n\n- Remove:<\/strong> The question to ask is: Do we still need this sheet? Is the information current? Is the information accurate? The recommended action is to remove the link, unshare the sheet, and then archive as needed for your department.<\/li>\n\n\n\n
- Replace:<\/strong> The question to ask is: Is this the best format for this content? Could you move it to another format, like a web page, or maybe even a web form? The recommended action is to convert that content to the other format, remove that web link and archive as needed.<\/li>\n\n\n\n
- Remediate:<\/strong> The question to ask is: Do your users require the version of this sheet (e.g., a template, or required for their job)? The recommended action is to make a copy<\/strong> of your content, run Grackle Sheets, fix your issues, and then share that accessible version with your audience.<\/li>\n<\/ul>\n\n\n\n
V. Grackle Sheets: Remediation Walkthrough<\/h3>\n\n\n\n
Grackle Sheets is an accessibility checker for Google Sheets. Google Sheets does not have a native accessibility checker, so Grackle Sheets is a third-party add-on that is available within every single Google Sheet.<\/p>\n\n\n\n
\n- To Access:<\/strong> Open your sheet, go to Extensions > Grackle Sheets > Launch<\/strong>.<\/li>\n\n\n\n
- Report Categories:<\/strong> The report is broken into five categories: Sheets, Tables, Images, Charts, and Contents<\/strong>.<\/li>\n\n\n\n
- Recommended Workflow:<\/strong> It’s actually better to work backwards<\/strong> from that more granular view. Fix Contents<\/strong> first, then Charts\/Images<\/strong>, then Tables<\/strong>, and finally Sheets<\/strong>.<\/li>\n<\/ul>\n\n\n\n
1. Contents: Fine Print and Color Contrast<\/h4>\n\n\n\n\n- Fine Print:<\/strong> This is flagged when anything is below 8-point font<\/strong>. The fix is to change font size to 10 or higher<\/strong> (12-point is ideal). Tips to avoid this include simplifying your wording, using bullet points, widening your columns, or using the text wrapping tool. For complex notes, consider moving lengthy notes to their own sheet to allow for more space, or use descriptive cell notes<\/strong> for specific data points.<\/li>\n\n\n\n
- Color Contrast:<\/strong> The report checks for text that is not using a high contrast color. The recommended tool is to manually verify colors using the Color Contrast Checker<\/strong> at colourcontrast.cc<\/a>. Warning:<\/strong> Anytime you have color in your sheet, always do a manual review<\/strong>, because Grackle Sheets may not pull in conditional formatting colors. Tip:<\/strong> Do not use color alone<\/strong> to indicate a value or change. You have to provide something else, like a plus or minus sign, to accompany the color.<\/li>\n<\/ul>\n\n\n\n
2. Images and Charts (Alt Text)<\/h4>\n\n\n\n\n- Charts:<\/strong> Charts require an alternative text description<\/strong>. Alt Text Tips include stating the chart type and purpose, providing a good summary of the key takeaways<\/strong>, and you can also direct the user to the underlying data table. The Chart Editor Tool can be used to add accessibility features like horizontal and vertical axis titles, data labels, and adjusting colors\/patterns.<\/li>\n\n\n\n
- Images:<\/strong> If the image conveys information, be concise but descriptive<\/strong> and convey the context and function. If the image is purely decorative<\/strong> (eye candy) with no information shared, use the Grackle Sheets option to mark as an artifact<\/strong> to tell screen readers to skip this image.<\/li>\n<\/ul>\n\n\n\n
3. Tables<\/h4>\n\n\n\n\n- Headers:<\/strong> Tables must be programmatically tagged with headers. The fix is to convert your content to a Table<\/strong> using Format > Convert to Table<\/strong> (or Ctrl-Alt-T). Then, use Grackle Sheets to mark the table with a header row, header column, or both.<\/li>\n\n\n\n
- Merged\/Isolated Cells:<\/strong> Avoid merged or isolated cells, as they confuse non-visual navigation. The fix is to use the Unmerge tool in Grackle Sheets to quickly unmerge all cells.<\/li>\n\n\n\n
- Table Length:<\/strong> The check for “tables should not be too long” will require human review<\/strong>. If the table has a logical break, split it into smaller tables. Tips include keeping tables simple, using a single clear row of header cells, and do not merge or isolate cells.<\/li>\n<\/ul>\n\n\n\n
4. Sheets (Metadata and Structure)<\/h4>\n\n\n\n\n- Descriptive Naming (The Final Check):<\/strong> Manually check that your document has a descriptive title<\/strong> (not just “Copy of Untitled 1”). Change generic sheet names<\/strong> (Sheet 1, Sheet 2) to descriptive names (e.g., “Quarterly Sales,” “Contact Info”). Also, check that sheets are not empty and are not too large.<\/li>\n<\/ul>\n\n\n\n
VI. Compliance Beyond Automated Checkers<\/h3>\n\n\n\n
Accessibility checkers are a good starting point but require human intervention.<\/p>\n\n\n\n
\n- Links:<\/strong> Make links descriptive<\/strong> (e.g., not “click here”).<\/li>\n\n\n\n
- Language:<\/strong> Use clear, simple language<\/strong>. Check for readability.<\/li>\n\n\n\n
- Logical Reading Order:<\/strong> Use the Tab key<\/strong> to navigate the sheet. If you can’t access all information, or if the order is confusing, reorder the content.<\/li>\n\n\n\n
- Cognitive Load:<\/strong> Prioritize clarity and simplicity<\/strong>.<\/li>\n\n\n\n
- User Feedback:<\/strong> Proactively seek feedback<\/strong> from users of assistive technology (the Anticipation Model). Don’t wait for complaints.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nVII. Q&A Summary<\/h3>\n\n\n\n\n- All Content Required to be Accessible?<\/strong> All sheets, including those used only by employees, must be made accessible under the updated guidance. This is to support employees who require accessible content and to build good habits.<\/li>\n\n\n\n
- Boise State Brand Colors Accessible?<\/strong> All brand standard colors have been checked for contrast ratios. The website uses a specific digital orange. Some colors are labeled as print-only<\/strong> because they are not digitally accessible.<\/li>\n\n\n\n
- Chart Legends Location?<\/strong> There is no hard rule on placement, but follow chart conventions for readability (most are on the right-hand side).<\/li>\n\n\n\n
- How Long is Too Long for a Table?<\/strong> There is no hard and fast rule; the warning is a “pass with warning” requiring human review. Use your best judgment. If the table has a logical break, split it into smaller tables.<\/li>\n\n\n\n
- Heading Size on webpages?<\/strong> (Regarding a separate question on WordPress headings) I don’t have a specific answer for that one yet. You’re talking about, like, our heading size. I believe, and I don’t think there has been any discussion on changing that at the moment, but if you wanted to follow up with me separately, we could take a look at your project and see, is there something that we could do to maybe adjust the way it’s presented on the page, or maybe change using one of our different block themes? Or block styling that we have available to meet your needs, because I know we’ve got some constraints in our web designs, but we may be able to adjust it a little bit based on your specific needs.<\/li>\n<\/ul>\n<\/details>\n\n\n\n
\n\n\n\n
Key Remediation Actions<\/h3>\n\n\n\n\n- Structure:<\/strong> Properly format tables with headers, use descriptive sheet names, and give the document a proper title.<\/li>\n\n\n\n
- Visuals:<\/strong> Add alternative text<\/strong> to all charts and images, and use the contrast checker to ensure sufficient color contrast<\/strong>.<\/li>\n\n\n\n
- Content:<\/strong> Fix readability issues like fine print<\/strong> (text below 8-point font) and avoid merged cells<\/strong>.<\/li>\n<\/ul>\n\n\n\n
Final Takeaway<\/h3>\n\n\n\n
While automated tools like Grackle are essential, true accessibility requires human intervention<\/strong> (clear language, descriptive links, logical reading order) and proactively seeking feedback<\/strong> from users of assistive technology.<\/p>\n\n\n\n
\n\n\n\n<\/div>\n\n\n\nSummary and Annotated Outline<\/h2>\n\n\n\n
Carolyn Quintero, Manager of Web Accessibility on the University Web Strategy team, presented a webinar on making Google Sheets accessible using Grackle for Google Sheets. The session focused on ensuring data accessibility for all university community members as part of Boise State’s broader web strategy.<\/p>\n\n\n\n
Carolyn began by explaining the importance of accessibility beyond mere compliance, emphasizing that accessibility should work for both content creators and end users. She introduced additional campus resources including Christine Dobson (Digital Accessibility Compliance Officer) and Jeremy Harper (for faculty support with course materials).<\/p>\n\n\n\n
The presentation covered the legal requirements under Title II of the Americans with Disabilities Act, noting that new digital accessibility guidelines were published on April 24, 2024, with a compliance deadline of April 2027. These guidelines require all digital content to meet WCAG 2.1 Level AA standards, including password-protected content in systems like Google Drive.<\/p>\n\n\n\n
Carolyn outlined a decision framework for reviewing Google Sheets: remove outdated content, replace content with more accessible formats when possible, or remediate sheets that must remain in their current format. She then provided a detailed walkthrough of using Grackle for Google Sheets to identify and fix accessibility issues.<\/p>\n\n\n\n
The demonstration covered several key accessibility areas: fixing fine print (text below 8-point font), ensuring proper color contrast, adding alternative text to charts and images, properly formatting tables with headers, avoiding merged cells, using descriptive sheet names, and giving documents proper titles. Carolyn emphasized that while Grackle is a helpful tool, it requires human intervention to ensure true accessibility.<\/p>\n\n\n\n
The session concluded with additional considerations beyond automated checking, including making links descriptive, using clear language, ensuring logical reading order, and considering cognitive load. Carolyn encouraged proactively seeking feedback from users of assistive technology rather than waiting for complaints.<\/p>\n\n\n\nWant to jump to a specific section of the video? Here’s the Annotated Outline<\/summary>\n\n- Introduction & Housekeeping (0:00-1:30)<\/li>\n\n\n\n
- Speaker Introduction and Campus Resources (1:30-4:27)<\/li>\n\n\n\n
- Legal Requirements and Compliance Deadlines (4:27-7:37)<\/li>\n\n\n\n
- Decision Framework for Google Sheets (7:37-10:00)<\/li>\n\n\n\n
- Introduction to Grackle for Google Sheets (10:00-11:48)<\/li>\n\n\n\n
- Addressing Fine Print Issues (11:48-15:01)<\/li>\n\n\n\n
- Ensuring Color Contrast (15:01-20:38)<\/li>\n\n\n\n
- Adding Alternative Text to Charts and Images (20:38-26:17)<\/li>\n\n\n\n
- Formatting Tables for Accessibility (26:17-37:13)<\/li>\n\n\n\n
- Ensuring Descriptive Names (37:13-42:05)<\/li>\n\n\n\n
- Accessibility Beyond Automated Checking (42:05-45:26)<\/li>\n\n\n\n
- Q & A (45:26-end of webinar)<\/li>\n<\/ol>\n<\/details>\n\n\n\n
\n\n\n\n<\/div>\n\n\n\nFull Text Transcript<\/h2>\n\n\n\nExpand to access the full text transcript<\/summary>\nI. Introduction and Housekeeping<\/h3>\n\n\n\n
Welcome, everybody! Very excited to talk to you today about Grackle for Google Sheets, making your data accessible. So this is a crucial part of our broader university web strategy, and it’s all about ensuring that the data we create and share is usable by every member of our community.<\/p>\n\n\n\n
Housekeeping<\/h4>\n\n\n\n\n- First of all, please, if you haven’t already, mute your microphones. This will help limit background noise as we go through today.<\/li>\n\n\n\n
- We are recording this session. I will make it available on the Boise State Accessibility site on the on-demand webinars<\/a> page.<\/li>\n\n\n\n
- If you do have questions, we will try our best to answer them at the end of the session. I’ve tried to leave some time at the end, but if we run out of time. We will still answer your questions and include them on that page with the webinar recording.<\/li>\n\n\n\n
- So if you have questions, please add them to chat, and my wonderful assistant, Ciera Garechana, will, collect all those, and we will answer those at the end.<\/li>\n\n\n\n
- If you have any questions, or need assistance, you can also directly message her.<\/li>\n\n\n\n
- We also have a resource available on the Boise State Accessibility website specific for Grackle Sheets. So if you go to Boise State Accessibility on the Resources and Tutorials<\/a> page, you will find all of these resources and more. <\/li>\n<\/ul>\n\n\n\n
II. Presenter and Campus Support<\/h3>\n\n\n\n
My name is Carolyn Quintero, and I am the Manager of Web Accessibility on the University Web Strategy team. I’ve helped guide the institution’s digital compliance and inclusion efforts specifically for our public-facing web content since 2017. My educational background includes a Master of Arts in Technical Communication and a Bachelor of Arts in Communications, both earned at Boise State University. My approach to accessibility is not just compliance. I think of accessibility as a critical element, ensuring every step in the content process works for everyone. So it has to work for our content creators as well as our end users.<\/p>\n\n\n\n
Additional Campus Support<\/h4>\n\n\n\n
I’m not the only resource available on campus to help with this huge topic. We do have additional support available for campus in our Office of Compliance and Ethics.<\/p>\n\n\n\n
\n- Christine Dobson (Digital Accessibility Compliance Officer):<\/strong> Contact her at accessibility@boisestate.edu or 208-426-1256. This support is for questions about the new accessibility requirements, scheduling compliance staff to explain regulations and provide basic accessibility training. They can answer compliance questions, do software testing, and answer general accessibility questions.<\/li>\n\n\n\n
- Jeremy Harper (Community Engagement and Belonging):<\/strong> Contact them at belonging@boisestate.edu or 208-426-6156. This support is for faculty support with making course materials accessible, including requesting a course review.<\/li>\n<\/ul>\n\n\n\n
III. Legal Commitment and Compliance<\/h3>\n\n\n\n
Our commitment to accessibility is rooted in legal compliance, specifically Title II of the Americans with Disabilities Act<\/strong>.<\/p>\n\n\n\n\n- New Guidelines & Deadline:<\/strong> The new digital accessibility guidelines were published on April 24th of 2024<\/strong>. The deadline for meeting the WCAG 2.1 level AA standards<\/strong> is April 24th of 2026<\/strong>.<\/li>\n\n\n\n
- Scope:<\/strong> These guidelines require that all of our digital content<\/strong>\u2014including websites, apps, digital documents, presentations, and course materials\u2014must be accessible. This even covers content stored in password-protected systems, like My Boise State, Canvas, or specifically Google Drive.<\/li>\n<\/ul>\n\n\n\n
Shifting to the Anticipating Model<\/h4>\n\n\n\n\n- Current (Accommodating) Model:<\/strong> This model is much more reactive. A user has to report a barrier and request access. That can lead to time delays, frustration, and lost engagement. And in the worst case scenario, the barrier is never fixed.<\/li>\n\n\n\n
- Goal (Anticipating) Model:<\/strong> The anticipating model is proactive<\/strong>, where we empower ourselves to build for accessibility from the start. This leads to fewer delays, less mental effort for the user, and a higher likelihood of engagement. We want to remove those barriers before they ever even become an issue.<\/li>\n<\/ul>\n\n\n\n
IV. The Decision Framework: Remove, Replace, or Remediate<\/h3>\n\n\n\n
Our goal for this month is to review our Google Sheets<\/strong> and make a decision for each one. Think of your files as going into one of these three buckets:<\/p>\n\n\n\n\n- Remove:<\/strong> The question to ask is: Do we still need this sheet? Is the information current? Is the information accurate? The recommended action is to remove the link, unshare the sheet, and then archive as needed for your department.<\/li>\n\n\n\n
- Replace:<\/strong> The question to ask is: Is this the best format for this content? Could you move it to another format, like a web page, or maybe even a web form? The recommended action is to convert that content to the other format, remove that web link and archive as needed.<\/li>\n\n\n\n
- Remediate:<\/strong> The question to ask is: Do your users require the version of this sheet (e.g., a template, or required for their job)? The recommended action is to make a copy<\/strong> of your content, run Grackle Sheets, fix your issues, and then share that accessible version with your audience.<\/li>\n<\/ul>\n\n\n\n
V. Grackle Sheets: Remediation Walkthrough<\/h3>\n\n\n\n
Grackle Sheets is an accessibility checker for Google Sheets. Google Sheets does not have a native accessibility checker, so Grackle Sheets is a third-party add-on that is available within every single Google Sheet.<\/p>\n\n\n\n
\n- To Access:<\/strong> Open your sheet, go to Extensions > Grackle Sheets > Launch<\/strong>.<\/li>\n\n\n\n
- Report Categories:<\/strong> The report is broken into five categories: Sheets, Tables, Images, Charts, and Contents<\/strong>.<\/li>\n\n\n\n
- Recommended Workflow:<\/strong> It’s actually better to work backwards<\/strong> from that more granular view. Fix Contents<\/strong> first, then Charts\/Images<\/strong>, then Tables<\/strong>, and finally Sheets<\/strong>.<\/li>\n<\/ul>\n\n\n\n
1. Contents: Fine Print and Color Contrast<\/h4>\n\n\n\n\n- Fine Print:<\/strong> This is flagged when anything is below 8-point font<\/strong>. The fix is to change font size to 10 or higher<\/strong> (12-point is ideal). Tips to avoid this include simplifying your wording, using bullet points, widening your columns, or using the text wrapping tool. For complex notes, consider moving lengthy notes to their own sheet to allow for more space, or use descriptive cell notes<\/strong> for specific data points.<\/li>\n\n\n\n
- Color Contrast:<\/strong> The report checks for text that is not using a high contrast color. The recommended tool is to manually verify colors using the Color Contrast Checker<\/strong> at colourcontrast.cc<\/a>. Warning:<\/strong> Anytime you have color in your sheet, always do a manual review<\/strong>, because Grackle Sheets may not pull in conditional formatting colors. Tip:<\/strong> Do not use color alone<\/strong> to indicate a value or change. You have to provide something else, like a plus or minus sign, to accompany the color.<\/li>\n<\/ul>\n\n\n\n
2. Images and Charts (Alt Text)<\/h4>\n\n\n\n\n- Charts:<\/strong> Charts require an alternative text description<\/strong>. Alt Text Tips include stating the chart type and purpose, providing a good summary of the key takeaways<\/strong>, and you can also direct the user to the underlying data table. The Chart Editor Tool can be used to add accessibility features like horizontal and vertical axis titles, data labels, and adjusting colors\/patterns.<\/li>\n\n\n\n
- Images:<\/strong> If the image conveys information, be concise but descriptive<\/strong> and convey the context and function. If the image is purely decorative<\/strong> (eye candy) with no information shared, use the Grackle Sheets option to mark as an artifact<\/strong> to tell screen readers to skip this image.<\/li>\n<\/ul>\n\n\n\n
3. Tables<\/h4>\n\n\n\n\n- Headers:<\/strong> Tables must be programmatically tagged with headers. The fix is to convert your content to a Table<\/strong> using Format > Convert to Table<\/strong> (or Ctrl-Alt-T). Then, use Grackle Sheets to mark the table with a header row, header column, or both.<\/li>\n\n\n\n
- Merged\/Isolated Cells:<\/strong> Avoid merged or isolated cells, as they confuse non-visual navigation. The fix is to use the Unmerge tool in Grackle Sheets to quickly unmerge all cells.<\/li>\n\n\n\n
- Table Length:<\/strong> The check for “tables should not be too long” will require human review<\/strong>. If the table has a logical break, split it into smaller tables. Tips include keeping tables simple, using a single clear row of header cells, and do not merge or isolate cells.<\/li>\n<\/ul>\n\n\n\n
4. Sheets (Metadata and Structure)<\/h4>\n\n\n\n\n- Descriptive Naming (The Final Check):<\/strong> Manually check that your document has a descriptive title<\/strong> (not just “Copy of Untitled 1”). Change generic sheet names<\/strong> (Sheet 1, Sheet 2) to descriptive names (e.g., “Quarterly Sales,” “Contact Info”). Also, check that sheets are not empty and are not too large.<\/li>\n<\/ul>\n\n\n\n
VI. Compliance Beyond Automated Checkers<\/h3>\n\n\n\n
Accessibility checkers are a good starting point but require human intervention.<\/p>\n\n\n\n
\n- Links:<\/strong> Make links descriptive<\/strong> (e.g., not “click here”).<\/li>\n\n\n\n
- Language:<\/strong> Use clear, simple language<\/strong>. Check for readability.<\/li>\n\n\n\n
- Logical Reading Order:<\/strong> Use the Tab key<\/strong> to navigate the sheet. If you can’t access all information, or if the order is confusing, reorder the content.<\/li>\n\n\n\n
- Cognitive Load:<\/strong> Prioritize clarity and simplicity<\/strong>.<\/li>\n\n\n\n
- User Feedback:<\/strong> Proactively seek feedback<\/strong> from users of assistive technology (the Anticipation Model). Don’t wait for complaints.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nVII. Q&A Summary<\/h3>\n\n\n\n\n- All Content Required to be Accessible?<\/strong> All sheets, including those used only by employees, must be made accessible under the updated guidance. This is to support employees who require accessible content and to build good habits.<\/li>\n\n\n\n
- Boise State Brand Colors Accessible?<\/strong> All brand standard colors have been checked for contrast ratios. The website uses a specific digital orange. Some colors are labeled as print-only<\/strong> because they are not digitally accessible.<\/li>\n\n\n\n
- Chart Legends Location?<\/strong> There is no hard rule on placement, but follow chart conventions for readability (most are on the right-hand side).<\/li>\n\n\n\n
- How Long is Too Long for a Table?<\/strong> There is no hard and fast rule; the warning is a “pass with warning” requiring human review. Use your best judgment. If the table has a logical break, split it into smaller tables.<\/li>\n\n\n\n
- Heading Size on webpages?<\/strong> (Regarding a separate question on WordPress headings) I don’t have a specific answer for that one yet. You’re talking about, like, our heading size. I believe, and I don’t think there has been any discussion on changing that at the moment, but if you wanted to follow up with me separately, we could take a look at your project and see, is there something that we could do to maybe adjust the way it’s presented on the page, or maybe change using one of our different block themes? Or block styling that we have available to meet your needs, because I know we’ve got some constraints in our web designs, but we may be able to adjust it a little bit based on your specific needs.<\/li>\n<\/ul>\n<\/details>\n\n\n\n
\n\n\n\n
Final Takeaway<\/h3>\n\n\n\n
While automated tools like Grackle are essential, true accessibility requires human intervention<\/strong> (clear language, descriptive links, logical reading order) and proactively seeking feedback<\/strong> from users of assistive technology.<\/p>\n\n\n\n Carolyn Quintero, Manager of Web Accessibility on the University Web Strategy team, presented a webinar on making Google Sheets accessible using Grackle for Google Sheets. The session focused on ensuring data accessibility for all university community members as part of Boise State’s broader web strategy.<\/p>\n\n\n\n Carolyn began by explaining the importance of accessibility beyond mere compliance, emphasizing that accessibility should work for both content creators and end users. She introduced additional campus resources including Christine Dobson (Digital Accessibility Compliance Officer) and Jeremy Harper (for faculty support with course materials).<\/p>\n\n\n\n The presentation covered the legal requirements under Title II of the Americans with Disabilities Act, noting that new digital accessibility guidelines were published on April 24, 2024, with a compliance deadline of April 2027. These guidelines require all digital content to meet WCAG 2.1 Level AA standards, including password-protected content in systems like Google Drive.<\/p>\n\n\n\n Carolyn outlined a decision framework for reviewing Google Sheets: remove outdated content, replace content with more accessible formats when possible, or remediate sheets that must remain in their current format. She then provided a detailed walkthrough of using Grackle for Google Sheets to identify and fix accessibility issues.<\/p>\n\n\n\n The demonstration covered several key accessibility areas: fixing fine print (text below 8-point font), ensuring proper color contrast, adding alternative text to charts and images, properly formatting tables with headers, avoiding merged cells, using descriptive sheet names, and giving documents proper titles. Carolyn emphasized that while Grackle is a helpful tool, it requires human intervention to ensure true accessibility.<\/p>\n\n\n\n The session concluded with additional considerations beyond automated checking, including making links descriptive, using clear language, ensuring logical reading order, and considering cognitive load. Carolyn encouraged proactively seeking feedback from users of assistive technology rather than waiting for complaints.<\/p>\n\n\n\n Welcome, everybody! Very excited to talk to you today about Grackle for Google Sheets, making your data accessible. So this is a crucial part of our broader university web strategy, and it’s all about ensuring that the data we create and share is usable by every member of our community.<\/p>\n\n\n\n My name is Carolyn Quintero, and I am the Manager of Web Accessibility on the University Web Strategy team. I’ve helped guide the institution’s digital compliance and inclusion efforts specifically for our public-facing web content since 2017. My educational background includes a Master of Arts in Technical Communication and a Bachelor of Arts in Communications, both earned at Boise State University. My approach to accessibility is not just compliance. I think of accessibility as a critical element, ensuring every step in the content process works for everyone. So it has to work for our content creators as well as our end users.<\/p>\n\n\n\n I’m not the only resource available on campus to help with this huge topic. We do have additional support available for campus in our Office of Compliance and Ethics.<\/p>\n\n\n\n Our commitment to accessibility is rooted in legal compliance, specifically Title II of the Americans with Disabilities Act<\/strong>.<\/p>\n\n\n\n Our goal for this month is to review our Google Sheets<\/strong> and make a decision for each one. Think of your files as going into one of these three buckets:<\/p>\n\n\n\n Grackle Sheets is an accessibility checker for Google Sheets. Google Sheets does not have a native accessibility checker, so Grackle Sheets is a third-party add-on that is available within every single Google Sheet.<\/p>\n\n\n\n Accessibility checkers are a good starting point but require human intervention.<\/p>\n\n\n\n
\n\n\n\nSummary and Annotated Outline<\/h2>\n\n\n\n
Want to jump to a specific section of the video? Here’s the Annotated Outline<\/summary>\n
\n
\n\n\n\nFull Text Transcript<\/h2>\n\n\n\n
Expand to access the full text transcript<\/summary>\n
I. Introduction and Housekeeping<\/h3>\n\n\n\n
Housekeeping<\/h4>\n\n\n\n
\n
II. Presenter and Campus Support<\/h3>\n\n\n\n
Additional Campus Support<\/h4>\n\n\n\n
\n
III. Legal Commitment and Compliance<\/h3>\n\n\n\n
\n
Shifting to the Anticipating Model<\/h4>\n\n\n\n
\n
IV. The Decision Framework: Remove, Replace, or Remediate<\/h3>\n\n\n\n
\n
V. Grackle Sheets: Remediation Walkthrough<\/h3>\n\n\n\n
\n
1. Contents: Fine Print and Color Contrast<\/h4>\n\n\n\n
\n
2. Images and Charts (Alt Text)<\/h4>\n\n\n\n
\n
3. Tables<\/h4>\n\n\n\n
\n
4. Sheets (Metadata and Structure)<\/h4>\n\n\n\n
\n
VI. Compliance Beyond Automated Checkers<\/h3>\n\n\n\n
\n
\n\n\n\nVII. Q&A Summary<\/h3>\n\n\n\n
\n
\n\n\n\n
![](\"https:\/\/i.ytimg.com\/vi\/PSsDw9Pm_GI\/0.jpg\"\n\t\t\t\t\talt=\"\"\n)
\n