New Highlighter, Email Reports, and Settings Tools

New Highlighter, Email Reports, and Settings Tools ![rw-book-cover](https://img.youtube.com/vi/DP_J5pr1CtI/maxresdefault.jpg) 🔗 **Source:** [New Highlighter, Email Reports, and Settings Tools](https://www.youtube.com/watch?v=DP_J5pr1CtI) > [!note]+ Document Notes > tags: #wordpress #accessibility #email-reports #screen-reader-text #frontend-highlighter > author: Equalize Digital > source: YouTube Live Stream > reference: https://www.youtube.com/watch?v=DP_J5pr1CtI > date created: 2024-11-15 14:30 > > # 🏷️ Title: New Highlighter, Email Reports, and Settings Tools >  ## 🧰 Action Inbox - [H1] Set up email reports for accessibility monitoring — enables weekly summary reports #accessibility - [H2] Implement screen reader text formatting for better link context — improves navigation experience #screen-reader-text - [H3] Test new frontend highlighter features for accessibility remediation — enhanced UI and functionality #frontend-tools ## 🧭 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/accessibility-checker) - [WordPress.org Plugin Repository](https://wordpress.org/plugins) - [My Equalize Digital Dashboard](https://my.equalizedigital.com) ## 📝 Summary - Equalize Digital released major updates to their Accessibility Checker WordPress plugin (v1.4.0.0) - Three key features launched: automated email reports, screen reader text formatting, and redesigned frontend highlighter - Email reports now available for both free and pro users with weekly accessibility summaries - New screen reader text format allows content editors to add hidden descriptive text without developer skills - Frontend highlighter received complete UI overhaul with improved functionality and upcoming features preview ## 📖 Main Content The Accessibility Checker plugin introduces significant workflow improvements for WordPress accessibility management. Email reports solve the challenge of tracking site-wide accessibility trends, particularly for stakeholders who don't regularly log into WordPress. The screen reader text formatter democratizes accessibility improvements by enabling content creators to add contextual information without coding knowledge. The redesigned frontend highlighter consolidates functionality while preparing for advanced features like heading maps and tab order visualization. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/DP_J5pr1CtI?t=0) — [H1] Live stream introduction and overview - Key idea: Monthly live stream covering three major accessibility checker updates - Evidence: "New highlighter, email reports, and settings tools - that's a lot" #### ⏱️ [02:30](https://youtu.be/DP_J5pr1CtI?t=150) — [H1] Email reports complexity and challenges - Key idea: Email feature took much longer than expected due to technical hurdles - Evidence: "Way harder than it should have been... email is horrible" #### ⏱️ [04:15](https://youtu.be/DP_J5pr1CtI?t=255) — [H2] Free user license key requirement - Key idea: Free users now need license keys to access email reports feature - Evidence: "Free users did not have a license key, which was immediately a blocker" #### ⏱️ [08:30](https://youtu.be/DP_J5pr1CtI?t=510) — [H2] Email report setup for free users - Key idea: Simple activation process through settings with license key entry - Evidence: "Click the enable email reports button. It will activate and you'll be redirected" #### ⏱️ [12:45](https://youtu.be/DP_J5pr1CtI?t=765) — [H2] Pro user email setup process - Key idea: Pro users get one-click activation using existing license keys - Evidence: "Since you already have a license key... all you have to do is click enable email reports" #### ⏱️ [15:20](https://youtu.be/DP_J5pr1CtI?t=920) — [H1] Free vs Pro email report content differences - Key idea: Pro users receive detailed breakdowns while free users get basic summaries - Evidence: "Free gets summary data... pro gets that data plus a little bit more" #### ⏱️ [18:45](https://youtu.be/DP_J5pr1CtI?t=1125) — [H2] Historical trend tracking in reports - Key idea: Weekly comparison data helps identify accessibility progress or regression - Evidence: "Up two from my last email... you can kind of see now I can go 'what happened?'" #### ⏱️ [22:30](https://youtu.be/DP_J5pr1CtI?t=1350) — [H2] Screen reader text format introduction - Key idea: New formatting option allows hidden descriptive text for screen readers - Evidence: "Help us give context to screen reader users and not create verbose descriptions for visual users" #### ⏱️ [25:15](https://youtu.be/DP_J5pr1CtI?t=1515) — [H2] Screen reader text implementation example - Key idea: Ambiguous links can be enhanced with hidden descriptive context - Evidence: "Learn more about what? Like... you want to describe it without being redundant visually" #### ⏱️ [28:00](https://youtu.be/DP_J5pr1CtI?t=1680) — [H3] Editor visibility controls for screen reader text - Key idea: Toggle option controls whether hidden text appears during editing - Evidence: "Always show screen reader text... so that you don't ever forget or lose the screen reader text" #### ⏱️ [31:20](https://youtu.be/DP_J5pr1CtI?t=1880) — [H2] Full Site Editor compatibility - Key idea: Screen reader text formatting works in WordPress Full Site Editor - Evidence: "We actually made it work inside the full site editor as well" #### ⏱️ [34:45](https://youtu.be/DP_J5pr1CtI?t=2085) — [H1] Frontend highlighter redesign overview - Key idea: Complete UI overhaul to align with backend changes and prepare for new features - Evidence: "Time to bring the front end highlighter in line with some of those UI changes" #### ⏱️ [37:30](https://youtu.be/DP_J5pr1CtI?t=2250) — [H2] Unified panel design and actions menu - Key idea: Consolidated interface with hidden actions menu reduces visual clutter - Evidence: "We've created an ellipses menu... expose these actions without cluttering the UI" #### ⏱️ [41:15](https://youtu.be/DP_J5pr1CtI?t=2475) — [H2] Panel positioning and docking features - Key idea: Flexible positioning options including drag-and-drop and docked modes - Evidence: "Click and drag it wherever I want it... dock the panel... pushes the page over" #### ⏱️ [45:00](https://youtu.be/DP_J5pr1CtI?t=2700) — [H3] Enhanced content display in highlighter - Key idea: More detailed issue information including WCAG guidelines and explanations - Evidence: "Title... problem or needs review badges... WCAG guideline... severity... toggle to show explanation" #### ⏱️ [48:30](https://youtu.be/DP_J5pr1CtI?t=2910) — [H1] Preview of upcoming features - Key idea: New tabs for headings map, landmarks, and tab order visualization - Evidence: "Four tabs... headings, landmarks, and tab order... hoping to get out pretty soon" #### ⏱️ [51:45](https://youtu.be/DP_J5pr1CtI?t=3105) — [H2] Headings map functionality demonstration - Key idea: Visual heading hierarchy with error detection for skipped levels - Evidence: "H2 then the next one's an H6... highlighted in red with warning icon" #### ⏱️ [54:20](https://youtu.be/DP_J5pr1CtI?t=3260) — [H3] Tab order visualization preview - Key idea: Visual representation of keyboard navigation flow across page elements - Evidence: "Visual representation of tab order... focusable elements have red circle with number" ## 📚 References - [Accessibility Checker Free Plugin](https://wordpress.org/plugins/accessibility-checker/) - [Equalize Digital Website](https://equalizedigital.com) - [WCAG Guidelines](https://www.w3.org/WAI/WCAG21/quickref/) ## 🗣️ Paraphrase - Email reports provide automated weekly accessibility summaries delivered to stakeholders, eliminating the need for manual WordPress dashboard checking - Screen reader text formatting democratizes accessibility by letting content editors add descriptive context without requiring developer intervention - The redesigned frontend highlighter consolidates functionality while preparing the interface for advanced diagnostic tools like heading maps and tab order visualization ## 📰 Newsletter The Accessibility Checker plugin just launched game-changing updates that make WordPress accessibility monitoring and remediation significantly easier. The new automated email reports deliver weekly accessibility summaries straight to your inbox, perfect for keeping stakeholders informed without requiring WordPress login access. Content creators can now add screen reader context using the new formatting tool - no coding required! The redesigned frontend highlighter provides a cleaner interface while previewing exciting upcoming features like visual heading maps and tab order diagnostics. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Explore integrating accessibility reporting features into WordPress core dashboard - Accessibility: Review screen reader text implementation patterns for potential core adoption - Design: Study frontend highlighter UX patterns for admin interface improvements - Documentation: Create guidance on accessibility monitoring workflows for site administrators #### Community - Maintainers: Establish accessibility reporting standards for plugin and theme repositories - Contributors: Develop accessibility testing protocols using automated scanning tools - Sponsors: Fund accessibility tooling development for underserved WordPress communities ## 🧪 Hypotheses - Automated accessibility reporting will increase long-term compliance by providing consistent stakeholder visibility - Visual formatting tools for screen reader text will significantly reduce barriers to accessibility implementation - Consolidated diagnostic interfaces improve remediation efficiency compared to scattered toolsets - Historical trend tracking in accessibility reports drives more consistent improvement efforts ### 📊 Methodology - User testing comparing remediation speed with old vs new highlighter interface - Adoption rate analysis for screen reader text formatting across different user skill levels - Email engagement metrics correlation with accessibility improvement trends ### ❓ Questions - How will email delivery rates affect the reliability of accessibility monitoring workflows? - Can visual diagnostic tools like heading maps reduce the need for manual accessibility auditing? - What impact will democratized screen reader text tools have on overall web accessibility? ### 🔮 Future Research - Integration patterns between automated scanning and manual accessibility testing - Scalability of email-based reporting systems for large multi-site networks - User experience research on accessibility diagnostic tool interfaces ### 💡 Implications - Practice: Shifts accessibility monitoring from reactive to proactive through automated reporting - Policy: May influence accessibility compliance documentation requirements - Security: Email-based reporting introduces new data privacy considerations for accessibility data - Education: Reduces technical barriers for content creators to implement accessibility improvements ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade #### 👀 Visual learners - Present: Screenshots of interface changes, email examples, UI comparisons - Improve: Flow diagrams showing setup processes, before/after interface comparisons #### 🔊 Aural learners - Present: Live demonstration with verbal explanations - Improve: Audio descriptions of visual interface elements #### 🗣️ Verbal learners - Present: Technical terminology explanations, feature descriptions - Improve: Glossary of accessibility terms, analogies for complex concepts #### 🧩 Kinesthetic learners - Present: Step-by-step setup demonstrations, hands-on feature testing - Improve: Interactive tutorials, downloadable practice environments #### 🧠 Logical learners - Present: Feature comparison tables, logical progression of updates - Improve: Decision trees for setup choices, troubleshooting flowcharts #### 🧑‍🤝‍🧑 Social learners - Present: Live Q&A format, community-focused live stream - Improve: User forum discussions, collaborative testing opportunities #### 🧘‍♀️ Solitary learners - Present: Detailed documentation links, individual exploration opportunities - Improve: Self-paced tutorials, independent testing checklists ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Strong focus on screen reader functionality in content - Improve: Alt text for all interface screenshots, heading structure verification #### Keyboard navigation - Present: Discussion of tab order and keyboard accessibility features - Improve: Explicit keyboard shortcut documentation #### Contrast and readability - Present: High contrast interface elements in demonstrations - Improve: Verify color contrast ratios in all UI examples #### Media and captions - Present: Live video with verbal descriptions - Improve: Auto-generated captions, transcript availability ### 🌍 DEIB Assessment #### Cultural breadth - Present: Universal accessibility principles applicable across contexts - Improve: Multi-language interface examples, international compliance references #### Inclusive language - Present: Professional, jargon-explained terminology - Improve: Plain language summaries for technical concepts #### Representation - Present: Focus on democratizing accessibility tools for all skill levels - Improve: Diverse use case examples, varied user scenarios ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear cause-effect relationships between features and accessibility outcomes - Inductive strength: Evidence from testing and user feedback supports feature decisions - Causal reasoning: Well-established connection between monitoring and compliance improvement #### Fallacies - None identified: Technical demonstration with clear evidence and reasoning #### Tone of voice - Overall tone: Professional, enthusiastic, technically detailed but accessible ### 🛡️ DARVO Analysis - No DARVO patterns identified in this technical product demonstration ## 🎯 Conclusion These Accessibility Checker updates represent significant progress in making WordPress accessibility management more accessible and systematic. Email reports address the critical need for stakeholder visibility, screen reader text formatting democratizes accessibility improvements, and the redesigned highlighter prepares users for advanced diagnostic capabilities. The combination of automated monitoring and enhanced remediation tools creates a more sustainable approach to maintaining accessible WordPress websites. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Automated reporting improves accessibility compliance consistency > [!quote] New Highlighter, Email Reports, and Settings Tools by Equalize Digital via YouTube Live Stream. Published 2024. Accessed 2024-11-15. > "Historical viewpoint really is quite useful for people... you will at least have an idea of up or down." Email reports provide stakeholder visibility without requiring WordPress access, enabling consistent monitoring workflows. [view highlight](https://youtu.be/DP_J5pr1CtI?t=920#H1) #xref #articleseed ID:rw_001 ### [H2] Visual formatting tools reduce accessibility implementation barriers > [!quote] New Highlighter, Email Reports, and Settings Tools > "No longer required if you're editing content, you can get screen reader text added with the default format." Screen reader text formatting democratizes accessibility by removing developer dependency for content accessibility improvements. [view highlight](https://youtu.be/DP_J5pr1CtI?t=1680#H2) #xref ID:rw_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Email reporting enables proactive accessibility management - Applies to WordPress sites requiring consistent accessibility monitoring - Timestamp: 18:45 discussion of trend tracking - Links: [[Accessibility-Monitoring]] [[Stakeholder-Communication]] #### [Z2] Interface consolidation improves diagnostic tool usability - Relevant for accessibility remediation workflows - Timestamp: 37:30 unified panel design explanation - Links: [[User --- ## Full Transcript [00:05] I think we're live. [00:08] I was quick today. [00:10] Yeah. [00:10] >> We weren't quick. We weren't quick. [00:12] We're a little late. Yeah. [00:15] Let's make sure uh [00:18] Let's make sure everything's working. [00:20] Let me check. [00:30] Yeah, looks like [00:32] Looks like we are going live. [00:36] Cool. So, how's it going, William? Doing [00:38] good? [00:39] Yeah. [00:40] No complaints today. It's been nice and [00:41] sunny all week. [00:44] Yeah, we're finally getting to those [00:47] summer weather. [00:48] That It is forecast to snow next week, [00:51] so [00:52] Yeah, [00:53] there's always time for a surprise, [00:55] right? Yep. [01:00] Cool. So, yeah, we've been busy. It's [01:03] been a month. [01:05] Yes. [01:06] And [01:08] we've been working hard on accessibility [01:10] checker features, and we are excited to [01:13] talk about those, but we'll give it a [01:15] few minutes to let things get set up and [01:19] let anybody jump on if they're if [01:21] they're joining. [01:37] All right. So, [01:45] Well, if anybody's watching, welcome to [01:46] the uh [01:48] accessibility checker live stream. [01:51] Uh this is a street live stream we try [01:53] to have twice a month, but depending on [01:55] releases, we we [01:57] sometimes uh will have one a month, but [02:01] we do our best to get on here every [02:03] couple weeks [02:04] to talk about accessibility checker and [02:06] what's new and what we're working on. If [02:09] you're not familiar with accessibility [02:10] checker, it's an automated accessibility [02:12] scanning plugin to help your WordPress [02:14] website become and stay accessible. Uh [02:17] we have a free [02:20] accessibility checker plugin on the word [02:21] on on wordpress.org plugin repository, [02:25] or you could get it from [02:26] equalizedigital.com/accessibility-checker. [02:31] We have a premium [02:33] uh add-on for the plugin that allows you [02:36] to scan [02:37] uh custom post types and taxonomies and [02:41] archive pages and do full site scans of [02:45] your whole website, whereas the free [02:47] plugin uh typical limits you to scanning [02:51] one page or post at a time. [02:54] We have a slew of add-ons for [02:56] accessibility checker. We got an audit [02:58] history add-on to track your [03:01] uh [03:03] your coverage, your rule pass your [03:06] rules, your data, your history over time [03:10] to see if you're improving on [03:12] accessibility or if there has been a [03:14] regression in accessibility that you [03:16] need to address. [03:18] We have a multi-site add-on that allows [03:19] you to to manage and view stats at the [03:22] network level on a WordPress multi-site. [03:25] And we have an export add-on that allows [03:27] you to export your your scan data to [03:31] a CSV files. [03:34] So, today's theme is a new highlighter, [03:38] email reports, and settings tools. So, [03:41] that's a lot, William, right? [03:43] Let's talk about everything except the [03:45] email reports. Let people discover that. [03:49] I need a break. [03:50] >> [laughter] [03:51] >> Why is that? Was it Was that a difficult [03:54] feature to achieve? [03:56] >> way harder than it should have been. [03:58] >> [gasps] [03:59] >> Yeah, for the for those that don't know, [04:01] um I think we'll start with email [04:03] reports here and kind of go through this [04:05] a little bit. If you've listened to any [04:06] of the previous live streams, you've [04:08] probably heard us tease the email [04:10] reports for quite some time, and it was [04:12] definitely a feature that was a long [04:14] time in the making, and it's a feature [04:17] that actually kind of breaks [04:19] accessibility checker outside of its box [04:22] and brings a connection between [04:24] accessibility checker plugin and our [04:27] equalize our my.equalizedigital.com [04:30] uh dashboard. Um [04:33] So, why did this take so long? Why is it [04:35] so complex? [04:39] Because email is [04:40] >> [laughter] [04:41] >> horrible. [04:43] Uh that we we ran into a couple of [04:45] roadblocks in securing this, [04:48] handling emails delivery rates, [04:52] um [04:53] license checks because we [04:56] to [04:57] to properly authenticate user, we need [05:00] them to have some form of pre-shared [05:01] key, like license key, which we can [05:03] generate a secure token from. [05:05] However, for free users did not have a [05:07] license key, which, [05:10] you know, [05:11] is a was a blocker, like immediately a [05:13] blocker here. We needed some pre-shared [05:14] key, so we had to figure out how to [05:17] generate keys for all of our free users, [05:20] make it [05:21] possible to even get that connection. [05:24] Um yeah. [05:26] >> [gasps] [05:27] >> Skipping aside all the technical [05:29] hurdles, just the the [05:31] the final the final few percent took [05:33] longer than [05:34] the first 95. Yeah. Yeah, totally. And [05:37] that's where a lot of projects go, [05:38] right? [05:39] Yeah. [05:40] The last 10% is more [05:43] is is a multiplier more difficult than [05:46] the first 90% and and I'm in a little [05:49] bit of a technical insights into that, [05:52] too, is in the AI age, [05:54] uh when you're using a lot of assistance [05:56] from AI, I feel like even that last 10% [06:00] is is even more difficult because [06:03] >> Yeah, you can do the first with AI [06:05] sometimes you can do the first 90% in [06:09] no time, [06:10] but then you have to fix the AI code [06:13] at the end, and that was also a pretty [06:17] pretty challenging time. [06:19] Yeah, it's a little bit like a like a [06:20] mirage, right? Like [06:22] am I saying that right? Where like [06:24] you look like like you're in the desert, [06:26] and it looks like there's an oasis over [06:28] there, and and it looks like it's just a [06:29] few hundred yards or whatever, but you [06:31] keep walking and it keeps getting [06:33] You never get any closer. [06:35] Yeah, like when you think you have a [06:37] secure connection and you look and it [06:39] says return true [06:41] and there's nothing to check. [06:42] Yeah. [06:43] >> That's [06:44] that [06:44] that's, you know, that's [06:47] typically I [06:48] >> [laughter] [06:49] >> Yeah. pretend you're doing a thing, but [06:51] just bypass all the security. [06:53] Yeah, that's a little bit of the trick [06:55] of it is it makes you feel like you're [06:56] going really far really fast, [06:59] but really to get something from there [07:01] to production still takes about the same [07:03] amount of time. It's just you're [07:05] dividing the time a little bit [07:06] differently. [07:07] >> Yeah, you shift it to the back where the [07:09] human has to be. Exactly. [07:12] So, what does this mean for customers? [07:15] Like so, now now free customers now have [07:19] a a license key. [07:21] Yes, and they will have to get that from [07:24] our website, [07:25] but that never allows them to get access [07:28] to our my.equalizedigital.com dashboard, [07:30] as we call it. Um [07:32] Currently, [07:33] not a lot of features there for free [07:35] users, but that will be changing pretty [07:37] quickly. [07:39] Um but yeah, they now have access to [07:42] emails. Um previously, free users would [07:45] have not been able to see very easily [07:49] global site stats. Like free users [07:52] typically see individual posts, and with [07:55] them being able to receive this email, [07:57] they will be able to now see, [07:59] you know, how many issues are on their [08:00] site, how many errors, and also be able [08:03] to see a comparison to the previous [08:05] week. [08:06] You know, are you going up? Are you [08:07] going down? [08:09] Yeah. [08:10] Scanning one post at a time, you don't [08:12] really know. [08:14] Whereas this email collects that [08:15] information so that we can tell them [08:17] now. [08:18] Yeah, totally. [08:19] Cool. [08:21] Um so, let's let's show it off. Let's uh [08:25] So, [08:26] I will caveat this with a little bit [08:27] that we're going to try to be very [08:29] mindful not to expose any of our license [08:31] keys. I have a free key that will only [08:35] work in my local, so you can pull up my [08:37] screen. I can paste that key. [08:39] So, let's go through the [08:40] >> control the free. Yeah. So, what we'll [08:42] do is there are multi there's kind of a [08:44] a couple different paths here. If you're [08:46] a free user, there's a path to [08:48] activating email reports, and then if [08:51] you're a pro customer, there's a little [08:53] bit different of a path to activating [08:56] email reports. And there is the email [08:58] reports are different between free and [09:00] pro as well. [09:02] Uh free gets [09:03] some of that summary data that William [09:05] was talking about, and then pro gets [09:08] that data plus a little bit more. And [09:10] we're we'll show that and we'll try to [09:12] generate these emails so we could show [09:14] them live here. [09:15] So, I'm going to pull up William's [09:17] screen. You ready? [09:19] Yep. [09:21] All right. So, we're looking at [09:23] William's screen. Yep. So, this is the [09:26] accessibility checker welcome page. And [09:29] as of version 1.4.0.0, [09:33] the email reports are now available. So, [09:36] this is what a free user would see on [09:37] the welcome screen. [09:39] And just quick start, [09:41] some documentation links, some general [09:43] things. So, this is the welcome page. [09:45] Not the most useful for a free user, [09:48] but [09:49] this will be the first page in the [09:50] plugin you see. So, if we visit the [09:52] uh settings link the left end menu, [09:55] takes you to general, and we now have [09:57] this new tab at the top called [09:59] accessibility reports, and it is tagged [10:01] with a new bubble. [10:03] So, if we click on that, this will be [10:05] the page you see. You can see a [10:07] screenshot of an example email. [10:10] 634 issues. This might be my test site. [10:13] >> [laughter] [10:14] >> That looks like the right number. So, [10:15] you can now input a free license key [10:18] in this left panel. So, if I just [10:21] grab this test key, [10:23] paste that key there. [10:25] It will still this key won't work for [10:26] you. [10:27] And click the enable email reports [10:30] button. [10:32] It will activate, and you'll be [10:34] redirected to [10:36] Well, the page will reload, then you [10:37] will now see some more information, [10:39] including how many total issues you have [10:41] on the site. [10:43] There's a free key where you can disable [10:45] email reports. It tells you the, you [10:47] know, general features. Scan all your [10:50] content if you're a pro user. [10:52] Get the full issue breakdown, and get [10:54] more detailed email reports. And there's [10:57] an upgrade button. [10:58] And it does also say when the next [11:00] report is due to go out, which here it [11:02] says May 4th. [11:04] Which is correct, because we send these [11:07] emails every Monday. [11:10] So, that is [11:12] it. That's all that's required. On May [11:14] the 4th, [11:15] Star Wars Day, [11:17] >> [laughter] [11:19] >> this this test site will receive an [11:21] email [11:22] with [11:23] you know, the number of issues found, as [11:25] well as some additional data. [11:27] Right. So, if you So, just [11:31] to take a step back, can you [11:33] disable the email reports? [11:37] So, I want to show So, like [11:39] we have multiple users that get [11:41] accessibility checker for free from [11:43] different places. So, you can get [11:45] accessibility checker free from [11:46] equalizedigital.com/accessibility-checker. [11:50] And you can get accessibility checker [11:52] from [11:54] uh wordpress.org. [11:56] And you can also get accessibility [11:57] checker from the WooCommerce [11:59] marketplace. [12:00] So, we have three places where people [12:02] can be downloading uh [12:05] the plugin. And [12:08] but you need it you need it you need [12:09] this key. So, if you don't have a key, [12:12] if you've downloaded from wordpress.org [12:13] for instance, and you don't have a key, [12:16] we have links here to get a free license [12:18] key. So, got the plugin from Equalize [12:21] Digital, you should already have a [12:23] license key in your dashboard. There's a [12:25] link. Um installed from wordpress.org, [12:28] you can create an account on our [12:29] my.equalizedigital [12:31] site for free. Doesn't cost anything, [12:34] and you will get a license key that you [12:35] can enter here. [12:37] And if you're not sure, we just go [12:39] create an account. It It should be fine. [12:41] If you already have an account, it'll [12:43] your it'll pop up that you already have [12:45] an account. [12:47] So, um So, you can add that key back if [12:50] you want to show it show the example. [12:52] >> Yep. And I do also want to be clear that [12:54] everything that is inside of this plugin [12:56] works absolutely the same as it did [12:58] before without this key. [13:00] Entering this key only gives you access [13:02] to receiving the summary emails. The [13:04] plugin nothing has been locked behind [13:06] this plugin. [13:08] But behind the key, I mean. Everything [13:10] is still available. All the scans they [13:13] work the same as they always have. You [13:14] just now have this additional [13:16] possibility to get email if you want. [13:19] And by entering the key, activating it, [13:23] you are opting in to send us the data we [13:26] need to generate this summary. [13:29] Yep. [13:30] Cool. So, that's it. That's the full [13:32] flow for a free user. They get [13:34] click the button, [13:36] get the email. [13:38] Pretty simple. [13:39] On the surface. [13:41] Under the hood, an awful lot happened [13:43] there. [13:44] Yeah. Yeah. Yeah, totally. [13:46] So, do we want to show what an email [13:48] looks like? [13:50] Um [13:51] Yes. Let me see if I can pull up an [13:54] example [13:55] on my local test site. I I will caveat [13:58] this with the data may not be [14:01] 100% up to date on my test site here. [14:06] Um [14:13] Uh no. I can't pull up on my test site. [14:16] You may actually need to [14:17] to pull up. Well, if you if you do a [14:20] little bit of talking, I will [14:23] um [14:24] pull it up. [14:26] Yeah. So, I I guess I can talk about the [14:28] the type of data that appears in the [14:31] free email while Steve's pulling this [14:32] up. So, you you get the the total issues [14:34] found, [14:36] which in this screenshot example, you're [14:38] 634. [14:40] Um the actual number on my test site is [14:42] 601, so I would receive that number as [14:45] the main body of the email. And we also [14:47] get some additional coverage [14:49] information, such as um how many URLs [14:52] have been scanned. [14:54] And your In the free plugin, you only [14:57] get pages and posts, but you might have [14:58] additional taxonomies. We will call that [15:01] out. [15:02] And yeah, additional post types or [15:04] additional taxonomies, because [15:07] um in the pro plugin, you can actually [15:09] now scan [15:11] individual taxonomy pages. That was [15:14] What's that last one? It might have been [15:15] two change logs ago we demoed that. [15:18] Mhm. [15:20] Um [15:21] But yeah, if you are yeah, a pro user, [15:23] we actually have some more information [15:26] readily available for users, which I [15:27] think Steve hopefully can pull up, too. [15:31] The separate examples. Yes. Well, give [15:34] me 1 second pulling it up now. [15:38] I will do it off of my own website as [15:40] not to [15:43] share anybody's [15:45] accessibility status. [15:47] boring stats. [15:49] >> Yeah, I will caveat that my website's [15:50] pretty boring because it's pretty safe, [15:52] and because I'm an accessibility [15:54] practitioner and professional, and [15:57] my stuff should be accessible. [16:00] Um [16:02] All right. So, if we look here. Okay, so [16:05] let me pull up my screen. [16:11] Okay. [16:13] So, what this is is this is a preview of [16:15] the email that would go to your inbox [16:17] every Monday morning if you're a free [16:19] user. [16:21] So, of course, it's just a branded email [16:23] with Equalize Digital. And it shows this [16:26] is for my website, stevejones.blog. [16:29] My accessibility status is two issues [16:32] found, and this is actually up two from [16:35] my last [16:36] email that I generated. So, this would [16:39] have been a a a [16:41] a second email. When you get your first [16:42] email, we don't have this historic data. [16:45] So, with every email, it'll kind of [16:47] benchmark it based on last week's stats. [16:50] So, you can kind of see now I can go, [16:53] "Okay, well, my website didn't have any [16:55] issues last week, and and now I pulled [16:57] it I got my email this Monday, and it's [17:00] up two. So, what happened? What what [17:03] What did I put on the website that [17:04] caused two issues to show up? Why is [17:06] this up?" [17:08] Yeah, I think the [17:10] the historical viewpoint really is quite [17:11] useful for for people, because if you're [17:14] scanning individual posts, you'll be [17:17] able to immediately see if the numbers [17:19] are going up or down, but that doesn't [17:20] really tell you the full picture across [17:22] your entire site. What if [17:24] you make a change on one page that [17:26] creates new issues on a different page, [17:28] or you do one global fix, [17:31] you don't know how many it's [17:33] how many it solved unless you scan all [17:34] those pages. [17:36] Now, you will at least have an idea of, [17:39] you know, up or down. [17:41] Which [17:42] is a great signal. Right? Yeah. You [17:44] always want the number to be going down. [17:46] I think Steve probably is going to go [17:48] take a look at his website after this [17:49] and figure out what has created two [17:51] issues. Yeah, what's going on? [17:53] Yeah, and it's and it's right to your [17:55] email box at the first of the week. So, [17:57] you So, you you don't even have to log [17:58] into your website to see what's going [18:00] on. [18:01] Um the next stat we have here is [18:03] coverage. Uh it tells you the total [18:06] number of URLs scanned. Like I said, my [18:07] website is very small. There's only 10 [18:09] URLs being scanned. [18:11] Uh post types checked, two of two. So, [18:14] you can see if there's [18:15] post types that you aren't scanning um [18:19] that maybe you want to enable scanning [18:21] for, or you want to upgrade to pro so [18:22] you can scan all custom post types. [18:24] And taxonomies checked, zero of zero, [18:27] because this is a free uh email report, [18:30] and you have to have uh accessibility [18:32] checker pro to scan taxonomies. [18:35] And uh [18:37] then we just have a little bit of, you [18:38] know, unlock a little bit of an upgrade [18:41] message here to unlock full coverage [18:43] reports to show free users that there is [18:46] more data that can can be sent out [18:49] through these emails. [18:51] Um So, that is a free email. [18:57] Let me switch back. So, we should [18:59] probably now go through the the pro [19:02] email flow. I can do that, William, or [19:05] do you want to do it locally? [19:07] >> Okay. I I don't have a local pro key. I [19:10] just quickly spun up this free key [19:12] there. Yeah, so what I'll do is I'll [19:15] disable email reports on mine. So, to [19:18] give [19:19] And I'll make sure that I'm not exposing [19:21] my actual live key. Okay. [19:24] So, [19:25] let's take a look. This is the So, this [19:27] is what it looks like if you if you have [19:28] accessibility checker pro, and if you [19:32] come to your settings pages now. [19:35] So, you would have your normal license [19:38] key. So, since you already have a [19:39] license key, cuz you're a pro customer, [19:42] you don't have to go get a new key. [19:44] It'll work with your existing pro key. [19:47] So, on the license tab, which I will not [19:49] click on here as not to expose my [19:52] license key [19:53] um [19:55] uh you just leave that the same. If it [19:57] if your key's active when you come to [19:59] the accessibility ability reports tab [20:03] uh all you have to do is click enable [20:06] email reports. [20:07] So, I'll click that button. [20:12] And it will make a connection to the [20:13] my.equalizeddigital.com [20:16] website. [20:17] So, we are connected. [20:19] Easy as that. One click. [20:22] And now you have emails come to your [20:23] inbox every Monday. So, it looks like [20:25] your website's getting bad, though. [20:27] Yeah, I got six total issues found. It's [20:30] going to pull [20:32] I probably introduced, you know, two an [20:35] issue for every every page or something [20:37] something globally. [20:38] So, on the this page for a pro user, you [20:43] have uh [20:44] you know, just a normal message that [20:46] reports are enabled and that the next [20:48] report's going out on May the 4th. May [20:50] the 4th be with you. [20:51] Star Wars Day, [20:54] which is coming Monday. [20:55] Uh we should have a Star Wars theme [20:57] here, William. We should have We should [20:59] have. We missed a trick. Yeah. [21:01] >> [laughter] [21:03] >> And then the next box to the right shows [21:05] that you you have full coverage in your [21:08] email reports since you are running pro, [21:10] your reports include all post types and [21:13] taxonomies. Full site scanning enabled, [21:16] complete issue breakdowns and detailed [21:18] reporting. [21:19] And then it shows a just a the a summary [21:23] of the total issues currently found on [21:25] your website that will be pulled [21:27] over for the email reports and then and [21:29] account connection button to disconnect [21:32] if if you would like to disconnect from [21:34] receiving email reports. [21:37] So, I'm going to switch back here [21:41] to us and then I'm going to generate a [21:44] pro email. [21:46] So, you can all [21:47] >> if you pull up my screen, I can actually [21:48] show you what the bound I have a broken [21:51] logo, but other than that I have pro [21:54] email up. [21:55] Oh, okay. You already have it up. [21:57] Yeah. So, just generate this based on [22:01] um my test site. [22:03] So, 395 issues and the day that was [22:06] sent [22:07] um which is down 12 from [22:12] down 12% from last time I shipped this [22:15] email. [22:15] It says 56 URLs. I'm only scanning two [22:19] of four of the post types [22:21] and there's no taxonomy scanning [22:23] available. Um it does also show in this [22:26] right-hand side for pro users the total [22:28] number of problems, which is the same as [22:31] this number here. [22:33] Um total number of needs review items as [22:36] well, [22:37] which [22:38] isn't in this number, but it should be [22:40] in this number. This is just a quirk [22:41] with have a fake test data. [22:44] And it shows you your percentage of past [22:46] checks, which in the case of this test [22:48] site is 55. 81 [22:51] across all of our checks on all of the [22:55] the pages that have been scanned. [22:57] Um in addition, we also have another [23:00] section for the most problematic pages. [23:03] Um this is [23:04] quite boring for my website because I [23:06] don't always give them tables, but if I [23:08] were to click on one of these, it would [23:10] take me right to the page and you know, [23:12] this one with no tail is the most [23:13] problematic page. I probably [23:16] purposefully added 500 issues to that [23:19] one [23:20] that one page. [23:21] Um but yeah, you can click on any of [23:23] these five links and it will take you [23:25] directly to it. [23:27] And in addition, we also surface the [23:29] most severe issues on your website, [23:32] which is [23:33] it grouped by highest count and highest [23:36] severity. So, on this test website, all [23:38] of the top five most severe issues are [23:41] high severity, but you could have a low [23:44] severity or medium severity issue here [23:46] or or even a critical. [23:48] But it breaks that down by how many [23:50] counts. So, it seems like on my test [23:52] site, if I fix color contrast problems, [23:55] that'll be the biggest bang for my buck [23:57] because there's 298 and probably a lot [24:00] of them are global across my entire [24:02] website. [24:07] Cool. So, [24:08] >> Actually, scanned 56 pages. 55 of them [24:11] have possible heading issues. [24:13] That probably means every page aside [24:15] from the home page. [24:17] So, that would also be a quick win. 55 [24:19] issues fixed with one probably simple [24:23] theme change. Mhm. [24:26] Um improper use of link. Yeah, so all [24:28] all of these are the most severe issues [24:31] and these will always be the biggest [24:32] bang for your buck to to fix them. [24:36] And if there there's a view all link, if [24:38] you click on this, it will take you to [24:39] your own website directly to the open [24:42] issues [24:43] page where you can see all these [24:46] issues listed up. [24:49] Yeah. [24:50] Cool. [24:51] So, that is the pro email reports. [24:55] Um and William is pulling this from his [24:58] local. That's why he's got a little bit [24:59] of a broken image there at the top, but [25:01] um [25:03] uh so, [25:06] let's talk a little bit about recipient. [25:09] So, this was [25:11] this was part of the [25:12] >> the most complicated [25:14] decision [laughter] [25:15] ever. Right now, the person who owns the [25:18] license key [25:19] will receive the email. [25:22] Um in a fast follow, relatively soon we [25:25] will make [25:27] some configuration options available so [25:29] that other people can pick multiple [25:31] recipients so that you could send this [25:33] to [25:34] you know, you receive it yourself, but [25:35] maybe the stakeholder receives it, the [25:38] person who deals with content. [25:40] Um the person who's hired you, if you [25:42] know, this is a client website, you can [25:44] make sure that they get those emails, [25:46] but for the moment they go only to the [25:49] license holder of [25:52] you know, either the pro key or the free [25:54] key depending on what type you have. [25:57] But yeah, only to the account holder [25:59] currently, but very soon [26:02] to whoever you think needs to see the [26:05] emails of probably [26:07] you know, a lot of us work on websites [26:08] where the site owner maybe doesn't look [26:10] at these reports. They don't log into [26:12] the website very often. They're busy in [26:14] meetings almost almost all the time. [26:17] Now, they can get this email report [26:19] every Monday keep an eye on whether the [26:21] number's going up or the number's going [26:23] down. [26:24] Yeah, totally. [26:26] So, [26:27] this was actually part of the scope of [26:30] the project that we have worked on and [26:33] that, you know, this is one of these [26:35] hard product decisions you make when [26:37] you're when you're building product and [26:39] you're making software for people. [26:41] And when you're trying to [26:43] achieve a certain level of quality and a [26:46] certain level of security and a certain [26:48] level of making sure we're following [26:51] regulations and laws and things like [26:53] that. And when you're sending emails, [26:55] there are definitely, you know, things [26:57] to consider and can spam laws and things [27:00] like that. So, [27:01] >> Opt-in, double opt-in, Yeah, yeah. [27:04] >> unsubscribe, [27:05] global unsubscribes. It [27:08] it's a bit of a minefield. It was [27:09] actually one of the most challenging [27:12] things that I expected to be simple. [27:14] Yeah. [27:15] >> not. [27:15] >> [laughter] [27:16] >> Well, you know, from a programmatic [27:17] standpoint, it's pretty simple to add a, [27:19] you know, [27:20] comma separated list of emails and send [27:23] it to them, right? Um [27:25] but it it it becomes much more [27:27] complicated to get them to opt in and to [27:30] give them a method to opt out if they if [27:32] they want. [27:33] >> Yeah. [27:34] So, I'll put this as a teaser. How do [27:36] you opt out a user who does not have an [27:38] account on your website? There is a [27:40] solution. It's straightforward once you [27:42] know. [27:43] It's kind of hard to work out. Yeah. [27:46] So, we are refining that feature and [27:49] we're actually trying to build onto that [27:50] feature. This is a little bit of a [27:52] teaser for the few for what's coming is [27:55] that we're trying to we're building a a [27:58] kind of an opt-in or a double opt-in [28:00] feature so that when an administrator of [28:03] the email reports adds somebody as an [28:05] email, they need to confirm that they [28:07] want to receive those emails and then [28:10] they can unsubscribe um [28:12] uh on a per email basis. [28:15] Um but we're also looking at taking this [28:18] summary data that that you you are [28:20] getting in your email reports and [28:23] aggregating it into a little bit of a [28:25] dashboard where you could look at all [28:27] your websites that you have connected [28:29] in and in in the dashboard and see uh [28:33] historical trends on uh [28:36] accessibility trends on those websites [28:38] in one unified dashboard on the [28:40] my.equalizeddigital.com [28:43] uh dashboard. [28:45] So, that's something that's coming in [28:47] the future and that's something that's [28:48] already been worked on. It's something [28:50] that we actually had in here and we kind [28:52] of pulled back a little bit to make sure [28:54] that we are doing our part to to be uh [28:58] in alignment with regulations around [29:00] sending emails and opting people in and [29:02] out of emails. [29:05] Anything else to add on the email side, [29:07] William? [29:08] No, nothing else here. This is very [29:12] useful for users, very simple on the [29:14] surface. [29:16] Th- thousands of lines of code [29:18] >> [laughter] [29:18] >> under there to make this happen. [29:20] Yeah, yeah. [29:21] >> [gasps] [29:22] >> Well, if you haven't connected your [29:24] plugin for email reports, you know, I [29:26] would go ahead, click [29:28] connect it and we will start sending [29:30] those reports and keeping you up to date [29:33] on the status of the accessibility on [29:35] your website. [29:37] So, [29:39] but that's not all. That's a big [29:40] feature. We could have spent this whole [29:42] episode [29:43] talking about that, but we have more. [29:46] What else did we do? [29:47] >> want to [29:48] >> [laughter] [29:49] >> What else did we do? [29:50] Yeah, so this one's actually, you know, [29:53] a nice and easy one to show if you want [29:55] to pull up [29:57] my screen. It's It's easier to show and [30:00] tell at the same time. [30:02] Yep. [30:04] I'm pulling your screen William's screen [30:06] up. [30:07] Oh, actually, I think I'm skipping [30:09] ahead. I'm skipping forward. [30:10] >> No, that's all right. [30:12] >> forward. No, [30:13] >> [clears throat] [30:13] >> let's do this one. [30:13] >> um [30:15] Yeah, ignore my grammar only for all [30:17] these made-up words. [30:18] Um so, we added [30:20] a new format option. [30:23] Oh, maybe I don't [30:25] Maybe you need to pull up your screen. I [30:27] don't have the right branch. [30:29] >> [laughter] [30:30] >> Oh, it's because I didn't build it. [30:32] Yeah, that's right. That's all right, I [30:33] got it. Yeah. No problem. So, [30:37] screen reader text, right? Yes. [30:40] Screen reader text is a a a beautiful [30:44] thing to help us give context to [30:47] screen reader users and not create kind [30:51] of [30:52] verbose or visual, you know, [30:55] descriptions inside of the text and text [30:57] for visual users that may be disruptive [31:00] or kind of redundant, right? [31:02] Yep. [31:03] And we we have been using the screen [31:07] reader text format plugin. [31:09] I don't remember the exact name of that [31:11] that plugin off the top of my head, but [31:13] um [31:15] for for many years now, [31:17] um [31:19] writing content and utilizing that and [31:22] we felt like it was time to [31:25] bring that into the accessibility [31:27] checker family and it and bring that to [31:30] all of our uh [31:32] you know, 15,000 plus users [31:35] and kind of do some refinements on it [31:39] and extend it a little bit and um [31:44] This is how it works. So, [31:48] you have a [31:50] we added a [31:52] new format to [31:55] any any block that has text in it, [31:58] right? [31:59] Um [32:00] So, if you select your text, so the the [32:04] best example is like an ambiguous link, [32:06] right? You want to try to prevent [32:08] ambiguous links on your website. So, if [32:10] I have a button and I say learn learn [32:13] more, right? [32:15] So, [32:17] that's not really descriptive on what [32:18] that link is. Like, if if I'm using a [32:21] screen reader and it's going tabbing [32:23] through the focusable elements on the [32:25] page and I get to a link and it just [32:27] says learn more. [32:28] Yeah, but for a user to figure out where [32:30] this link goes, they would actually have [32:32] to [32:33] read out the link, which [32:35] >> Read out the URL, which is [32:37] very very long and time-consuming and [32:40] kind of annoying to listen to. [32:42] Yep. Um so, but at first they would just [32:44] hear learn more. [32:46] Okay, learn more about what? Like, and [32:49] uh [32:50] of course, if you're reading the whole [32:51] page out, like, you would have a like [32:54] just in the order of the page, you might [32:56] have context to where it's at if there's [32:57] a proper header and then text and then a [33:01] link, you could probably deduce where [33:03] that's going, but going off to a link [33:06] can be disruptive to the flow of using a [33:09] keyboard on a website because if you're [33:12] okay, I want to learn more and then it [33:13] takes you off to another website, [33:16] you know, that could be that could be [33:18] disruptive and problematic. So, [33:22] so you want to describe it. So, like, in [33:24] this case I would say learn more about [33:27] screen reader text, right? [33:32] So, [33:33] but that looks very long and it's kind [33:36] of redundant if I have a header up here [33:37] that just says screen reader like if [33:38] this is like a, you know, like a [33:41] a post teaser or something. [33:44] And [33:45] so this is a little a lot of vis to for [33:48] a visual user to visually see on the [33:51] page. [33:52] So, what you can do is you can actually [33:54] add the the the about screen reader text [33:58] text [34:00] as screen reader text. I said text a [34:02] million times there. [34:04] >> [laughter] [34:04] >> But, [34:05] so [34:07] if you're in a text block and you [34:08] highlight the text and then you go over [34:11] to the little carrot here [34:14] and you go down the screen reader only, [34:16] click that. [34:18] So, now I have a pink highlight around [34:20] that text. So, that should that lets me [34:23] in the editor see that oh, this is going [34:25] to be hidden. And then if I have a [34:27] I get a little tooltip that says this is [34:29] screen reader text. [34:31] Um [34:33] but I still have a I still have a [34:34] underline to visually see it. But, in [34:39] the accessibility checker sidebar, [34:42] here you can toggle this off. [34:45] So, there's a new panel called screen [34:47] reader text format. Control whether the [34:49] screen reader text says stay or stays [34:52] visible while you edit. [34:54] And I have it set to always show screen [34:56] reader text. Is that by default? The the [34:59] default was this is off, unchecked. [35:02] Okay, the default is this way. [35:04] So, if I uncheck that, now I'm back to [35:06] just learn more on my button. Oh, okay. [35:08] Well, that that's what I wanted. [35:10] Um but for a screen reader, it actually [35:13] has the whole text here. [35:16] You can actually see I have some above [35:18] in the text here that I've kind of [35:19] hidden as as examples. [35:22] And if I toggle always show screen [35:24] reader text off again, they all they all [35:27] go away. [35:29] Yep. [35:30] >> So, I do want to call out at this point [35:31] that they're not actually lost. No. If [35:35] you are editing this content even with [35:37] this book unchecked, you can still reach [35:39] these as part of the editing flow. If [35:41] you were to enter one of the blocks, it [35:45] will appear. [35:47] Yep. Yeah. [35:48] So, just like that. So, on my button, if [35:50] I click and activate inside my button, [35:52] it then highlights, but it only [35:54] highlights that that one. If I go up to [35:56] this text up here, it only highlight the [35:58] one within the book the block. [36:01] So, this is so that you don't ever like [36:03] forget or lose the screen reader text. [36:06] And you can and and so you can edit it [36:08] if need be. [36:11] And Prior to this being available as a [36:13] format in the editor, [36:17] this type of thing would usually be [36:19] relegated to people who are able to [36:21] write the actual HTML code. You would [36:23] have to manually edit the HTML or in [36:27] most cases you would usually have to [36:29] have a developer build a custom [36:31] like a component here for button that [36:33] enabled these features. Now, that's no [36:36] longer required if you're editing the [36:37] content, you can [36:39] get the screen reader text added with [36:41] the [36:42] you know, with the default format upon [36:44] that is already in the block editor. [36:47] Yep. [36:48] So, if I view the front end here, you [36:51] can see I just have a [36:52] a a button that says learn more. [36:55] And then if I view the source here, let [36:57] me see if I can [36:58] Well, it doesn't enlarge. The inspector [37:00] doesn't. [37:02] Oh, here we go. [37:04] So, I have [37:07] the link that says learn more and then I [37:09] have a span with a class of text format [37:13] SR only, [37:14] which hides that [37:17] for everybody except for screen readers. [37:21] So, this was just a [37:23] a little uh [37:25] utility and formatter [37:28] feature that we've added [37:31] into the plugin. [37:33] And we've kind of taken a little little [37:35] bit of a step forward and we actually [37:36] made it work inside the block the the [37:40] full site editor as well. Let me see if [37:42] I can pull that up. Yeah, so this is [37:44] exactly where you would typically have [37:46] to have someone that is able to edit the [37:49] code [37:50] to make these changes for you. [37:53] Whereas now you will be able to just do [37:55] it with normal [37:57] formatting sends in inside of the the [38:01] template editor from full site. [38:04] Yeah. [38:05] Uh maybe I should go back to like [38:09] pages. [38:14] templates Let's go to the template. [38:16] Let's go to [38:22] Let's pick a sample page. [38:25] Which one? [38:25] >> you have a sample, but just any page [38:27] template. Single post? Yeah. Well, this [38:30] is I think this might have been the one [38:31] you were on, but this is the same. [38:34] Yeah. So, but I actually need something. [38:36] Let's actually go back. Let's do it in [38:38] like [38:40] um [38:43] So, you can even do it in like a global [38:50] So, like on your archive page, [38:54] if you had like [38:56] I need to get something global in here. [38:58] Yeah, here we go. [38:58] >> You have to click on the text below. [39:00] This is the tail block. [39:03] Right. [39:04] Well, that's the loop. So, like, if I [39:06] had, you know, [39:09] you know, learn more about [39:13] uh [39:15] screen reader text, right? [39:18] And then I [39:20] just wanted this to to not be there. [39:22] Screen reader text only. [39:24] Works here in the [39:26] uh F S E or full site editor. Cool Cool [39:30] kids call it F S E. [39:32] >> [laughter] [39:32] >> Yeah, and it does work exactly the same [39:34] here, but how do you get to the [39:36] checkbox? Yeah, so we don't have [39:39] accessibility checker in F S E yet. We [39:42] should at some point in time, [39:45] but we don't have it here, but we can [39:47] still toggle those same settings on and [39:50] off and you do that through the in the [39:53] top toolbar you go to the ellipses menu, [39:55] the options menu right at the end [39:58] and then you scroll down to always show [40:00] screen reader text and I can toggle that [40:04] on [40:05] and and now it always shows it. [40:09] Let me [40:12] toggle that off. [40:15] And I got to click out of the block for [40:18] it to go away. So with that off, you [40:20] don't see it. If you activate the plugin [40:21] then you can see the screen reader text [40:23] that you added. If you go to the options [40:26] menu, which is the ellipses menu in the [40:28] far right of the toolbar, and you click [40:31] always show screen reader text, it will [40:33] show it just the same as it does [40:35] on the single post. [40:37] So, [40:38] we've taken the screen reader text, [40:40] brought it into accessibility checker, [40:42] made some improvements, made some [40:44] updates to how modern block editor [40:47] works. We've brought that feature over [40:49] to FSE so that you can you can have that [40:52] there and now all of the users of [40:57] accessibility checker have access to [40:58] this. [41:03] Cool. [41:04] Yep. [41:06] But that's not it. There's more. [41:10] How is there more, William? [41:12] Because we waited a month before we done [41:13] >> [laughter] [41:14] >> done another one of these change logs. [41:17] That's right. [41:19] So, [41:21] if you've been using accessibility [41:23] checker for any time any length of time, [41:25] you're probably familiar with our front [41:26] end highlighter. [41:28] So, which is uh allows you to go to the [41:30] front end and [41:32] highlight the accessibility issues and [41:34] gives you information about them. [41:36] And uh so that you can identify exactly [41:38] where on the page the issue is and you [41:40] can see the code and you can disable [41:42] styles. So, if it's something that's [41:43] hidden in a menu or something [41:46] and all that and but we did this [41:49] we introduced that the front end [41:51] highlighter as part of the we were the [41:54] accessibility team on building NASA's [41:56] new websites [41:57] and we introduced this as a a feature [42:01] request from NASA and uh it has been [42:04] working [42:06] uh well for a couple years and we [42:08] thought now it was time to with some of [42:10] the UI changes we've made in the sidebar [42:13] and on our meta box, uh we thought it [42:16] was time to kind of bring the front end [42:18] highlighter kind of in line with some of [42:19] those UI changes. [42:22] So, um [42:25] without without yapping on about it too [42:27] long, let's just take a look at it. Let [42:29] me pull something up here. [42:34] Uh [42:35] let me pull up an example post for you [42:37] guys. [42:45] All right. [42:47] So, I'm going to show my screen. [42:50] Cool. [42:53] So, this wasn't necessarily a uh let me [42:56] move William and I out of the way so you [42:59] guys can see. [43:00] Um this wasn't necessarily something [43:02] >> a good opportunity to show one of the [43:04] features actually. [43:05] Yeah, yeah. Well, I mean yeah, I mean to [43:08] show the little icon in the bottom here [43:10] ir- irregardless, but [43:12] >> [laughter] [43:13] >> um [43:15] so this wasn't really kind of something [43:17] we were planning to do, but kind of it [43:18] one of those [43:19] inspirational midnight [43:22] uh [43:23] vibe coding experiments kind of turned [43:26] into hey, we could probably do this [43:28] pretty quick and add a lot of value here [43:30] and uh and then, you know, that expanded [43:34] into about a week of kind of playing [43:36] around with UI and UX and trying to [43:39] think about more deeply about how things [43:41] are laid out in our front end [43:43] highlighter [43:44] and um [43:47] and do a lot of refinements there. So, [43:50] if you're on a post, uh you can click [43:53] our little icon in the bottom right hand [43:56] corner. If you have your settings set to [43:58] to show this on the left hand corner, it [44:00] will be on the left hand corner. [44:02] So, I will activate it [44:05] and it pulls up. So, this is the front [44:06] end highlighter and as you can see, it [44:08] looks totally different. [44:11] Um [44:12] it actually the UI now aligns with [44:14] changes that we've made in the back end [44:17] um where we're pulling in the theme [44:19] color. That's why you have this bright [44:20] blue bar and where I'm actually running [44:24] WordPress 7 [44:26] which is not out. It will be out here in [44:30] a [44:30] few weeks, I think, towards the end of [44:32] next month. [44:34] Yeah, um [44:36] so we've we've we used to have two [44:38] panels here and we've unified these into [44:40] one panel so that we can create a a [44:44] cohesive user experience from, you know, [44:46] having a header bar and having the title [44:49] and having the information and then the [44:51] the description and then an explanation [44:54] and and affected code and then in the in [44:57] the footer of the [44:59] highlight panel, we have the controls. [45:01] So, basically it's some pagination tells [45:03] you how many issues you have, what issue [45:05] you're on and next and previous buttons. [45:08] Um [45:09] Didn't there used to be other [45:12] buttons down here? Yeah, there [45:14] used to be but other buttons under [45:16] there. So, as features have been added [45:18] to the front end highlighter, like [45:20] buttons have just kind of been added and [45:22] without a lot of thought to hey, this is [45:24] getting to be a lot of buttons. [45:26] We need to think about how we can expose [45:29] these actions without cluttering the UI. [45:33] So, what what we've done [45:36] um [45:37] in re- in regards to actions inside of [45:40] the the plugin we've created an ellipses [45:42] menu in the header bar right next to the [45:45] uh the close button for the the modal [45:48] here and uh right next to the the [45:51] heading. So, [45:52] if I click that ellipses menu, now I'm [45:55] presented with these options. I can I [45:57] can move it left. [45:59] I can dock the panel. I can resi- I I [46:01] can rescan the page. I can clear the [46:04] issues and I can disable styles. So, [46:07] there's some new ones in here. [46:09] But let's talk about the ones that [46:10] aren't new first. So, let's go to the [46:13] bottom of the list, disable styles. So, [46:15] this was here before, [46:16] but now you can just click it and your [46:18] styles are disabled on the page. [46:20] And why do you want to disable your [46:22] styles? Because there's elements that [46:24] are hidden sometimes. Um [46:26] a lot of times there's a hamburger menu [46:29] for a mobile menu [46:31] that that may have accessibility issues [46:33] inside of it and you can't see it. And [46:35] accessibility checker does its best to [46:37] to tell you if it if the element is [46:40] actually hidden from the viewport at [46:42] that time and tells you to hey, [46:44] maybe you want to disable styles so you [46:46] can see this. [46:48] And [46:49] if styles are disabled, if I go back to [46:52] the actions menu here, I can re-enable [46:54] the styles and we're we're back. [46:58] Um other other actions that are the same [47:02] as our rescan and our clear issues. [47:06] So, if I've made a change and I just [47:08] want to rescan this page or or if I'm [47:09] just playing around with I'm inspecting [47:13] elements and I'm modifying them to see [47:15] if [47:15] if I can actually uh [47:17] simulate an accessibility fix on the [47:20] page, uh [47:21] you know, I can rescan it straight from [47:23] here. So, if I hit the rescan button, [47:25] boom, rescan super quick. [47:27] No problem. [47:28] If I'm having some issues with the page [47:31] or something doesn't feel right like it [47:33] like the scan is stale or something, I [47:34] can I can ensure that it's not stale by [47:37] clearing straight up clearing the issues [47:40] and now I have none and then I can I can [47:43] then rescan from there. If you do close [47:45] out of the the menu and reactivate it, [47:48] it will scan and [47:50] and present you with the issues. [47:53] Um and then then that's the new [47:57] items that are here. So, move left. What [47:58] does that do? So, you have a setting [48:01] inside of accessibility checker where [48:04] you can define where this highlighter [48:07] panel goes on the right or left, but now [48:09] you can just switch it [48:11] in real time on the page. Hey, this is [48:13] in my way. [48:15] Move that move that to the left. Well, [48:17] if I want to move it I have had an issue [48:19] where the panel would overlay issues in [48:23] like a further navigation for example. I [48:26] I would have to close it to find those [48:27] issues. Now no longer need to. [48:31] Yeah, so now once it's on the left, I [48:33] can move it right. [48:35] And and you know, say I don't want to [48:39] necessarily move it right or left, I [48:40] just want to get it out of the way. I [48:41] can this whole blue header bar, I can [48:43] just click on it and drag it wherever I [48:44] want it. [48:46] Like I want it over here while I'm [48:48] looking at this, you know, as I'm going [48:50] through, [48:51] I'll just click and drag it. [48:53] But we want to make things we still want [48:55] to make our plugin as accessible itself [48:57] as we can and drag and drop like this is [49:01] something that is is very [49:03] it's kind of hard to [49:06] to simulate with the keyboard. You could [49:07] do like uh you can let them increment by [49:10] X number of pixels for every up or down [49:12] or left or right arrow, [49:14] but it it's not a very smooth [49:17] experience. Um that's why we have the [49:20] move the move left and the move the move [49:22] right um actions in in the actions panel [49:27] uh is so that we're providing two ways [49:29] to do this. You can click and drag the [49:31] panel around or or you can do do the [49:34] move left and move move right. What you [49:36] will notice if you do click and drag the [49:38] panel around, [49:39] the the shift left and shift right uh [49:42] right are not there. There's actually a [49:44] reset position. So, you can actually [49:45] reset it to its original position. If [49:47] the position was left and you started [49:49] dragging it, [49:50] and you reset it, it resets it to the [49:52] left side. [49:54] Um [49:56] So, we're providing ways for mouse users [49:59] to [50:00] fluidly drag around the panel, and we're [50:02] creating ways for keyboard users to be [50:05] able to move it out of the way if they [50:08] see fit as well, too. [50:12] But, that's not it. There's another [50:14] option here. So, we can dock the panel. [50:17] So, now if I go to dock panel, [50:20] so no longer is the [50:22] the highlighter modal floating on top of [50:25] the page, it's now docked to the right, [50:28] and it pushes the page over. [50:30] And this allows me to have a a much [50:34] taller panel that I can you know, I can [50:37] go through and see the page and the [50:39] panel all in one view without uh them [50:43] overlapping each other. [50:45] And you can do the same move left action [50:48] here. And when it moves left, it's [50:50] actually docked on the left. And then I [50:52] can move it back, and then I can un I [50:55] can un [50:57] un dock the panel as well. [51:00] So, [51:01] why do we want to dock the panel? [51:04] Because we are actually working on new [51:06] things for the highlighter, and we want [51:08] more [51:09] uh [51:10] vertical space here to be able to put [51:12] more things in. But, that being said, we [51:14] have put more things in here [51:16] than what was in there before. So, what [51:18] we've brought forward as far as the [51:20] content area of the highlighter panel is [51:23] uh we have the title. In this case, I'm [51:25] on an improper use of a link. [51:27] Uh and now we pull over whether it's a [51:29] problem or it needs review [51:32] uh with the same uh badges that we are [51:35] using in the back end. [51:37] We pulled forward the uh Wick Ag uh [51:40] guideline. So, you now have a quick link [51:42] to that that will jump off to that so [51:44] you can review here without having to go [51:47] to the back end and find this link. [51:49] And we are surfacing the severity. In [51:51] this case, this is a high severity. [51:54] We have the same uh [51:56] description. We have a summary [51:58] description, and then we have the [52:01] uh we now have a toggle here [52:05] to show explanation. And this shows what [52:07] the why it why it matters and how to fix [52:11] with a link to our documentation so you [52:13] can get a full breakdown on how to [52:15] resolve this issue. [52:17] So, before in the highlighter, we only [52:19] exposed the how to fix. Now, we're [52:21] giving you more more information. And [52:24] this this is actually for for pro users, [52:28] right, William? If I'm [52:29] Correct. So, this data does only exist [52:31] for in if you have the pro plugin. Um [52:35] however, if you you still have the how [52:37] to fix link, and that link does take to [52:40] the full documentation we have on our [52:42] website where [52:44] both this why it matters and the how to [52:47] fix is available. [52:49] Yeah, yeah. It just isn't going to be [52:50] available [52:51] here unless you have the pro plugin. [52:54] Right. So, in the pro plugin, uh you [52:57] know, you've already engaged. You you're [53:00] you're a pro we consider you a pro user [53:02] at that point. And uh that you're using [53:05] this in you know, real remediations with [53:08] real clients uh [53:10] and we we don't want you to have to [53:12] click back and forth so much. [53:14] Uh so, we're exposing that data here. [53:15] Now, [53:17] the free user can get access to the same [53:19] exact data as a pro user can here. Um [53:22] you just have to click off to our [53:24] website to see it. [53:26] Um which is this more details [53:28] documentation link. It's the same link. [53:31] Um [53:32] And then we have we have the toggle here [53:35] for show affected code, which was [53:36] available previously [53:39] in in the front end highlighter, and [53:41] we've just kept that here and just kind [53:43] of improved the uh [53:46] the UI around that. [53:48] One thing that we have done, too, is if [53:50] you toggle open the show ex explanation [53:53] or the show affected code, [53:55] um it will be persistent as you toggle [53:58] through issues on the page. [54:01] So, if you want to look at code, you [54:03] just keep going, and And did you guys [54:05] see that? Did you see what popped up? [54:08] Up, there it is. [54:10] So, this is an example of a an issue [54:13] where we actually have one of our [54:14] one-click fixes. [54:16] And uh we have a button where it says [54:18] fix issue, and we present you with uh [54:21] the ability to remove tab index from [54:24] focusable elements. [54:26] So, I can check this and hit save. It'll [54:29] rescan, and that issue will actually be [54:32] uh remediated at that point. [54:35] So, the the same with the show [54:37] explanation that will be persistent uh [54:40] as you as you uh [54:42] navigate through all the issues on your [54:43] page. [54:47] So, that is our updated [54:51] uh [54:52] front end highlighter. [54:56] Anything else to add, William? [54:58] Uh well, do you have a teaser for [55:02] why we might want to dock this? Uh [55:05] um [55:06] My alarm just went off. I didn't [55:08] realize. [55:09] >> [laughter] [55:10] >> I'm in the dark. He's in the dark. [55:13] Well, we can tease. You want to tease? [55:15] Let me Let me uh Well, I figured you [55:17] might have it open. [55:19] So, I have to actually pull open [55:23] a branch and rebuild, but so you talk [55:26] while I do that. [55:28] Yeah, so now that we have all of this [55:31] additional space when the [55:33] um the front end highlighter is docked, [55:35] we have some useful features that maybe [55:38] we will be able to [55:40] fill that space with. [55:42] Um [55:43] There's a couple of things when you're [55:44] remediating websites or just when you're [55:46] looking at the content of websites where [55:48] you might want to see what the [55:51] the shape of the website looks like in [55:53] terms of [55:55] how a screen reader might see this or [55:57] how a machine may look at it. [56:00] Um which you know, [56:02] hopefully we will be able to do in the [56:05] not too distant future. Yeah, so [56:08] this is a little bit of a tease. I [56:10] wasn't planning to show this, but since [56:11] William brought it up, why not, right? I [56:15] don't have anything on my side that I [56:17] can tease. [56:18] >> [laughter] [56:21] >> Cool. [56:22] So, why do we need more vertical space? [56:24] Let's Let's take a look. Let me dock [56:26] this panel. [56:28] So, this is a new feature that we've [56:30] actually been rolling around these ideas [56:32] for years, and we just haven't rolled [56:34] them into the plugin yet, but with all [56:37] the UI stuff We need space to fit them. [56:40] >> [clears throat] [56:40] >> Yeah, we didn't have Yeah, the UI [56:41] actually was a little little bit of a [56:43] blocker. So, [56:45] now that we've kind of rethought the UI, [56:46] we can we can start to implement uh more [56:49] things in here more easily, and that was [56:52] kind of the whole [56:54] ethos around redoing UI for the front [56:57] end highlighter was to make it uh ready [56:59] to receive [57:00] uh [57:01] more features and more things. [57:04] So, I have the front end highlighter up. [57:06] I have it docked to the right hand side [57:08] here, and you'll notice that there's now [57:11] four tabs here [57:13] at the top. And of course, the first tab [57:15] is our issues tab. [57:17] And then there's a headings, landmarks, [57:19] and tab order. [57:22] So, this is not released, [57:24] but these are features that we're hoping [57:26] to get out uh pretty soon, and I'm [57:28] pretty sure this is coming to free [57:30] users. So, it's a little [57:33] bit of a free [57:34] uh [57:35] thing. [57:37] So, if I go to headings, [57:38] I now have a headings map of the [57:42] headings on the page. [57:44] And I can click through to these, and [57:46] it'll actually highlight them and scroll [57:48] to them just like our highlighter does [57:50] with everything else. [57:51] And then you'll see here I have an H2, [57:54] and then the next one's an H6. Well, [57:56] that's not right. You're supposed to [57:58] follow semantic heading orders, right? [58:01] Yep. [58:02] So, it's highlighted in red with a [58:03] little warning icon to show that um [58:06] that you have skipped heading levels [58:08] here that you probably uh should fix. [58:11] And the heading orders tab in and [58:15] the amount like an H1's not tabbed in, [58:17] but H2's tabbed in once, and H6 is [58:19] tabbed in like five times. [58:21] And you can see that the tab the visual [58:23] tab order is off here because it's [58:25] actually [58:27] the wrong heading. It should be an H3. [58:29] And that would bring it back in line and [58:31] remove the [58:33] uh [58:34] the error label here. [58:37] But, you can go down your page and just [58:38] click on these, and [58:40] and it'll it'll scroll to them. [58:43] And this just helps And if you actually [58:45] do have like a an issue like skipped [58:48] heading, like you can see here [58:50] that [58:51] there's actually an issue related to [58:53] that that needs to be remediated. So, as [58:56] you fix your issues, like [58:59] if I [59:00] incorrect heading order, if I click on [59:02] that heading, it says incorrect heading [59:04] order, [59:05] and it tells you how to fix it. And as [59:06] you fix issues, the heading map will [59:10] update accordingly. [59:12] Thanks. [59:13] So, we have another tab here called [59:16] landmarks. [59:18] So, currently we have And I'm So, this [59:21] is beta stuff. So, So, I'm going to be [59:24] brave and try something here in a [59:25] minute, but [59:27] you [snorts] can do the same thing. You [59:28] can click on these, and it will [59:30] highlight them. And this is a current [59:31] feature in the plug-in. If you're in the [59:33] back end and you click on a landmark, it [59:35] will click over and [59:37] and highlight it. Um [59:40] And previously you weren't able to see [59:42] this map, right? Right. Right. [59:44] >> You could just get to the landmark from [59:46] the editor. [59:48] And this will show the accessible name [59:49] of the [59:51] landmarks as well. Like these are [59:52] actually labeled two and three. Like [59:54] there's in the footer there's two [59:55] navigations. One's labeled two and one's [59:58] labeled three. You should give it an and [60:00] I would say two and three is not [60:01] descriptive. [60:06] Um like this navigation element up here [60:08] actually has a label of toolbar and then [60:11] the main navigation has a label of post [60:13] navigation. [60:15] So we're trying to show you here your [60:18] your [60:20] landmarks and their accessible labels. [60:22] Now, I want to test something. [60:25] Um [60:27] So like you didn't pull up the other tab [60:28] which I haven't actually tested myself [60:30] yet. [60:32] The [60:33] uh I'm going to click on a landmark and [60:36] see if it actually highlights. [60:40] Nav. [60:42] Ooh. [60:44] It went to it but it didn't highlight [60:45] it. Okay, little bit of a bug but this [60:47] is beta it's not released. [60:49] But it did scroll to it. So it will [60:51] highlight here in the panel [60:54] uh once you click landmarks from the [60:56] back end. [60:58] But we've got one final one here. Tab [61:00] order. [61:01] Why does tab order matter, right? What [61:04] So for [61:06] good accessibility you want to make sure [61:07] that you have, you know, a tab order [61:10] that follows the visual order of the [61:12] page left to right up to down up down, [61:14] right? You want to be mindful not to be [61:17] modifying tab indexes as to throw this [61:19] off. [61:21] Um but if I click on tab order here, [61:24] I'm now presented with [61:27] a scribble across my page as it looks, [61:29] right? [61:30] But what this is is this is a visual [61:32] representation of the tab order. So all [61:35] the focusable elements on the page [61:38] have a have a little red circle with a [61:40] number in them and I'm not sure if red's [61:41] the right color to use here cuz red [61:44] in kind of what we do means bad. [61:46] Um so I'm not sure if it's going to end [61:48] up being red or if we switch it to kind [61:50] of our like highlighter pink or blue or [61:53] something to kind of make neutralize it [61:55] to [61:56] not make it seem like it's a bad thing. [61:59] Um [62:00] But anyway. Well, talking of bad things, [62:03] having this lane here immediately shows [62:05] me that the tab index is [62:07] Yeah. [62:07] >> horrible. [62:09] Horrible at the beginning. Yeah, so you [62:11] can see I added a link here. It's called [62:12] wrong tab index and then I gave it a tab [62:15] index that was wrong and you can see in [62:17] the panel that it's actually it's [62:19] highlighted as as wrong. I'm not sure [62:21] why this is orange. Probably should be [62:23] red. But uh [62:26] it shows that and I can click on this in [62:30] the panel and it will scroll to. [62:33] So if I go through I'm like, okay, [62:34] what's my tab order? Like without [62:35] actually like tabbing through the page [62:37] cuz sometimes your page doesn't have [62:38] proper focus [62:40] uh outlines and you can't really tell [62:41] where you're at, the page that you're [62:43] remediating. So I click on the first [62:44] one. Oh wait, hold on. This is [62:46] further down. [62:47] >> the page. That's not in a That's not [62:49] right and you know, the the highlighter [62:52] is signifying that this is not right. [62:54] But the rest are. So when I start [62:56] clicking through those and you know, [62:58] they they all follow the order. [63:00] And [63:01] uh we give a little label on each [63:03] highlight here that says the tab stop [63:06] and what it is. These are links. [63:08] Uh what else have we got? Like a text [63:10] area here. [63:12] So we're trying to we're trying to [63:14] highlight what the actual focusable [63:16] element is and sometimes that can be [63:18] helpful, too. [63:20] Uh like that's a submit and I think all [63:23] the rest are are links. So you can just [63:26] follow these down the page, make sure [63:27] your tab order is correct. [63:30] So that is [63:31] >> Orphaned issues where it isn't correct [63:33] as this exactly show. [63:35] Yeah, at the very top. Yep. [63:38] So these are a few little utilities that [63:40] we're trying to bring into the [63:41] highlighter to help you remediate your [63:43] page and to kind of give you a little [63:45] bit more [63:46] uh [63:47] information on [63:49] what may be the problem and a little bit [63:52] more visual information as well to help [63:55] identify where the problems are. [63:58] So that's a an upcoming thing and thanks [64:02] William who is sitting in the dark here [64:04] for [64:05] >> same for me. My camera doesn't [64:06] [laughter] like it. [64:09] So that's a lot for the release. Now, we [64:12] do have more that was in this release. [64:15] Do we want to like kind of like [64:16] lightning round this and go through like [64:20] some of these? Okay, cool. [64:21] So minor fixes that were also in in the [64:24] latest releases of accessibility checker [64:26] and accessibility checker pro. [64:28] Yeah, so in the pro plug-in we have a [64:31] feature that allows adding the file size [64:33] and type onto links so people are aware [64:36] of what they might be getting when they [64:37] pick that link. Um sometimes it breaks [64:40] layouts which has been a complaint from [64:43] us and at least one user. So now there's [64:46] a modifier class that will allow you to [64:48] turn that off. It will retain it in the [64:50] label so for screen readers it will [64:52] still be accessible but it will avoid [64:55] breaking your layout by injecting that [64:57] text there. [64:59] Um Next thing, so and I actually had to [65:02] enhance this feature this morning. So we [65:04] now have a fail handler in the full site [65:07] scanner for the pro users where if post [65:10] fails the scan properly and it situation [65:13] where it's completely broken and breaks [65:15] our scanner, we now try our best to to [65:17] skip that. And I did fix that [65:21] even more to make it even more robust [65:23] this morning. So in the next pro release [65:25] that will be solved and specifically [65:27] where this has come up is [65:29] privacy policy links. So turns out on [65:32] some sites editors can't change them [65:36] which means we can't appropriately scan [65:38] and save results to them. [65:40] Um next thing in the the list, so pro [65:43] license checks. Every day we check if [65:45] pro license is still active. If it's [65:48] not, [65:49] it can disable on your site. If there's [65:51] a network issue, it could also [65:52] technically disable on the site. So I [65:54] added uh [65:56] recovery mechanism. So if there's a [65:58] network error next time it does check, [66:00] it can reactivate. No longer will you [66:02] hopefully have to go in and click the [66:05] enter license key button ever again. [66:08] Um orphaned issues. So we have a cleanup [66:10] routine. Once a day we try and clear 50 [66:12] orphaned issues. If you've switched post [66:15] types, [66:16] edited your content, deleted the post in [66:18] a non-standard way, um one user [66:20] contacted us and pointed out that it was [66:22] taking quite a long time. He had shifted [66:25] 900 events to [66:28] a different post type orphaned in those [66:30] issues. Now it runs twice a day so it [66:32] will delete up to 100 per day. Hopefully [66:35] you don't ever have that many orphaned [66:37] issues but if you do, we'll clean them [66:39] quicker. [66:40] Um [66:41] Table checks. So now our [66:44] um missing header row will detect proper [66:48] scopes. So if you have a a header that [66:50] has a scope of the full row, no longer [66:53] will the other columns flag as a missing [66:56] header. It will also skip if your table [66:58] has like a row of presentation. So it's [67:01] just a little bit more clever about how [67:03] it identifies [67:06] appropriate headers on the table. [67:07] Previously if you didn't have a TH [67:09] column [67:10] uh or TH for each row, it wouldn't [67:14] it wouldn't consider that as valid [67:15] markup when there is actually some [67:17] parents. So [67:19] um and yeah, I think that's all the the [67:21] minor fixes. There's one major thing if [67:23] you want to quickly [67:25] pull that up or [67:26] mention that, Steve. [67:27] It's above the minor fixes on the list. [67:30] Oh yeah, we skipped one, didn't we? We [67:32] did. [67:34] Okay, there's more. This is like this is [67:37] like Christmas, you know, like your [67:38] parents have given you the big, you [67:40] know, you got your gift from Santa [67:41] Claus. [67:42] You got your gift from your parents and [67:44] you're like you're jazzed, right, as a [67:46] little kid. And then [67:48] And then the cousin shows up there. Then [67:50] in walks that favorite uncle with a big [67:53] old present right at the end. Oh, [67:54] there's more, right? [67:56] So there is more. I did skip. So we did [67:58] lightning round. Those those are more of [68:00] features coming your that are already [68:02] out. They're there for you. [68:04] Um and William's done a great job in in [68:07] getting those in the latest release and [68:09] but we do have another thing to show. We [68:11] are running short on time but we're [68:12] going to try to be fast with it. So [68:14] we've added [68:15] >> saves people a lot of time if they have [68:17] more than one site. Yeah, yeah. [68:19] So we have we've added the ability to [68:22] import and export settings [68:26] uh and from the uh back end. So this is [68:30] a pro feature [68:32] for pro users. So you can export your [68:35] settings as JSON files and you can [68:38] import your settings into another site [68:40] uh with the same JSON file. [68:41] Yeah, so if you're maintaining 15 sites, [68:44] you'll only need to configure one. [68:46] Grab the [68:48] grab the settings. I will call out that [68:50] anything that may be security adjacent [68:53] such as your token for email reports or [68:56] your actual license key does not come [68:58] out in that export. So if you want to [69:01] export the settings file and share it [69:03] with another user, you can do that just [69:05] fine. It will not include your license [69:07] key or [69:09] any [69:10] any of the security information but it [69:11] will include all of the settings. So if [69:13] you've configured your site in a [69:15] specific way and someone else needs that [69:17] file, you can give that to them. [69:20] Yeah, so um let me try to make things [69:23] bigger here. Yeah. [69:25] So if you're running Accessibility [69:27] Checker Pro version 1. [69:31] 22 [69:32] .0 Um [69:35] then you will get this new feature. If [69:37] you go to settings, you'll see there is [69:40] a a fifth tab next to the new email [69:44] reports called import export. So, export [69:48] your Accessibility Checker settings to a [69:50] JSON file, then import them on another [69:53] website. [69:54] >> [snorts] [69:55] >> So, we've got two columns here. In the [69:56] In the left column, it says export [69:59] settings, download your current settings [70:01] to a JSON file. [70:02] And then I've got check boxes for [70:04] include settings and include fixes. [70:07] So, I can choose to [70:09] do export all the settings by itself or [70:13] all the fixes by themselves or [70:14] everything by itself. [70:16] Uh so, you may not be want So, you may [70:19] only want to update somebody's settings [70:21] on their site and not all their fixes. [70:23] Um [70:23] cuz implementing fixes on a website just [70:25] wholesale can be you know, it can be a [70:28] little problematic. You want to [70:30] Well, I mean, I don't know if it's [70:31] problematic. It's probably good. It's [70:33] probably a net positive, right? It's [70:35] actually not positive or not not [70:37] problematic. It's completely positive to [70:39] turn all of our fixes [70:41] >> [laughter] [70:41] >> on. But, what we advocate is that you [70:44] turn them on and you let it scan the [70:45] page so that you can ensure that those [70:48] fixes are working. [70:50] Um [70:51] and then in the right-hand column, we [70:53] have import settings, upload a JSON file [70:56] to restore settings on this website. So, [70:59] there's a file upload input here, and [71:01] then the same check boxes for import [71:04] settings and import fixes. [71:07] So, [71:09] here's an example. So, I'm going to [71:10] leave both checked, and I'm going to [71:12] download this export. Let me I think [71:15] I've got plenty of settings. [71:17] Um because I've been testing this. [71:20] So, I will download this, and then [71:24] Hold on. Let me pull [71:27] Let me pull this up real quick. [71:37] Um I'm not sharing my [71:39] whole screen, so [71:41] I don't So, you're going to have to get [71:42] your IDE up to show. Yeah, yeah. [71:46] Hold on. [71:49] Do you Do you have one of these JSON [71:51] files? [71:51] >> one. I'm just looking. So, since I've [71:53] already got your screen shared here, [71:57] Um [71:59] I do not have one, but I guess I can [72:02] grab one. [72:05] No, I can't cuz I don't have pro [72:06] enabled. [72:07] Okay, here. Let me reshare my screen [72:09] then. [72:10] Um [72:15] I will [72:18] share my whole screen here. [72:36] It won't let me [72:39] stop. All right. [72:42] So, I'm going to share this whole screen [72:44] here. [72:53] All right. So, [72:59] So, you can see here I have the JSON [73:01] file. [73:02] In the JSON file, you can see that we [73:05] have settings, [73:06] and then these are all the exported [73:08] settings, and then we have fixes, and [73:11] these are all the exported fixes. [73:14] Uh and I would say this is loosely human [73:17] readable. [73:18] Yeah, yeah. Yeah, I mean, I think any [73:20] developer could probably go through here [73:22] and and, you know, modify this if they [73:23] need to modify it. [73:25] Um [73:26] with with out with out issue. [73:29] So, I've exported that. If I go over to [73:33] my [73:34] settings, so let's say that I go to a [73:36] different website, which I I'm not on a [73:38] different website, but let's [73:41] let's, you know, modify these settings [73:43] so we can show that [73:46] you know, all these millions of custom [73:48] post types I have. [73:54] I will deselect one at a time. [73:57] I I have I have everybody [73:59] >> I I deselect all button there, right? [74:01] Yeah, yeah. [74:03] So, I'm just deselecting all these to [74:05] kind of show that they will change, [74:08] right? [74:10] So, if I hit save on that, and then if I [74:12] go to fixes, [74:15] I'm just going to deselect all the [74:16] fixes. [74:22] Look at all these wonderful fixes. [74:25] You've got a horrible test site if you [74:27] need all them. [74:29] >> [laughter] [74:30] >> So, if I go back to import export, and I [74:34] uh [74:36] Let me [74:38] go here. [74:39] I'm just going to drag and drop that [74:42] import file, [74:44] and I want to import both. [74:46] But, even though this file contains both [74:49] settings and fixes, I can actually only [74:51] import [74:53] settings. So, I'm going to deselect [74:55] fixes, and then I'm going to run an [74:56] import, and then I get a success [74:58] message. [75:00] And then if I go over to settings, you [75:01] can see these things are all selected [75:02] again because I I imported that. But, my [75:04] fixes are not selected because I did not [75:06] import those. [75:08] So, if I now want to import my fixes [75:10] with the same file, [75:12] drag and drop that there, and then I'll [75:14] deselect settings cuz I don't want to [75:16] override my settings I just imported, [75:19] and I select import fixes, and I run the [75:21] import. [75:22] You can now see on the fixes I have all [75:25] the fixes selected that were selected [75:27] when I ran the initial import. Nice. [75:32] And And for a single site, this may not [75:35] save a lot of time, but if you have 15, [75:38] 20 sites, it's going to save you a lot [75:40] lot of hours. [75:41] >> Right. [75:42] So, we do have like we do have a way to [75:46] manage settings like this in a [75:48] multi-site Yes. [75:50] >> in a network. So, at the beginning of [75:52] the live stream, I mentioned that we [75:53] have this multi-site add-on uh that you [75:56] can use to manage your [75:58] your Accessibility Checker license key [76:00] and stats throughout the whole network. [76:02] And and what it also does is it allows [76:05] you to select a [76:07] So, you set up one site, and then it [76:09] allows you to select that site, and then [76:11] allows you to take those settings from [76:12] that one site and duplicate it on all [76:15] the other sites. [76:17] So, that is a way to do it in a [76:20] multi-site, but there's not a way to do [76:22] it not in a multi-site. And [76:25] what we do here at Equalized Digital is [76:28] sometimes we get enterprise clients that [76:30] have, you know, a large number of [76:32] websites, [76:34] and they engage with us to do what we [76:36] call our white glove onboard. And that's [76:38] where we will actually go through all of [76:40] their websites, and we will onboard [76:43] Accessibility Checker [76:45] um onto those sites, set up this the [76:48] desired settings uh that we've [76:50] determined uh with with the client, and [76:53] we will white glove set it all up for [76:56] them on all of their websites, run an [76:58] initial scan so so that they have [77:01] everything up and running, configured, [77:03] and scanned uh all in one fell swoop. [77:06] >> issues. Yep. [77:08] And what the import export does is it it [77:11] This is one of those times where it's [77:12] like, you know, it'd be really nice for [77:14] us to have this. Well, in software, [77:16] sometimes if it's nice for us to have [77:18] it, it's probably nice for everybody [77:19] else to have it, too, right? [77:21] So, this is a little bit of a helping us [77:24] do something, but it also helps you do [77:26] it as well, too. So. Yeah, well, we have [77:28] quite a number of users that are agency [77:30] clients. They have 25 sites. [77:33] We We save them a few minutes every [77:34] single site. Yep. [77:36] >> you know, it's worth doing. [77:38] And it turns out it wasn't that [77:39] complicated to build this, right? [77:41] No, not at all. [77:43] So, [77:45] um that is all of the features. That's [77:48] it. It's just a massive release this [77:51] last month. We've been busy. This coming [77:54] month, we're busy already. We're already [77:55] working on new features, which we teased [77:58] already here in this live stream, and we [78:01] look forward to jumping on again and [78:02] talking about those new things when [78:03] they're ready uh here in a few weeks, [78:06] and uh [78:07] uh or here in a couple weeks, [78:09] and uh [78:11] and we hope that you join us, and we [78:12] hope that you watch after the fact. Uh [78:15] um thanks for joining. If you use [78:17] Accessibility Checker, do us a solid. [78:20] Give it a review. Uh [78:22] um preferably a five-star review [78:24] on uh wordpress.org, and But, if you [78:27] give us a four-star review, I will [78:30] find and fix your problem, so bear that [78:32] in mind as well. [78:33] >> will. [78:33] >> But, don't give me a one-star. We We [78:35] will stop at nothing to resolve your [78:38] issue. We will earn that extra star. [78:40] So. [78:42] Well, I think that concludes our live [78:43] stream for today. Uh thanks uh William [78:47] for joining, and thanks for all your [78:48] hard work on Accessibility Checker over [78:50] the last month, and [78:51] look forward to doing this again. [78:55] I I'll have more light next time, maybe. [78:57] >> Yep. [78:59] It's all right. [79:01] Cool. All right. Take care.  📄 **Full text:** ![[Full Document Contents/Articles/New Highlighter, Email Reports, and Settings Tools.md|New Highlighter, Email Reports, and Settings Tools by YouTube]] ## Highlights - pro as well. Uh free gets some of that summary data that William was talking about, and then pro gets that data plus a little bit more. And we're we'll show that and we'll try to generate these emails so we could show them live here. So, I'm going to pull up William's screen. You ready? Yep. All right. So, we're looking at William's screen. Yep. So, this is the accessibility checker welcome page. And as of version 1.4.0.0, ([View Highlight](https://read.readwise.io/read/01kre5vqn8xetjn6qdrg33fcht)) - Tags: 👻 ai highlighted - the email reports are now available. So, this is what a free user would see on the welcome screen. And just quick start, some documentation links, some general things. So, this is the welcome page. Not the most useful for a free user, but this will be the first page in the plugin you see. So, if we visit the uh settings link the left end menu, takes you to general, and we now have this new tab at the top called accessibility reports, and it is tagged ([View Highlight](https://read.readwise.io/read/01kre5vqqybcmttmq204vwd430)) - Tags: 👻 ai highlighted - Um All right. So, if we look here. Okay, so let me pull up my screen. Okay. So, what this is is this is a preview of the email that would go to your inbox every Monday morning if you're a free user. So, of course, it's just a branded email with Equalize Digital. And it shows this is for my website, stevejones.blog. My accessibility status is two issues ([View Highlight](https://read.readwise.io/read/01kre5vqsdyze61bt419x9r13p)) - Tags: 👻 ai highlighted - and you have to have uh accessibility checker pro to scan taxonomies. And uh then we just have a little bit of, you know, unlock a little bit of an upgrade message here to unlock full coverage reports to show free users that there is more data that can can be sent out through these emails. Um So, that is a free email. Let me switch back. So, we should probably now go through the the pro ([View Highlight](https://read.readwise.io/read/01kre5vqw8571ftzgfc9v3cx4f)) - Tags: 👻 ai highlighted - those reports and keeping you up to date on the status of the accessibility on your website. So, but that's not all. That's a big feature. We could have spent this whole episode talking about that, but we have more. What else did we do? >> want to >> [laughter] >> What else did we do? Yeah, so this one's actually, you know, a nice and easy one to show if you want to pull up my screen. It's It's easier to show and ([View Highlight](https://read.readwise.io/read/01kre5vr261haekzjw0jmb37ah)) - Tags: 👻 ai highlighted - Cool. Yep. But that's not it. There's more. How is there more, William? Because we waited a month before we done >> [laughter] >> done another one of these change logs. That's right. So, if you've been using accessibility checker for any time any length of time, you're probably familiar with our front end highlighter. So, which is uh allows you to go to the ([View Highlight](https://read.readwise.io/read/01kre5vr5gz6654kyagt3jjwqw)) - Tags: 👻 ai highlighted