More Control, Less Friction - CourtneyR.dev's 2nd Brain

More Control, Less Friction ![rw-book-cover](https://img.youtube.com/vi/LTtkq_SH2eA/maxresdefault.jpg) 🔗 **Source:** [More Control, Less Friction](https://www.youtube.com/watch?v=LTtkq_SH2eA) > [!note]+ Document Notes > tags: #accessibility-checker #wordpress-plugin #accessibility #ui-improvements > author: Equalize Digital > source: YouTube > reference: https://www.youtube.com/watch?v=LTtkq_SH2eA > date created: 2024-12-19 10:30 > > # 🏷️ Title: More Control, Less Friction - Accessibility Checker Plugin Changelog #12 >  ## 🧰 Action Inbox - [H1] Implement CSS modifier classes for new window warnings — reduce layout conflicts #accessibility - [H2] Configure block editor metabox visibility settings — improve UX workflow #wordpress - [H3] Set up post ID exclusion filters for full site scans — handle problematic pages #scanning ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Accessibility Checker Plugin](https://equalizedigital.com) - [WordPress.org Plugin Directory](https://wordpress.org) ## 📝 Summary - Accessibility Checker plugin releases version 1.39.0 (free) and 1.21.0 (pro) focused on removing friction from accessibility auditing - New CSS modifier classes allow better control over new window warning display to prevent layout issues - Block editor metabox can now be hidden when using the sidebar interface - Full site scanner improvements include post ID exclusion filters and performance optimizations - UI refresh brings modern design aligned with WordPress core styling across all interfaces - New empty search handling fix prevents confusing results for users with cognitive disabilities ## 📖 Main Content Equalize Digital's Accessibility Checker plugin has released significant updates focused on giving users more control while reducing friction in accessibility workflows. The plugin provides automated accessibility scanning for WordPress websites, with both free and premium versions available. The release introduces CSS modifier classes for new window warnings that allow developers to hide icons or tooltips when they interfere with navigation menus or break layouts. Performance improvements to the full site scanner reduce database queries from four to one during scan initialization, providing up to 3x speed improvements on large sites. A major UI refresh modernizes the plugin's appearance to better integrate with WordPress core styling, adopting user color scheme preferences and updating terminology from "errors/warnings" to "problems/needs review." The interface now supports both the new block editor sidebar and traditional metabox views based on user preference. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/LTtkq_SH2eA?t=0) — [H1] Changelog 12 Introduction - Key idea: Episode 12 focuses on "more control, less friction" theme for accessibility auditing - Evidence: "This release is really about removing the little points of friction that slow people down when they're doing accessibility auditing and remediation" #### ⏱️ [02:30](https://youtu.be/LTtkq_SH2eA?t=150) — [H2] CSS Modifier Classes for New Window Warnings - Key idea: New classes allow hiding icons or tooltips that break layouts or navigation - Evidence: "The modifier classes do two specific things. The first one is it hides the visible label and it prevents the tool tip from being displayed" #### ⏱️ [06:45](https://youtu.be/LTtkq_SH2eA?t=405) — [H3] Navigation Menu Tooltip Issues - Key idea: Tooltips can interfere with hover-based navigation menus by triggering close events - Evidence: "When you hover over the tool tip, you're no longer within the navigation and some navigations act on that when you leave the navigation" #### ⏱️ [12:20](https://youtu.be/LTtkq_SH2eA?t=740) — [H2] Block Editor Metabox Control Setting - Key idea: Users can now choose whether to show the metabox alongside the new sidebar - Evidence: "Show accessibility checker metab box in the block editor... existing users will retain the metbox... new users will have this enabled by default" #### ⏱️ [18:15](https://youtu.be/LTtkq_SH2eA?t=1095) — [H1] Post ID Exclusion for Full Site Scans - Key idea: Problematic pages like logout URLs can be excluded from full site scanning - Evidence: "Some sites have log URLs and they are technically pages but if you visit those pages it logs you out" #### ⏱️ [25:30](https://youtu.be/LTtkq_SH2eA?t=1530) — [H2] Performance Improvements for Large Sites - Key idea: Database query optimization reduces scan initialization time by up to 3x - Evidence: "We were gathering that information with potentially three or four... queries... So what I did was I made one of the queries slightly more intensive" #### ⏱️ [28:45](https://youtu.be/LTtkq_SH2eA?t=1725) — [H3] Failed Scan Management - Key idea: New interface allows clearing failed page scans individually or in bulk - Evidence: "There is three things new here... you can see there's an action button. Clear on the individual item. There's also a clear all button" #### ⏱️ [35:20](https://youtu.be/LTtkq_SH2eA?t=2120) — [H2] Empty Search Handling Fix - Key idea: Prevents confusing search results when users submit empty search queries - Evidence: "For someone who might not fully get what's going on here, this could be incredibly confusing" #### ⏱️ [40:15](https://youtu.be/LTtkq_SH2eA?t=2415) — [H1] UI Refresh and WordPress Integration - Key idea: Complete visual overhaul adopts WordPress core styling and user color preferences - Evidence: "I actually like my plugins to look like WordPress... Everything in our plug-in should look like WordPress because it is inside WordPress" #### ⏱️ [47:30](https://youtu.be/LTtkq_SH2eA?t=2850) — [H3] Terminology Updates - Key idea: Changed from "errors/warnings/ignore" to "problems/needs review/dismiss" for better UX - Evidence: "We don't call things errors anymore. We call them problems... We have gone away from using the word ignore in favor of dismiss" #### ⏱️ [52:40](https://youtu.be/LTtkq_SH2eA?t=3160) — [H3] Progress Bar Visual Enhancements - Key idea: Added animated candy stripes to show scanning activity between page completions - Evidence: "I wanted to add these stripes... to give a little bit of movement to show... hey it's doing something" #### ⏱️ [56:10](https://youtu.be/LTtkq_SH2eA?t=3370) — [H2] Smarter Transcript Detection - Key idea: Improved video transcript detection searches deeper in DOM structure for page builders - Evidence: "We actually increased the limit. So it will now look five levels of DOM depth away to try and find the transcript" #### ⏱️ [58:45](https://youtu.be/LTtkq_SH2eA?t=3525) — [H1] Email Reports Preview - Key idea: Upcoming feature will connect free users to dashboard for weekly accessibility reports - Evidence: "Our email reports were are going to let you... attach your free or your paid plugin... and then it will get audit summaries" ## 📚 References - [Accessibility Checker Plugin Documentation](https://equalizedigital.com) - [WordPress Plugin Repository](https://wordpress.org) - [WP Accessibility Plugin by Joe Dolson](https://wordpress.org/plugins/wp-accessibility/) ## 🗣️ Paraphrase - The plugin now offers CSS modifier classes to hide new window warning icons or tooltips when they interfere with site layouts or navigation functionality - A new setting allows users to hide the traditional metabox in the block editor while keeping the modern sidebar interface - Full site scanning has been optimized with database query improvements and the ability to exclude problematic pages that cause scan failures ## 📰 Newsletter 🚀 **Accessibility Checker Gets Smarter and Smoother** The latest Accessibility Checker update is all about removing friction from your accessibility workflow. New CSS modifier classes let you fine-tune new window warnings to work perfectly with your theme's navigation, while performance improvements make full site scans up to 3x faster on large sites. The refreshed UI now matches WordPress core styling and adopts your chosen color scheme, making the plugin feel like a native part of your dashboard. Plus, you can now exclude problematic pages from full site scans and clear failed scans with one click. Most exciting: upcoming email reports will connect even free users to automated weekly accessibility summaries delivered to your inbox! Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Evaluate empty search handling as potential core enhancement - Design: Review plugin UI integration patterns with core styling - Accessibility: Document best practices for tooltip implementation in navigation #### Community - Maintainers: Share performance optimization techniques for large-scale scanning - Contributors: Provide feedback on accessibility terminology standardization - Sponsors: Support accessibility tooling development for page builders ## 🧪 Hypotheses - CSS modifier classes will reduce support requests related to layout conflicts with new window warnings - Unified UI styling will improve user experience and reduce cognitive load when switching between WordPress admin areas - Performance optimizations will increase completion rates for full site scans on large websites - Terminology changes from "errors" to "problems" will reduce user anxiety and encourage remediation ### 📊 Methodology - Track support ticket volume related to new window warning layout issues before and after modifier class implementation - Monitor full site scan completion rates and performance metrics across different site sizes - Survey user satisfaction with terminology changes and UI refresh - Analyze usage patterns between sidebar and metabox interfaces ### ❓ Questions - How can accessibility plugins better integrate with page builder workflows without requiring constant updates? - What impact does UI styling consistency have on accessibility tool adoption rates? - How do terminology choices affect user perception of accessibility issues and remediation urgency? ### 🔮 Future Research - Investigate automated detection of layout conflicts in accessibility fix implementations - Explore standardization of accessibility terminology across WordPress ecosystem - Study performance patterns in accessibility scanning across different hosting environments ### 💡 Implications - Practice: Demonstrates importance of user feedback in accessibility tool development - Policy: Shows value of progressive enhancement in accessibility feature rollout - Education: Highlights need for accessibility tool documentation that addresses real-world implementation challenges - Funding: Indicates sustainable model of freemium accessibility tooling with advanced features for paid users ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Live screen sharing demonstrations of plugin features and UI changes - Improve: Static screenshots in documentation, visual workflow diagrams #### 🔊 Aural learners - Present: Complete audio walkthrough with verbal explanations - Improve: Separate audio tracks for key feature explanations #### 🗣️ Verbal learners - Present: Clear definitions of technical terms, real-world analogies - Improve: Glossary of accessibility terminology, comparative explanations #### 🧩 Kinesthetic learners - Present: Live demonstrations with step-by-step interactions - Improve: Hands-on sandbox environment for testing features #### 🧠 Logical learners - Present: Performance metrics, systematic feature categorization - Improve: Decision flowcharts for feature adoption, comparative tables #### 🧑‍🤝‍🧑 Social learners - Present: Live Q&A format, community feedback integration - Improve: User testimonials, collaborative testing opportunities #### 🧘‍♀️ Solitary learners - Present: Detailed technical documentation, independent exploration - Improve: Self-assessment checklists, private testing environments ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Good heading structure and landmark usage in interface - Improve: Ensure all dynamic content changes are announced #### Keyboard navigation - Present: Focus management in scanning interfaces - Improve: Verify tab order in refreshed UI components #### Contrast and readability - Present: Adopts user's chosen WordPress color scheme - Improve: Validate contrast ratios across all theme options #### Media and captions - Present: Complete video transcript in source material - Improve: Time-coded captions for key demonstrations ### 🌍 DEIB Assessment #### Cultural breadth - Present: Plugin translated into 35 languages - Improve: Include examples from different regional accessibility standards #### Inclusive language - Present: Updated terminology from "errors" to "problems" reduces stigma - Improve: Continue reviewing language for cognitive accessibility #### Neurodiversity support - Present: Clear progress indicators and status feedback - Improve: Reduce cognitive load in complex scanning workflows #### Representation - Present: Focus on real user needs and feedback integration - Improve: Highlight diverse use cases and user stories ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear connection between user friction points and implemented solutions - Inductive strength: Pattern recognition from support requests leading to feature development - Causal reasoning: Performance improvements directly address scan timeout issues - Analogical strength: UI consistency patterns from WordPress core applied successfully #### Fallacies - None identified - reasoning appears sound throughout #### Tone of voice - Overall tone: Professional and collaborative, focused on user value and practical improvements ### 🛡️ DARVO Analysis - Deny: No instances of denial or minimization - Attack: No attacks on users or competing solutions - Reverse victim/offender: No victim/offender reversals identified - Emotional cues and rhetoric: Positive, solution-focused language throughout ## 🎯 Conclusion This Accessibility Checker release successfully addresses user friction points through thoughtful feature development driven by real user feedback. The combination of technical improvements (performance optimization, flexible configuration) and user experience enhancements (UI refresh, terminology updates) demonstrates a mature approach to accessibility tooling that balances functionality with usability. The upcoming email reports feature represents a significant expansion of value for free users while maintaining sustainable business model differentiation. The development process showcased here - from user feedback to implementation to testing - provides a strong model for accessibility-focused plugin development in the WordPress ecosystem. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] CSS modifier classes improve layout compatibility > [!quote] [More Control, Less Friction](https://www.youtube.com/watch?v=LTtkq_SH2eA) by [[Equalize Digital]] via [[YouTube]]. Published 2024. Accessed 2024-12-19. > "The modifier classes do two specific things. The first one is it hides the visible label and it prevents the tool tip from being displayed." Enables developers to prevent new window warning tooltips from interfering with hover navigation menus by providing granular control over icon and tooltip display. [view highlight](https://www.youtube.com/watch?v=LTtkq_SH2eA#H1) #xref #articleseed ID:rw_changelog12_01 ### [H2] Database query optimization reduces scan initialization time > [!quote] [More Control, Less Friction](https://www.youtube.com/watch?v=LTtkq_SH2eA) > "We were gathering that information with potentially three or four individual separate queries each that were resulting in very similar post ID lists." Performance improvement consolidates multiple database queries into single query for full site scan initialization, providing up to 3x speed improvement on large sites. [view highlight](https://www.youtube.com/watch?v=LTtkq_SH2eA#H2) #xref ID:rw_changelog12_02 --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Accessibility tooling requires layout conflict prevention - Scope: When accessibility fixes interact with existing theme functionality - Pointer: 02:30-06:45 discussion of navigation menu issues - Links: [[Accessibility-UX-Balance]] [[Theme- --- ## Full Transcript [00:00] All right, [00:03] we are live. [00:06] William, how's it going? Uh, [00:08] >> it's going okay. Very itchy today. [00:10] Springtime has sprung. [00:12] >> Springtime has sprung. Yeah. So, [00:16] springtime in Scotland. Um, not doesn't [00:21] really feel like springtime over here in [00:23] the Midwest of the United States so [00:26] much. got kind of cold again. But [00:30] >> I mean for me it just means that [00:32] daffodil have started to bloom. Makes me [00:35] itchy. Sneeze. [00:37] >> Yeah, [00:39] it hits me hard too. Those allergies [00:41] will hit very hard very soon. [00:45] Well, [00:47] um we are just getting set up, making [00:50] sure everything's going out live [00:53] to everybody. [00:56] And it looks like we have a [00:58] >> live on YouTube. [00:59] >> We are live on YouTube. We got a [01:01] confirmation from our very own Equaliz [01:05] Digital [01:07] and our very own Amber who probably just [01:10] switched her YouTube account from [01:12] Equaliz back to Amber, [01:16] which I do all the time, too. [01:19] Uh, [01:20] very cool. [01:23] So, uh, this is episode number 12. [01:27] William, we've made it 12 episodes. [01:29] >> Can't believe it. [01:31] >> So, change log 12. Uh, this is a live [01:35] stream where we go through and we talk [01:38] about uh changes in the accessibility [01:41] checker plug-in. [01:43] For anybody that is not aware, the [01:45] accessibility checker plugin is an [01:47] automated accessibility scanning plugin [01:50] to help your WordPress website become [01:53] and stay accessible. [01:57] So, uh we have a free plugin on uh you [02:03] can get at our website or at [02:05] wordpress.org. [02:07] It's a very fullfeatured scanning plugin [02:09] where you could scan individual pages [02:11] and posts, but we also provide a pro [02:14] plugin as well where will allow you to [02:17] extend out and uh scan custom post [02:20] types, run a full site scanned, and a [02:23] handful of lovely add-ons. We have an [02:26] audit history add-on to track your [02:28] accessibility over time, a multi-sight [02:30] add-on to manage your accessibility [02:33] checker license and stats at the [02:36] multi-sight network level, and an export [02:39] add-on that allows you to export your uh [02:42] accessibility issues to a CSV file. [02:47] So, today's theme [02:49] is more control, less friction. This [02:53] release is really about removing the [02:56] little points of friction that slow [02:58] people down uh when they're doing [03:01] accessibility auditing and remediation. [03:04] So [03:06] excited about this one. Uh these [03:08] releases went out [03:10] uh last week and if I'm right, the [03:15] version numbers it's accessibility [03:17] checker version 1.39.0. [03:22] Correct. [03:23] >> And in Pro, it's version 1.21.0. [03:28] >> Yep. [03:28] >> Oh, I got it. [03:29] >> Right. [03:30] >> All right. Very good. I didn't have that [03:32] written down in my notes off the top of [03:34] my head. Living accessibility checker [03:37] daily. Got those releases stuck in my [03:41] brain. [03:43] Uh, cool. [03:45] So, [03:46] more control where it matters. Let's [03:48] start with the first one here, William. [03:51] Yeah. So, we have added some CSS [03:55] modifier classes to our plug-in for the [03:57] new window warning row. This has been [04:01] I think it was requested more than once. [04:04] Um, however, we [04:07] yeah, we didn't action on this until [04:09] just recently. Um, the the modifier [04:12] classes do two specific things. The [04:14] first one is it hides the visible label [04:16] and it prevents the tool tip from being [04:19] displayed. Those are now options that [04:21] you can apply to your your window [04:24] warning classes. Um, the reason this was [04:27] important, it hiding either of them was [04:30] important for two different reasons. The [04:32] icon first off, sometimes people just [04:35] don't like it. That's one of the [04:37] reasons. Um, but the other main reason [04:39] is that sometimes it does break layouts [04:41] in certain certain situations. An icon [04:44] in a pun might break a line or something [04:47] like that. So that can be quite [04:48] complicated for people to just bulk [04:50] apply the fix to their website and make [04:53] sure everything looks just fine. So now [04:55] there is modifier class to not output [04:57] the the icon. Um the tool tip was a bit [05:02] different. Um the main issue with the [05:04] tool tip was in hover navigations. [05:07] um when you hover over the tool tip, [05:09] you're no longer within the navigation [05:11] and some navigations [05:13] act on [05:15] that when when you leave the navigation. [05:17] Sometimes they close and it's a bit of a [05:20] pain. Um ideally they should handle the [05:24] tool tip, but many of the navigations do [05:26] not. Um I actually I do have I haven't [05:29] shared my screen yet. I can share this [05:31] screen. I have [05:32] >> Oh, I have this. [05:33] >> Do you have up? [05:34] >> Is this helpful? Yeah, this is the same [05:36] markup I was going to test. So if you [05:38] preview this on the front site, you can [05:39] actually show. [05:41] >> So should we show the the classes first? [05:44] So [05:45] >> sure, just just a little caveat here. I [05:47] am running WordPress uh 70.0 beta [05:52] something. Um so I'm I'm on a unreleased [05:56] version. That's why this code box looks [05:59] a little different. In 7.0 [06:01] you you actually can, you know, uh have [06:04] a preview and you can add CSS and [06:07] JavaScript. So, this looks a little [06:08] different than what you may be seeing on [06:10] your site, but you want to walk through [06:12] this, William? [06:13] >> Yeah. So, in this um code section, we [06:17] have a bunch of divs that contain links [06:20] essentially. Um each link either has one [06:23] of the modifier classes applied or does [06:26] not. Um, the purpose of the wrapper div [06:30] is to show that you can actually apply [06:31] those modifiers to a wrapper and then it [06:33] would target all of the links inside of [06:37] that wrapper. Um, so we have two [06:39] modifier classes. We have edac-Nw [06:46] icon. Um, and the yeah this is a pattern [06:51] we follow. So eac at the beginning is [06:53] equalized digital accessibility checker. [06:56] This is for new window warning. And then [06:58] there's the modifier at the end which is [07:00] no dash icon. That there is another [07:02] modifier class which is no-ash tool tip. [07:06] EDAC- NWW-n [07:10] tool tip. And these, you know, these [07:13] handle both the two new behaviors that [07:15] we talked about. Um, and as I said, you [07:18] can apply this to the wrapper class or [07:20] you can apply it directly to the link. [07:22] It functions in both cases. [07:26] So if we have a look at the the front [07:28] end, we have the new window warning [07:29] link. This is the default behavior at [07:31] the top. So it has an icon and has a [07:34] tool tip when you hover over it. Um the [07:37] next link down has no icon but still has [07:40] the tool tip. Um the one after that, no [07:43] tool tip but has the icon. [07:46] And then these last two links both have [07:48] no icon and no tool tip. One of these [07:50] has the classes directly applied to the [07:52] link and one has it applied to the [07:54] wrapper class. And the reason it was [07:57] important to target the wrapper class as [07:59] well is you might want to put one of [08:01] these modifier classes on an entire [08:02] section on your website such as your [08:05] navigation or a hero block, a specific [08:09] piece of content. You might want to have [08:11] this applied [08:13] everywhere inside that block. So you can [08:16] do that. It's either on the link [08:18] directly or on any of the pendant [08:21] wrappers. [08:23] >> Yeah. And I I'll note too that we did [08:25] update the documentation for our opens [08:28] in a new window uh fix. [08:30] >> Correct. [08:31] >> To include these modifier classes. If [08:33] you're a current user, you can uh [08:36] reference that documentation for those [08:37] classes. And we're also reference those [08:40] in the in the in the post that goes out [08:43] in regards to this change log. But to [08:45] speak a little bit about like what [08:46] William was talking about in navigation [08:48] menus. So like in navigation menus you [08:51] can kind of with the JavaScript that's [08:53] used to handle them you can have that [08:55] bubble up effect of events event [08:58] handling. And I'm going to preview this [09:01] on our equalized digital website because [09:03] this is actually something we ran into. [09:06] um when when it uh [09:11] when when you have the new window [09:13] warning in a navigation menu, there can [09:16] be a bubble of effect of those uh [09:18] JavaScript events to where when the tool [09:20] tip is initiated, [09:23] we're doing the accessible thing and [09:25] kind of trying to move focus to it. Um, [09:28] and what that does, it actually triggers [09:30] those other [09:32] uh JavaScript uh handlers that will [09:35] actually they actually think you've gone [09:37] off of the menu and then the menu just [09:39] closes. [09:41] So if I add that um util the utility [09:44] class not to show the tool tip here now [09:48] I can hover over this without the tool [09:51] tip getting focus or out without the [09:55] navigation menu thinking that I've [09:57] actually hovered off of it because [09:59] essentially I have um because that tool [10:02] tip actually doesn't exist [10:04] uh exactly in the same markup. it, you [10:07] know, it's a right [10:09] >> that is correct. It is a globalized [10:11] element. It is one tool tip that appears [10:14] regardless of which link you hover and [10:16] as such is external to all of the markup [10:20] that lives here. [10:21] >> Yeah. So, it is not technically part of [10:24] the navigation menu as far as the [10:26] accessibility tree goes. And it does [10:28] cause issues with [10:31] mobile navs and probably other hover [10:35] effect elements like maybe some sliders [10:39] or anything else that requires your [10:41] mouse to remain on the element might get [10:44] thrown off by moving into a tool tip. [10:46] And this isn't just a problem with our [10:48] tool tip. This is just a custom tool pip [10:52] implementation almost always has this [10:54] issue. [10:55] >> Yep. And you know we can't account for [10:58] how every navigation menu is coded. So [11:01] this is a way to kind of circumvent [11:03] those issues [11:05] and uh and it just puts more control [11:09] where it matters back in your hands to [11:11] help you control uh the output on the [11:15] front end. Um [11:17] cool. [11:18] >> Yeah. And if anyone is listening and [11:19] would like userfacing options to enable [11:22] these globally, let us know. And that's [11:25] something we're considering but have not [11:27] yet implemented. [11:29] >> Yeah. Yeah. We're also Yeah. So we're [11:31] also looking at too with all of our [11:34] fixes um where you can have a you can [11:38] have an active state of a fix but it's [11:40] not actively applied globally. Is that [11:44] what you were referencing, William? [11:46] Correct. [11:47] >> But I was thinking that we would expose [11:49] options where they could disable the [11:51] icon globally as opposed to having to [11:54] use the modifier classes everywhere. [11:56] >> Sure. [11:57] >> True. [11:57] >> However, what you're talking about is [11:58] maybe a secret feature. [12:00] >> Yeah. Secret. So like you can enable a [12:03] fix but but the fix doesn't get applied [12:05] globally to where you could actually use [12:07] these utility classes to apply the fixes [12:10] on an individual basis. [12:13] So just that puts that takes kind of the [12:16] control piece and you know ramps it up [12:19] to 11 and gives you full control on how [12:23] a fix is applied. [12:24] >> Yeah. But by default what we will almost [12:26] always do is we will have a link with an [12:29] icon and a tool tip when the fix is [12:31] enabled. But we will put control of [12:34] those options in users hands. [12:37] >> Yep. in the not too distant future both [12:39] in the the additive method and the [12:43] subtractive. [12:45] >> Perfect. [12:47] So, moving on um putting more control [12:51] back in your hands. So, in our last live [12:54] stream, we went through and we previewed [12:56] our new uh block editor sidebar and that [13:00] kind of brought to rise a few questions [13:04] about what should a user be using? [13:06] Should they be using that new sidebar? [13:08] Should they be using the legacy metab [13:10] box? Um, in some cases they have to use [13:12] the metab box because they're not on a [13:14] block enabled uh post type or post. Um, [13:19] so we we wanted to and if we wanted [13:24] ourselves to be able to not see the [13:27] metab box if we don't have to see the [13:29] metab box. And so what we've done is [13:32] we've added a new setting. And this was [13:34] prompted by one of our uh members of our [13:37] Facebook group. So if you uh are not a [13:40] member of our Facebook group, we will [13:42] put a link in the show notes for this [13:45] and u jump over to our Facebook group [13:47] and join and you can ask us questions [13:50] about the plugin and accessibility and [13:52] anything in between. Um [13:56] so uh we added a setting. Uh I'll pull [14:00] up my screen again. [14:04] And let me go to accessibility checker [14:06] settings [14:09] um [14:11] >> accessible not locator. [14:13] >> Yes. So, if you go to accessibility [14:16] checker settings and you go to system [14:18] settings at the very end, we've added a [14:20] new setting called block editor or block [14:24] editor metab box and with a checkbox [14:28] that says show accessibility checker [14:30] metab box in the block editor. So, you [14:33] can enable that or disable that and and [14:37] your metab box will show or hide based [14:40] on that. But we went a little further, [14:43] right, William? [14:44] >> Yes. So, there is some default behavior [14:46] here. Um, if you already see the metab [14:48] box, you have this plug-in installed, we [14:50] are not going to just immediately head [14:52] it. Um, you are going to still see the [14:55] metab box and you will be able to come [14:57] to the settings page, toggle this in, [15:00] change that so that you don't have to [15:01] see the metab box in the block header if [15:04] you don't want to. If you like the [15:06] metbox, keep it. It's not going away. [15:09] But I think most people will probably [15:11] prefer the sidebar when they have the [15:13] option. Um, so existing users will [15:17] retain the metbox. They have to come [15:18] here, toggle this in. Um, new users will [15:22] have this enabled by default. So they [15:25] will only see the sidebar in the block [15:26] header. They will continue to see the [15:28] classic metbox in classic header. Um, [15:31] and if they want to restore it, they [15:32] have to come to the sense and [15:34] >> yeah, this will actually be disabled. [15:36] Like so if you're a new user, this will [15:38] actually be disabled by default. [15:40] >> Correct. [15:41] >> Yeah. So if you're if you download the [15:44] plugin and put it on a new website, the [15:47] metab box on block enabled pages will be [15:51] disabled by default. But you can come [15:53] here and turn it back on if that's your [15:55] preference. Um if it's a classic editor [15:59] page, um then then we will show you the [16:02] metab box regardless of this setting. [16:05] So, let's show it in action. So, I'm [16:08] going to leave it toggled on and I'll go [16:10] to a post. I'm zoomed in. Let me zoom [16:13] out so it doesn't look weird. Um, [16:17] I'll just edit the same post. [16:21] So, in recent versions, you know, we [16:23] have this separation now with the uh [16:26] where the metab boxes live. [16:28] Um, and a neat little trick that William [16:31] taught me that I didn't know was if you [16:33] actually click on this bar with one [16:34] click, it collapses. [16:36] >> I found it by accident. [16:38] >> And if you click it again, it opens. I [16:40] was I was always clicking this and [16:42] dragging it back and forth. [16:44] >> I I was trying to [16:46] >> Yeah, [16:46] >> that's how I discovered this feature. [16:49] >> So, this is a block enabled theme. Um, [16:52] you have our metab box and you have our [16:56] sidebar. But if I go and deselect the [17:02] uh block editor metabox setting and then [17:06] refresh the page, [17:08] our metab box is gone. Of course, [17:10] there's still, you know, Yost SEO still [17:13] has theirs here, but now it now ours is [17:17] gone. And you can close that and you can [17:19] just uh do your auditing and your [17:22] remediating straight here from the [17:24] sidebar with your content right next to [17:26] it. Um [17:30] and if if you know the sidebar icon is [17:35] how you initiate these and sometimes [17:36] it's hard to find if you're just on a [17:39] regular post. We've actually added a [17:41] little kind of helper [17:43] um panel. Is this a is it? It's a panel. [17:46] It's a panel. [17:47] >> Um, to open our panel up if you're just [17:51] on the regular post edit edit panel. [17:54] >> So, let me test you a bit here. What if [17:56] you unpin this sidebar? How do you get [17:58] it back? [18:00] >> Uh, uh, you want to test me? So, the [18:03] ellipses. So, if I go to the ellipses in [18:06] the top toolbar and then I go to [18:08] accessibility checker and I I turn Wait, [18:12] hold on. How do you unpin it? Up here. [18:13] Right here. There. So, I unpin it. So, I [18:16] had to go to the sidebar. There's a [18:18] little star to unpin it. So, you're [18:20] asking, "How do I get to it?" Well, I [18:22] can I can just do this. [18:25] >> You can do that. [18:26] >> Yeah. [18:27] >> How do you get it back in the toolbar? [18:30] >> Uh, you pin it. [18:32] >> You can You can also go through the menu [18:34] and do this as well. Just for those that [18:35] don't know, [18:36] >> you click the little star. Uh, so this [18:38] is just a little sidebar that, you know, [18:42] if you don't know about sidebars in the [18:44] block editor, you can actually, you [18:46] know, choose which ones you want to see. [18:47] Like I can get rid of Yost SEO from [18:50] here. I thought I could. Hold on. [18:52] >> You have to go through the settings to [18:54] turn it off. The quickest way is to [18:55] click the star icon. [18:57] >> Oh yeah, that's right. See, this is a UX [19:00] problem. [19:01] >> It is. [19:02] >> So I can, you know, I can get rid of [19:04] Yos. I can get rid of our accessibility [19:08] checker, but we, you know, we've kind of [19:11] gone that extra mile to make sure it's [19:13] always here for you in case you forget [19:15] or, you know, you don't know to go to [19:18] the ellipsies menu. [19:20] So [19:22] cool. Um, [19:25] so that's kind of a simple feature that [19:27] had a little bit of thought to it and, [19:30] um, we're glad to get that out in the [19:34] release. and one release from the from [19:37] when we released the sidebar, the very [19:38] next release had that setting. That was [19:40] a request from a a customer. [19:45] All right. So, [19:47] continuing on with our theme of giving [19:50] more control to the user, we have [19:52] another issue that kind of came up [19:53] through our support channels that um [19:56] that William worked on. You want to [19:58] explain this? [19:59] >> This was an issue that came up many [20:01] times actually. So a lot of websites [20:04] have specific pages. So the first and [20:09] the problem at the forefront here was [20:11] some sites have log URLs and they are [20:14] technically pages but if you visit those [20:16] pages it logs you out and due to the [20:18] nature of the way we do our scan. we [20:21] browse the website as a user would see [20:23] it and if you h happen to hit that page [20:26] in the full site scanner it logs you out [20:29] and then you can't continue subsequent [20:31] scan pages. So we needed a way to [20:33] exclude specific pages for that reason. [20:36] Some users have other problem pages that [20:39] don't scan because they're filled with [20:41] JavaScript issues or slow pages or any [20:45] number of other reasons why a page might [20:47] not want to be scanned. There was no [20:49] previous way to exclude them. Now there [20:52] is there's no user exposed feature for [20:54] this yet. This is only done via um a [20:58] filter. You pass any post ID you want to [21:01] skip in the full set scanner, restart [21:03] the scan, that post will get skipped. Um [21:06] and when I say skipped, I mean it will [21:08] not be scanned at all in the full set [21:10] scanner. However, if you visit that page [21:14] individually in the editor, you can [21:16] still scan it. You can also scan it from [21:18] the front end high layer. So this does [21:20] not mean you won't get results for the [21:22] page. It just means it won't be scanned [21:24] in the full site scanner. [21:29] Yeah. So let's let's do a little show [21:31] and tell. Well, you did the tell. Let's [21:33] do the show. [21:35] So [21:37] um like William said, this is not [21:40] currently an exposed setting, but we are [21:43] planning to create a setting for this [21:45] because we are finding it quite valuable [21:47] for our own testing and for clients uh [21:50] troubleshooting uh when there are uh [21:54] scan uh issues with scanning certain [21:56] pages. [21:58] So right now it's a filter. Um we have [22:01] doc we've documented this in our [22:04] documentation correctly. [22:06] >> The documentation article for this one [22:08] is yet to be published but [22:11] >> okay so we will be updating our [22:13] documentation. [22:14] >> Oh no as Dan corrected it is published. [22:17] So [22:18] >> perfect. [22:18] >> You can find this in our docs. [22:20] >> Yeah [22:21] >> with basically this exact example. [22:23] >> Right. So, it's just a a simple filter [22:26] to filter in uh post ids on the ones [22:29] that you you don't want to be scanned. [22:33] So, you can see here I'm I've actually [22:35] created a little utility plugin of and [22:40] um the only thing that exists inside [22:42] this plugin is the filter itself. So [22:45] it's just edact [22:47] p for pro underscoreexclude_post [22:52] ids and then uh we catch we uh catch the [22:57] excludes ID and we pass in our ids. This [23:00] can be an array of ids. Uh right now I [23:03] only have one ID here. [23:06] >> So I will say this must be an array of [23:09] ids if you want it to actually exclude a [23:11] post. It cannot be a string ID. Um, if [23:15] you pass a string here, it does not [23:16] break because there is error handling, [23:18] but it won't do what you think. So, you [23:21] do have to pass actual an array of [23:23] integer numbers for the post ID. [23:26] >> Right. [23:28] So, let's see what this looks like when [23:30] I go to um a a fullsight scan. [23:37] So, William did uh actually give the [23:40] user feedback in the UI when they have [23:44] excluded IDs. [23:46] Um, so now when you go to uh [23:50] accessibility checker fullsight scan, [23:52] there's a a check summary [23:55] and this is going to show you, you know, [23:58] what's going to be scanned. You know, I [24:00] got 644 posts to be checked. 11 pages [24:03] will be checked. archive pages will not [24:06] be checked because I don't have that [24:07] enabled. And now we have this new uh one [24:11] here. It says one specific post ID is [24:13] set to be excluded from check via the [24:19] excludes filter. And then it shows the [24:22] IDs of the posts that are to be [24:25] excluded. So we're kind of letting you [24:27] know, hey, you've you've done this. And [24:29] we did this uh one to so you have [24:32] assurance that it's it's it's working. [24:34] And two, if you forget to remove it for [24:37] some reason, like if I if I have this uh [24:41] this post and you know I actually do [24:43] want to scan if I have this plugin, this [24:46] custom little plugin and I do actually [24:48] want to scan this page because I've [24:50] resolved why it wasn't scanning. Um you [24:54] know, this will be like, oh, I need to [24:56] disable that plugin and then I can I can [24:58] scan and it goes away. Um, I will also [25:00] call out here that the numbers above [25:02] this that say how many posts or pages to [25:04] be scanned does reflect the excluded [25:06] post post ids. So if you were to remove [25:09] this filler, I believe that number of [25:11] pages goes up by one. [25:15] >> Okay. So I'll disable the utility [25:18] plugin. [25:19] >> It may be a post. I can't remember what [25:21] that ID is, but these numbers should go [25:24] up by one. [25:25] >> It was a page [25:27] >> and that is the same number. So I [25:30] >> is it? [25:31] >> I think it is. Let me take a note of [25:33] that. [25:34] >> Activate. [25:37] >> Do you have to reinitiate? [25:41] >> You shouldn't have to reinitiate the [25:42] scan. That's [25:44] >> that that's I've not I've broken that [25:47] somehow in [25:48] >> you can definitely see that. Um [25:54] when I disable the plugin the you can [25:56] the filter message goes away. And then [25:58] if I reenable it, it it it returns. So [26:03] So William will make a note to update [26:05] this count uh the way he described it. [26:11] >> Anything else on uh excluding post IDs [26:14] from the full site scan? [26:15] >> Um nothing else on this one. Do you have [26:19] a broken page to show someone though? [26:22] >> Because we do have a feature on this [26:25] page. I'd have to Yeah. Yeah. We will [26:29] get to that. That's under a different [26:32] section. But [26:36] so we Yeah, we do have um a new a new [26:40] fullsight scanning feature that William [26:43] is so excited to talk about that he's [26:45] trying to jump ahead. But we're going to [26:47] hold off and we're going to go make [26:49] >> sense to talk about it here. [26:51] >> I know. Um, [26:53] >> let's talk about your stuff, the UX. [26:55] >> Well, we could do it. Let's let's jump [26:57] down. So, we could jump into our pro uh [27:01] scaling and accessibility scanning. So, [27:02] since we're talking about the full site [27:04] scanner, uh let's let's talk about a [27:07] couple of improvements we've made. Um [27:09] while while I grab the little code [27:12] snippet we have to generate a uh [27:15] >> broken page [27:16] >> a failed scan why don't you explain some [27:19] of the performance improvements that [27:20] went into this release? [27:22] >> Yes. So the full site scanner we have in [27:26] this is really quite quy intensive. To [27:29] get some of these numbers and to [27:31] generate the list of IDs we want to scan [27:33] requires us effectively looking at every [27:36] post and an awful lot of the post [27:38] metadata for all of those posts to [27:41] generate the full list. um we were [27:45] gathering that information with [27:47] potentially three or four [27:51] I think it was four individual separate [27:53] queries each that were resulting in very [27:56] similar post ID lists. So what I did was [27:59] I made one of the queries slightly more [28:02] intensive to gather all of that [28:04] information and once all that [28:07] information is gathered then we process [28:09] it in the place where the other queries [28:10] were. So we don't need to query the [28:13] database more than one time other than [28:15] to do additional metadata lookups if [28:17] required later on as part of the scan. [28:20] But when the scan starts, it it really [28:23] it should be almost three times faster [28:25] at generating the ID list. [28:28] And for some sites, small sites like a [28:30] site of this size, the time it takes to [28:33] generate the ID list is really quite [28:35] small. But for a site that might have [28:38] 50,000 pages and post to scan, that that [28:41] can take 15 or more seconds to perform [28:44] each of those queries. [28:46] >> So now it only takes one of those times [28:49] and the rest of it is processed in PHP. [28:53] >> Yeah. I mean performance improvements on [28:55] things like uh you know a scanner of [28:56] sorts like this definitely will net the [28:58] greatest benefits at scale, right? [29:00] >> Yes. that the bigger your site, the [29:03] quicker that quidy has become for you or [29:06] the more time you have saved. And this [29:08] is also in line with the previous [29:10] performance improvements we made. On [29:12] very large sites, it might be seven [29:14] times faster due to those previous [29:16] improvements. But on a small site, it it [29:20] isn't directly measurable how fast those [29:22] queries are. However, it is [29:25] significantly more efficient, even if [29:27] the time doesn't add up on a small [29:29] second. [29:31] Yeah. Yeah. [29:34] Um, we got a request to show our pretty [29:37] little faces while we do the screen [29:38] share. [29:39] >> I didn't realize the screen share was up [29:41] by itself for so long. And [29:42] >> sneeze. [29:45] >> So, we are on camera. William, do not [29:47] pick your nose. Um [29:50] so um [29:55] that is just a little performance [29:57] improvement and we continue are always [29:59] trying to do performance improvements to [30:00] the fullsight scanner. I I think it it [30:03] it I can't underestimate [30:06] how advanced this full-sight scanner is [30:08] and how complex it is and how we are [30:12] continually always working to refine it, [30:14] to make it work smoother, to make it [30:16] work faster, and to make it handle any [30:20] kind of edge case we run into because we [30:22] run into a lot of them when we're [30:23] scanning real websites, right? [30:25] >> Yeah. I also think it's real nice that [30:27] we have this change log where we can [30:29] tell people about those changes because [30:31] that change is entirely invisible. Users [30:34] would just I users that couldn't start [30:36] their scan easily before we'll be able [30:38] to start their scan and they'll be able [30:40] to see a benefit. But the majority of [30:42] users actually don't have a problem [30:45] starting their scan. Their sites are [30:47] small to mediumsized and they didn't [30:49] need this improvement, but they got it [30:51] anyway. [30:52] >> Yep. Totally [30:54] cool. So, let's move on to the next [30:57] goodie and uh that is [31:02] um [31:05] being able to clear out failed scans. [31:07] So, I've got a code snippet here so we [31:10] can [31:12] generate a failed page scan. So, while I [31:15] do this, can you explain what a page [31:17] failed page scan is? Anyway, [31:19] >> so there are usually three different [31:22] scenarios where a page might fail to [31:24] scan. The first one is the page just [31:27] fails to load. Times out. There's some [31:29] issue with that. Um, the other issue [31:31] might be there's a lot of JavaScript [31:34] headers on the page. It breaks our [31:36] scanner because of one of those errors. [31:38] We can't scan the page. Um the third [31:40] issue is [31:43] um you know there's potentially redirect [31:46] or something in the way of our scanner [31:48] actually being run. So there is a few [31:49] reasons why a page might fail to scan [31:52] that. The most common reason is the page [31:55] doesn't load quick enough. But there is [31:58] a fware to increase that time if anyone [31:59] needs it. But that is the most common [32:01] reason for a scan fail is a page timeout [32:04] because we have to load the entire page [32:07] to see it the way a user would see it. [32:10] >> And and a page timeout in in the sense [32:12] that you're speaking is not uh like a [32:15] server timeout. This is our own imposed [32:18] timeout. Right. [32:19] >> Correct. So we will only wait 15 [32:21] seconds. If the page hasn't fully loaded [32:24] in that 15 seconds, we will move on. And [32:26] that is to just prevent the scan being [32:28] infinitely blocked on a page that might [32:30] never hit its load event. And for anyone [32:34] who's a developer, they'll the load [32:36] event is a specific event in the page [32:38] loading order in a browser. And that is [32:42] what we trigger our scan on the load [32:44] event which is effectively when the [32:46] entire page is fully rendered. as much [32:48] of the things have happened on the page [32:50] that would happen for a normal user and [32:53] then we scan it so that we see what [32:54] users are going to see. [32:56] >> Right? So we take those failures and I [32:59] put those in quotes um and we collect [33:02] them and we hold them and then we expose [33:04] them to you at at the end of your scan. [33:07] Um or the scan will refresh on an [33:10] interval so they may pop up before the [33:11] end of the scan. Um, and we expose those [33:15] to you so you can you can troubleshoot [33:17] uh why that page failed. A lot of times [33:20] in my own experience, if I visit that [33:23] page and just let it scan inside the [33:25] editor at an individual level, it will [33:28] it scans and then the the failure goes [33:31] away. Was that a new feature that it [33:32] goes away? [33:33] >> That is a new feature. Previously, the [33:34] list would be static and saved until you [33:37] start a fresh scan. Now, if you [33:38] successfully scan the page, either [33:40] through the front end highlighter or by [33:43] visiting in the editor, once it [33:45] successfully scans, it will be removed [33:46] from the fails list. [33:48] >> Yeah. Cool. So, I have a little code [33:50] snippet that William wrote here. This [33:52] will actually just hit the uh the uh the [33:55] endpoint here and trigger a fail. [33:57] >> You have to run this whale in the middle [34:00] of the scan. [34:01] >> Oh, it has to be running. Okay. Okay. [34:03] Hold on. Let me [34:07] run accessibility. Okay. So, [34:11] so we are running a scan [34:20] and I've got quite a few post. So, uh [34:24] >> this is going to take a while, but you [34:25] don't need to wait till the scan [34:26] completes. You can fail this post now [34:28] and reload this page. [34:31] >> Okay, cool. So I will trigger the [34:33] script. [34:35] >> Oh, what happened? I can't read that. [34:39] >> It for 40 or three for forbidden. [34:44] >> Um, is the URL correct there? I I can't [34:48] read it. You'll need to read it out. [34:49] >> It should be correct. [34:51] uh wp-json/acessibility-checker- [34:56] version one- [34:59] slash post-scan- [35:01] results. [35:02] >> Yeah, that is correct. Is this post ID a [35:05] real post ID? [35:07] >> Uh it was at one point. Let's go find [35:11] this a post ID. Hold on. [35:14] 12900. [35:15] >> Oh, the fact that that's not a real post [35:17] ID is the reason why the counts didn't [35:18] update. [35:21] Oh, well, [35:23] let's test that. That's a good catch. [35:26] So, I'm going to Okay, there we go. I [35:28] got the failure. [35:30] It returned back a success in the [35:32] console log. So, now I'm going to [35:34] refresh. So, now I have a failure on an [35:36] actual existing post ID. So, these are [35:39] these are sandbox sites, local sites [35:42] that we use for testing. And William and [35:43] I bang on these things really hard. And [35:46] we delete post and we create posts. [35:48] That's why that post ID didn't exist. So [35:50] now I'm using an actual post ID. So I [35:53] have a scan failure. You can open this [35:55] up. And this has been here for a long [35:58] time, but we have updated this now. So [36:03] >> yeah. So there is three things new here. [36:06] First off, you can see there's an action [36:08] button. Clear on the individual item. [36:11] There's also a clear all button after [36:13] the entire list. Um the clear all button [36:16] will wipe all of these failures in one [36:18] go. The individual action will clear [36:22] just one post as you go. Um we I did [36:25] also add a template column here. A [36:28] customer told me that this would be [36:30] quite useful for them to know whether a [36:32] specific template was causing their [36:34] failures or not. So there's now the [36:37] template column that can be referenced. [36:39] And in my experience, it is actually [36:42] quite common that someone has a slow [36:44] template causing a lot of these [36:46] timeouts. So this helps them identify [36:49] that now. [36:50] >> And if you want to pick any one of these [36:52] clear buttons and just click them, it [36:54] will go away. [36:57] Issue gone. And if you refresh the page, [36:59] the accordion won't show again. It is [37:02] resolved. And you can't see it cuz [37:04] you're zoomed in, but there was an admin [37:05] notification that appears and it gets [37:08] read out by the screen reader. [37:13] >> Yeah. Let me uh let me grab that snippet [37:16] again [37:17] because I want to show [37:20] that post that post ID was 12900. [37:24] Um [37:29] all right. So now I have the failure [37:31] again. So, one cool feature, like I [37:34] said, a lot of times when the page fails [37:37] in the fullsight scan, it it could be [37:39] that your the scanner is running too [37:41] fast and for for it's running too fast [37:44] for your server resources. And we do [37:47] have a setting where you can slow that [37:48] down to prevent these. And um but what I [37:52] found is if you just go to the p page, [37:54] it'll scan it. So if I if I open up this [37:58] post ID, it automatically scans [38:01] and then [38:04] then if I refresh that now clears out [38:07] that issue whereas before it it [38:09] persisted. [38:11] >> So so I can kind of in real time fix [38:14] some of my failures while the scan's [38:16] running. Um [38:19] >> um that list does stay present once the [38:21] scan completes. So you can work through [38:23] that list after the scan as well. [38:26] >> Right. [38:27] >> And it is almost always going to scan [38:29] when you visit the page in the editor. [38:34] >> Yep. [38:35] So let me stop this scan real quick. And [38:39] we're going to jump all the way back and [38:41] we're going to go back to the uh [38:43] excluding ids for just a moment to um [38:50] to check and see if the the count is [38:53] actually function functioning correctly [38:55] when an actual post ID is used. So we [38:58] got 644 posts and 11 pages. If I open [39:03] this [39:05] plugin [39:07] and I update this post ID to 12900, [39:10] which is an [39:12] a real post ID, I go back to fullsight [39:16] scan. [39:18] And I refresh. Oh, got to go to plugins [39:21] and enable this plugin. [39:28] And now I have 643. So we're down one. [39:31] So I excluded it and the count actually [39:34] went went down. [39:36] >> I was worried there for a second. [39:37] >> Yeah. No, you did good. [39:40] >> Works as intended. Maybe as an [39:42] additional verification layer, I should [39:43] verify that these IDs do exist prior to [39:47] showing them. [39:50] >> Cool. So that's the fullsight scanner. [39:52] Uh all the lovely improvements. [39:56] And uh [39:58] next we've added a new fix. [40:02] So if you're not aware already, [40:04] accessibility checker comes with a a [40:06] whole uh list of fixes that you can use [40:09] to uh programmatically fix accessibility [40:13] issues on your website uh with with one [40:16] click or you know two or three. It [40:18] depends. But um [40:21] so uh you can see all of our fixes here [40:23] on this page. I'll zoom in a little bit. [40:26] Um, so we've got several fixes to do [40:31] uh to cover a lot of areas, but we've [40:35] added a new one, [40:37] and this one is the empty search [40:40] handling. Force WordPress to show a [40:43] search results page when a search is [40:46] submitted with an empty uh query. So, [40:50] the way that this works out of the box, [40:54] and this is actually quite a quite [40:56] interesting one, and this is this is a [40:57] fix that's also in Joe Dawson's uh WP [41:01] accessibility plugin, and um you know, [41:05] we we pulled this over uh because I [41:08] think there was actually a client need [41:09] for this um the clients that was already [41:12] using our plug-in, but wanted to [41:14] actually use this as well. And um so we [41:17] pulled it over, made some modifications, [41:19] we submitted the modifications back to [41:21] Joe's plugin so that both plugins now [41:24] are have parody of sorts and are [41:27] improved. So let me take a look at a [41:30] search page. [41:33] So if I go to search, [41:37] so if you don't know, you can just [41:39] throw, you know, in a query parameter [41:41] and search for for something, you know, [41:43] like you know, tests. I write test in [41:46] this website a million times. I'll get a [41:47] bunch of posts. So, and when I actually [41:50] pass through a value on that query [41:53] parameter, I get the posts that I I [41:55] should get. But what happens by default [41:58] in WordPress is that if you pass in an [42:01] empty value uh you know you get search [42:06] results for and it says not you know [42:08] it's just blank and then uh I think it [42:11] returns [42:13] >> it returns effectively everything. The [42:15] reason this number is different to the [42:17] number in the back end is because it [42:19] actually is literally searching for no [42:21] space characters. So, if there's like an [42:23] empty return space in a post or [42:25] whatever, but this is this is an [42:27] interesting generally unseen [42:29] accessibility issue for people with any [42:31] kind of um cognitive disabilities [42:35] >> where this doesn't really make any [42:38] sense. [42:39] >> And, you know, this really doesn't make [42:40] a lot of sense for me either, but for [42:43] someone who might not [42:45] >> fully get what's going on here, this [42:47] could be incredibly confusing. [42:49] >> Yeah. For somebody that can't see what's [42:51] going on. Yeah. Yeah. [42:52] >> Um because essentially you're passing [42:54] nothing but you're getting a bunch of [42:55] results. And so it's like why? [42:59] So um now we can force uh force an error [43:03] on empty search results by toggling this [43:06] uh setting and hitting save. So now when [43:11] I go back to the site and I search for [43:13] an empty string, [43:16] I don't get any post and we get a [43:19] message. sorry, but nothing matches your [43:22] search terms. Please try again with some [43:24] different keywords. So, we're forcing an [43:26] error. And on this theme, there's a a [43:29] search box for you to search a different [43:30] keyword. [43:32] So, this just cleans it up a little bit. [43:34] It gives context to to to what's going [43:37] on. Like, if nothing is sent over, then [43:39] nothing should be shown. I I also think [43:43] this is one of these fixes that has no [43:47] it has no negative [43:49] that this should just be how core [43:51] behaves core. [43:53] >> Um I actually think everyone can just [43:54] enable this and if they have a search [43:56] box on their website they might help [43:59] some users for free that this is a free [44:02] fix. Nothing but I mean it's also in the [44:05] free plugin but this is an easy win. [44:08] >> Yep. Totally. [44:10] So, that is our new fix. [44:13] We're always uh thinking about and pro [44:16] prototyping new fixes that we have [44:19] coming down the line. And we're doing [44:21] everything we can to not just surf [44:25] service surface accessibility issues in [44:26] your website, but also be there to to [44:29] help you fix those right away and to [44:31] make your website accessibility and to [44:33] make those issue counts go down. [44:38] Um, cool. So, the next thing [44:42] is if you were in our last live stream [44:45] or watched our last live stream after [44:47] the fact, uh we did kind of a big UI [44:52] update on the the sidebar, which we [44:55] spoke about a minute ago. Um so, we have [44:58] a new sidebar, but that new sidebar [45:01] comes with a new UI. We updated our [45:04] metab box, which I think I have disabled [45:06] right now. [45:08] Let me turn it back on. Go to settings, [45:12] show metabox. [45:18] So, we have our new sidebar, which our [45:20] sidebar kind of pushed us to think about [45:22] the UI and the user experience and what [45:25] it should look like and a little bit how [45:28] it could dovetail into WordPress a [45:30] little more seamlessly and to kind of [45:33] just modernize the look of accessibility [45:36] checker because accessibility checker is [45:38] is five years old and when you're five [45:41] years old, it's time to start thinking [45:43] about how you look and update update [45:46] updating your [45:48] your appearance. So [45:50] >> I must have missed that one when I [45:51] turned five. [45:53] >> That's right. [45:55] Uh [45:57] so [45:58] so we we changed it to sidebar and then [46:01] we kind of mirrored that over to the [46:04] metab box inside the free plugin. And [46:06] what we've done in this update is we've [46:09] taken that a step further and started [46:11] translating the termin ter terminology [46:13] and the UI um elements into the rest of [46:18] the the pro plugin. Um so let's take a [46:22] look at that. The the first place where [46:23] you notice it is on [46:26] if you're running uh accessibility [46:28] checker pro. Um, [46:31] actually this is in free too, but uh [46:33] there's more UI here to look at. If [46:35] you're in pro, you get some more stats. [46:38] So, we've updated our dashboard widget [46:41] with just some of the new colors. U we [46:45] actually adhere, we decided to inherit [46:49] the uh the users color palette settings. [46:54] Um, and in WordPress 7.0, it's this this [46:56] bright blue. Um, but you can change it [46:59] if it doesn't meet color contrast. It's [47:02] kind of on you as a user because you can [47:05] change this to something that does have [47:07] contrast. [47:08] >> I actually got a screenshot from a [47:10] customer on support who had the red [47:12] theme on. It was interesting to see the [47:14] full sight scan [47:16] >> with the red. [47:17] >> Yeah. Yeah. I'll I'll demo that just for [47:20] fun here in a minute. But um [47:23] so we updated this with some colors and [47:25] just some layout changes just to and we [47:27] brought in our iconography and we [47:30] brought in our new terminology. You [47:32] know, we don't think we don't call [47:33] things errors anymore. We call them [47:34] problems. We don't call them warnings [47:36] anymore. We call uh issues that need [47:38] need review. And um and we we've just [47:43] kind of cleaned up the UI a bit here. um [47:45] and and using core buttons instead of [47:48] our own buttons and adding, you know, uh [47:52] opens some new window indicators [47:55] um throughout this. So, this is just [47:57] kind of a a design cleanup and uh um [48:01] just to bring it in alignment with the [48:03] free plugin. [48:06] The next place is the welcome screen. [48:10] So, the welcome screen, we uh kind of [48:13] brought over the same thing. We removed [48:15] the the heavy background colors and [48:18] brought in our iconography and our [48:20] terminology and and kind of the the same [48:24] color into the the welcome page. Uh, I I [48:28] don't think there's anything major on [48:30] here other than just a design change and [48:33] some, you know, some button changes, a [48:35] few layout, just kind of padding things [48:38] to clean this up a little bit on the [48:41] welcome page. [48:43] And then you'll notice as you go through [48:46] uh open issues, you'll see uh uh we've [48:51] brought in the new icons on the the [48:55] initial open issues page that shows all [48:57] of the issues on the website. Um and we [49:01] brought in the terminology. We've [49:02] updated the severity label here to match [49:05] the modified severity label we used in [49:08] the sidebar. [49:10] But other than that, um, this kind of [49:13] remains the same. If you go into an [49:16] issue, uh, we've kind of just brought [49:19] that over as well, the same kind of [49:21] iconography and terminology and updated [49:25] those throughout the interface and tried [49:28] not to be obtrusive or modify this too [49:31] much with this first pass. [49:33] So um in the sidebar it doesn't you can [49:37] see dismissed issues here. It doesn't [49:40] say ignored anymore. We have gone away [49:43] from using the word ignore [49:45] and in favor of dismiss because we don't [49:48] want you to ignore accessibility issues. [49:51] You can dismiss them if you have [49:53] confirmed they are in fact not issues. [49:57] And then global ignores is now global [49:59] dismissals. And uh so just updating all [50:03] of that kind of terminology throughout [50:06] the the plugin. If I go to the fullsight [50:08] scanner, which we've been looking at [50:10] already for quite some time on this uh [50:13] live stream, but [50:16] there a lot changed here, but it doesn't [50:18] look like a lot changed here because we [50:21] were using um kind of our really own out [50:25] of the box buttons and things like that. [50:27] And we we have removed stripped out [50:30] those custom button styles in favor of [50:32] just adopting what what what core what's [50:35] in core the core button styles. And uh [50:38] this will be more apparent too once [50:40] WordPress uh 70 comes out here in a [50:43] couple weeks. [50:45] So I've got a blue button here now which [50:48] is just your core button. when I start a [50:49] scan, [50:51] you know, we've updated these buttons [50:53] and [50:55] kind of something I've been wanting to [50:56] do for a while that I haven't is our [51:00] scanner will run and you know, of [51:02] course, if you got a lot of pages, it [51:04] doesn't look like it the bar is loading [51:06] very fast, but I wanted to give the [51:08] impression that it's doing something [51:10] because it is doing something like if [51:13] you know if I inspect the page and I go [51:15] to the network tab, you can you can see [51:18] that our scan scanner is doing [51:19] something. Um, you can I mean you can [51:22] tell it's very active. It's pulling up a [51:24] page. It's scanning it, sending the [51:26] results back. It's clo it's closing that [51:28] and redoing that over and over again. [51:31] Um, so we I wanted to add these stripes [51:34] in um what they call them candy stripes [51:37] I think. [51:38] >> I think so. And uh I wanted to give a [51:40] little bit of movement to show kind of [51:43] hey even though the bar only goes uh you [51:47] know horizontally every scan every page [51:51] scan completion uh that also to give [51:54] some movement in between those those [51:56] movements that hey it's doing something [51:58] and it kind of just looks kind of fun. [52:02] But to what William was saying about um [52:06] the the the color palette. [52:11] So I don't know you want me to go to to [52:14] like a really ugly one. [52:15] >> Any of these is quite different. The one [52:16] I seen was this one. The red one. Sun. [52:18] >> Sunshine. So now if you need [52:25] in the editor if you need to have a [52:27] certain level of color contrast I would [52:30] probably stick with the default. [52:33] But um so I've switched the the theme. [52:36] If I refresh the page then our our [52:38] scanner adopts [52:41] you know whatever you've chosen as as [52:43] your uh profile color the everything [52:46] changes. And we're just doing what we [52:50] can to make the the plug-in kind of fit [52:53] in with with the core a little more. And [52:56] you can see it here. You can see it on [52:57] the [52:59] >> uh dashboard. Like it brings in in the [53:02] the theme colors. So I [53:04] >> I think I might be in the minority of [53:06] users here, but I actually like my [53:08] plugins to look like WordPress. Um, a [53:12] lot of plugins try and look quite [53:14] different and if it's quite [53:17] obtuse to me when I'm browsing the [53:19] dashboard that things look all kinds of [53:22] different ways depending on what page [53:23] you're on. So, I I really like this [53:25] change. Everything in our plug-in should [53:28] look like WordPress because it is inside [53:31] WordPress. That's something I believe. [53:35] Not every plug-in believes it, but now [53:37] we do. [53:39] >> Yeah. Yeah. [53:41] So, I prefer the default theme and the [53:45] default theme is changing [53:48] um with WordPress 7.0. So, it looks a [53:50] little bit different. Um is the current [53:53] one fresh? Is that what the current one [53:55] is? [53:55] >> Yes, the Well, it's called default I [53:57] think in 6.9. [54:00] Um it's been renamed to fresh in [54:03] >> and 7.0. [54:05] >> There's a new default. Yeah. [54:07] >> Yeah. So if I go back to the the default [54:10] then here there we go. So [54:14] that is some of the UI stuff that we [54:17] have gone through and cleaned up. In [54:20] doing that uh you know anytime you go [54:22] into software and you start messing with [54:24] things you start finding other things. [54:26] We updated [54:28] um [54:30] you know these labels here are [54:33] translatable now. Like you find things [54:36] that weren't translated and and you fix [54:39] the accessibility on them and you fix [54:41] the translat [54:43] make them translatable. And we found [54:46] several areas throughout the plug-in um [54:49] and that that we did uh translation [54:53] improvements on. And you know, we have [54:55] our plug-in translated into 32 [54:58] languages, something like that. [55:00] >> I think it's 35 now. [55:02] >> Oh, is it up to 35? And um we're con, [55:06] you know, continually making [55:08] improvements to uh make sure everything [55:10] is uh as translatable as possible. [55:16] So, and uh we made we did some [55:18] accessibility fixes as far as UI in the [55:21] settings panel. We did find um a couple [55:25] orphaned labels and we went through and [55:28] uh fixed those and attached those to the [55:31] proper setting so that they read out [55:33] properly for screen readers. And this is [55:35] just us practicing what we preach, [55:38] finding accessibility issues in our own [55:40] plug-in and fixing them. [55:42] Um so I think that's kind of the UI uh [55:48] improvements that we've done. [55:51] Uh I think we have one last thing to [55:53] talk about, William. It's kind of our [55:55] smarter detection [55:57] >> and updates to our missing transcript. [56:00] >> Yeah. So the the missing transcript [56:03] check we have loosely the way it works [56:06] is it searches around about a video to [56:09] try and find any reference to a [56:12] transcript or any link that might be to [56:14] a transcript to tell you this there's a [56:17] video on this page. It doesn't have a [56:19] transcript. It is a AAA requirement to [56:22] provide transcripts for video. It is it [56:26] double A no it is a AAA requirement. Um [56:29] so it is a needs warning in our plug-in [56:33] um or needs review so that it so users [56:37] look to check for it and previously we [56:40] have made a lot of enhancements to that [56:42] rule over time about how it detects the [56:44] transcripts but something that [56:46] interesting came in recently is we look [56:48] for nearby words to say that there's a [56:52] transcript and nearby is relative. um it [56:57] could be visually very close but in the [56:59] content of the page the HTML markup [57:01] actually be relatively quite far away [57:04] and that is what we discovered with the [57:06] specific format of Beaver Builder video [57:08] inputs. [57:10] Um it could be I think it was four [57:13] levels away in terms of DOM depth which [57:16] our check just was considering too far [57:20] and as such we actually increased the [57:22] limit. So it will now look five levels [57:24] of DOM depth away to try and find the [57:26] transcript which is really quite far in [57:30] terms of the DOM but as we recently [57:34] found is actually really quite close [57:36] visually in certain builders. Beaver [57:38] Builder was where we discovered this at [57:40] first but I did also figure out that [57:42] this is a problem in certain element [57:45] permutations of videos as well. So now [57:48] the missing transcript video will search [57:50] further to try and discover the [57:52] transcript before it determines it's [57:54] just too far away. And that does fix a [57:56] specific support issue for one customer. [58:00] But I presume anyone who used [58:02] BeaverBuilder may have ran into this and [58:05] we didn't know because we we'd never [58:08] tested that specific format of [58:11] connecting the video with the [58:12] transcript. [58:13] >> Yeah. So it's pesky page builders, [58:16] right? [58:17] Yeah, we get a bit better every time. So [58:20] reports an issue, we fix it. [58:22] >> Actually just this morning fixed an [58:24] issue with cadence [58:25] >> in the a pro fix for the adding file [58:29] type and size. Um cadence also has a [58:33] similar issue where the link is too far [58:36] away from the content if it's an overlay [58:38] link. So [58:41] >> that'll also be fixed in the next [58:43] release hopefully. [58:45] >> Yeah. So that's, you know, we're always [58:48] trying to improve the rules and it and [58:51] our users give us giving us feedback [58:54] helps us have context and helps us test [58:56] a a whole world of uh page builders and [58:59] themes and things like that that we [59:01] don't always have at our disposal. [59:04] >> And a lot of these page builders change [59:06] so frequently that [59:08] >> you know this this issue with the ad [59:10] fail or this BeaverBuilder issue might [59:13] not have existed a year ago. And it does [59:16] now and it should be resolved forever [59:18] hopefully. Fingers crossed. But [59:20] >> yeah, [59:21] >> wait and see if Before change how they [59:23] output their video. I am hopeful they [59:25] change it so that you can have your [59:26] transcripts closer in the DOM. [59:29] >> Yeah, we will see. [59:32] >> Cool. Well, I mean, that's just, you [59:35] know, that's how we're that I think all [59:38] these things sum up how we're uh trying [59:41] to give you more control where it [59:43] matters and we're giving you the UI [59:46] fixes and visual improvements, these [59:49] smarter detection, which we just talked [59:51] about, and um the procanning [59:54] functionality and performance [59:56] improvements that we've made in these [59:58] releases. And it just kind of it's just [60:01] us trying to improve our software to [60:04] make it as usable and helpful to our [60:06] users as possible. We have a few minutes [60:09] left. Well, we're a few minutes over, [60:11] but we can go as long as we want. Do we [60:14] want to tease what's next? [60:16] >> Um, do you have anything ready to tease? [60:19] >> I I don't want to show it, but do we [60:21] want to talk about it? [60:23] >> Yeah. Well, yeah, we can. I mean, I [60:25] don't know what one you're talking about [60:26] because we have quite a number of [60:27] things. [60:28] >> That's right. We got a lot of things in [60:29] the so we are uh we have teased this [60:33] before and you know I want to bring it [60:35] up again because it's you know it's kind [60:38] of the the thing that we're working on [60:40] pushing through but our email reports [60:43] will be launching very soon hopefully [60:46] next release or maybe the one after [60:49] depending on how we do this. There's [60:52] some complexities around uh u generating [60:55] email reports because we now uh will [60:59] have a connection between accessibility [61:01] checker and the e the my.equalized [61:04] website. If you're not familiar with [61:06] what my.agalizeddigital.com [61:09] is, it's our dashboard for any of our [61:11] customers that have uh either downloaded [61:14] a free accessibility checker plug plugin [61:18] um or one of our premium plugins, bought [61:21] a course, [61:22] um affiliates. So, we have a dashboard. [61:26] So, our email reports were are going to [61:29] let you uh attach your free or your paid [61:34] plugin. If you're have a paid plugin, [61:36] it's already attached to the dashboard. [61:38] Um but we now will let free customers [61:41] attach and to the dashboard and then it [61:44] will get uh [61:47] it will get audit summaries and then it [61:49] will process those and send them to you [61:52] and right into your inbox and show you [61:56] uh any improvement or regression in your [61:59] accessibility uh from week to week. [62:03] I'm looking forward to getting this [62:04] feature [62:06] out. [62:07] >> I don't want to say done. I think [62:09] there's still some work some [62:10] improvements there, but I would love to [62:13] get this actually released. And this is [62:15] a really big change. The the ability for [62:18] free plug-in users to connect to my do [62:22] get, you know, get the email reports is [62:24] is a big it's a really big change. [62:27] Previously only paid customers would [62:31] have any functionality inside of the [62:32] dashboard. Free customers will too. [62:36] That's a huge leap forward. You know, [62:38] we're not just building these things for [62:40] the people that pay us. We're building [62:42] them for everyone. That's that's the [62:44] point. Accessibility is for all users. [62:49] >> Man, couldn't have said better myself, [62:51] William. [62:52] >> I think I'm going to need to write that [62:53] one down. [62:54] >> That's right. Write it down. That's a [62:55] tweetable moment right there. Yeah, [62:57] >> we still call them tweets. That's a [62:58] postable moment right there. [63:01] >> So, no, perfectly. Very well said. And I [63:05] think that sums it all up. And I think [63:07] with that, we're going to call this a uh [63:10] we're going to call this into our live [63:12] stream. We thank anybody that watches uh [63:14] here live with us or anybody watching [63:16] later to go check out accessibility [63:19] checker free. Uh if you like it already [63:22] uh or if you like it after using it, [63:24] please give us a fivestar review on [63:26] WordPress.org. We appreciate it and uh [63:29] we appreciate your support and we look [63:31] forward to uh bringing new features to [63:33] you in the next live stream. See you. [63:37] Back.  📄 **Full text:** ![[Full Document Contents/Articles/More Control, Less Friction|More Control, Less Friction, YouTube]] ## Highlights - >> All right. Very good. I didn't have that written down in my notes off the top of my head. Living accessibility checker daily. Got those releases stuck in my brain. Uh, cool. So, more control where it matters. Let's start with the first one here, William. Yeah. So, we have added some CSS modifier classes to our plug-in for the new window warning row. This has been ([View Highlight](https://read.readwise.io/read/01kmzmg7qd22td9bhrw43fe4q0)) - Tags: 👻 ai highlighted - problem. >> It is. >> So I can, you know, I can get rid of Yos. I can get rid of our accessibility checker, but we, you know, we've kind of gone that extra mile to make sure it's always here for you in case you forget or, you know, you don't know to go to the ellipsies menu. So cool. Um, so that's kind of a simple feature that had a little bit of thought to it and, ([View Highlight](https://read.readwise.io/read/01kmzmg7s0nvaff4nvx4x6kbcp)) - Tags: 👻 ai highlighted - I go to um a a fullsight scan. So, William did uh actually give the user feedback in the UI when they have excluded IDs. Um, so now when you go to uh accessibility checker fullsight scan, there's a a check summary and this is going to show you, you know, what's going to be scanned. You know, I ([View Highlight](https://read.readwise.io/read/01kmzmg7tj9cqv3zr65wyejhst)) - Tags: 👻 ai highlighted - assurance that it's it's it's working. And two, if you forget to remove it for some reason, like if I if I have this uh this post and you know I actually do want to scan if I have this plugin, this custom little plugin and I do actually want to scan this page because I've resolved why it wasn't scanning. Um you know, this will be like, oh, I need to disable that plugin and then I can I can scan and it goes away. Um, I will also ([View Highlight](https://read.readwise.io/read/01kmzmg7yd5c0qmkfxmy1p10ct)) - Tags: 👻 ai highlighted - scaling and accessibility scanning. So, since we're talking about the full site scanner, uh let's let's talk about a couple of improvements we've made. Um while while I grab the little code snippet we have to generate a uh >> broken page >> a failed scan why don't you explain some of the performance improvements that went into this release? >> Yes. So the full site scanner we have in this is really quite quy intensive. To get some of these numbers and to ([View Highlight](https://read.readwise.io/read/01kmzmg82g7mwb7ngb7yren428)) - Tags: 👻 ai highlighted - that change is entirely invisible. Users would just I users that couldn't start their scan easily before we'll be able to start their scan and they'll be able to see a benefit. But the majority of users actually don't have a problem starting their scan. Their sites are small to mediumsized and they didn't need this improvement, but they got it anyway. >> Yep. Totally cool. So, let's move on to the next goodie and uh that is ([View Highlight](https://read.readwise.io/read/01kmzmg8809ytk9t6m498w5rbk)) - Tags: 👻 ai highlighted - away. Was that a new feature that it goes away? >> That is a new feature. Previously, the list would be static and saved until you start a fresh scan. Now, if you successfully scan the page, either through the front end highlighter or by visiting in the editor, once it successfully scans, it will be removed from the fails list. >> Yeah. Cool. So, I have a little code snippet that William wrote here. This will actually just hit the uh the uh the endpoint here and trigger a fail. >> You have to run this whale in the middle ([View Highlight](https://read.readwise.io/read/01kmzmg8embd5kxfwajqa1pvdh)) - Tags: 👻 ai highlighted - of the scan. >> Oh, it has to be running. Okay. Okay. Hold on. Let me run accessibility. Okay. So, so we are running a scan and I've got quite a few post. So, uh >> this is going to take a while, but you don't need to wait till the scan completes. You can fail this post now and reload this page. ([View Highlight](https://read.readwise.io/read/01kmzmg8mk7a9kwyzbxvbe13zp)) - Tags: 👻 ai highlighted - fix. Nothing but I mean it's also in the free plugin but this is an easy win. >> Yep. Totally. So, that is our new fix. We're always uh thinking about and pro prototyping new fixes that we have coming down the line. And we're doing everything we can to not just surf service surface accessibility issues in your website, but also be there to to help you fix those right away and to ([View Highlight](https://read.readwise.io/read/01kmzmg8ska1kr4aa97mtktgkt)) - Tags: 👻 ai highlighted - proper setting so that they read out properly for screen readers. And this is just us practicing what we preach, finding accessibility issues in our own plug-in and fixing them. Um so I think that's kind of the UI uh improvements that we've done. Uh I think we have one last thing to talk about, William. It's kind of our smarter detection >> and updates to our missing transcript. ([View Highlight](https://read.readwise.io/read/01kmzmg9189hng1n444hxjek5n)) - Tags: 👻 ai highlighted