Pope Tech

We're starting to simplify PDF accessibility too, by partnering with GrackleDocs to offer PDF Scanning for our Web Platform and Canvas Dashboards. Learn more in our update: https://lnkd.in/gyHpEcfb

Please join our CEO, Jay Pope, on Monday, May 11th, for a discussion on making web accessibility more manageable for higher-education instructors. He will be joined by a panel of accessibility experts and higher education professionals who will share practical strategies for implementing manageable accessibility improvements in your courses. Title: Accessible Course Materials Without Faculty Burnout Date: May 11, 2026 Time: 1:00 pm ET Register for the roundtable: https://lnkd.in/gnNZBZNf

Have a question about digital accessibility? Meet AIMee, WebAIM’s new AI-powered chatbot designed with accessibility at its core. AIMee can help explain WCAG criteria, suggest accessibility improvements, generate checklists, and more, providing quick guidance while keeping human expertise and verification front and center. Learn more and ask AIMee: https://lnkd.in/eBC-a4Em

Check out our Canvas Accessibility Dashboard webinar, where we'll demo three new features, including BeeLine Reader, PDF Scanning, and our new Course Dashboard that helps faculty tackle accessibility. Great chance to get a sneak peek and ask any questions: https://lnkd.in/eq43i4g5

We're excited to announce that Pope Tech's Canvas Accessibility Suite now includes the award-winning BeeLine Reader readability feature! This partnership means Canvas is the first ever LMS to have BeeLine Reader available. BeeLine's readability feature uses color gradients to help students and faculty read more easily. This helps readers of all ability levels, but is especially helpful for readers with disabilities like dyslexia, ADHD, or visual impairments. Try the BeeLine reader tool and learn more in our announcement: https://lnkd.in/gvD_jPn6

Have you ever wiggled your mouse just to find the cursor? For keyboard users, that cursor is the focus indicator. Without a clear indicator, they’re tabbing through with no way to know where they are on the page. Many devs hide these because browser defaults can be “ugly.” but accessibility doesn’t have to clash with your brand. You can customize focus indicators just like you customize hover states. Three rules for better focus design: - The 3:1 contrast rule: To be visible to most users, your indicator needs a contrast ratio of at least 3:1 against the background. For context, black text on a white page is a 21:1 ratio.  - The 2px rule: A high-contrast line is great, but if it’s too thin, it’s still invisible. The recommended size is at least 2 CSS pixels of thickness to make sure that indicator actually pops.  - Designing for the “job”: A one-size-fits-all box won’t work for every part of your website. We show you how to design different indicators for different elements, like bold underlines for links and robust outlines for buttons, so the user knows what’s coming next when they click an element. Read our full blog here: https://lnkd.in/gATPBjjm #A11y #Webdev #UXDesign

Website navigation is one of the first things users interact with and one of the easiest places for accessibility issues to creep in. Common navigation questions include: Should this submenu open on hover or click? How should keyboard users move through navigation? When does a dropdown become more trouble than it’s worth? In this guide, we break down how to create accessible navigations and sub-menus using semantic HTML and predictable keyboard behavior. Read the article: https://lnkd.in/gz2bKfiP Curious: what issues have you experienced with a navigation bar?  #Accessibility #WebAccessibility #InclusiveDesign #UX #WebDevelopment

Some of the most effective accessibility improvements are also the simplest. Declaring your page’s language is a small step that makes a real difference for screen reader users. Here’s a quick breakdown of why it matters and how to implement it: https://lnkd.in/gAV2x2X6 What other “small but important” accessibility details do you see overlooked? #Accessibility #WebAccessibility #InclusiveDesign

How to set up an accessible page structure and navigation A clear page structure isn’t just a nicety:  it’s a fundamental accessibility requirement that helps users understand where they are and how to navigate your content. In this article, we break down: Why headings, landmarks, and regions matter How assistive technologies use structural elements to build context Practical, actionable steps you can take today to improve page navigation Whether you’re a developer, content strategist, or UX designer, investing in accessible structure improves usability for people who rely on keyboards and assistive tools. Read the full guide: https://lnkd.in/ge_D2CHu #Accessibility #WebAccessibility #A11y #InclusiveDesign #UX #FrontEndDevelopment

What are HTML5 regions and why do they matter for accessibility? HTML5 regions like <nav>, <main>, and <footer> help assistive technology users understand page structure and navigate more efficiently. When these landmarks are missing or misused, keyboard and screen reader users can’t use them to move through a page. In this short video, we explain what HTML5 regions are, how they’re used by assistive technologies, and why they’re a foundational part of accessible web structure. https://lnkd.in/gY-pr6E7 #Accessibility #WebAccessibility #HTML #A11y