Hike One’s Post

Is WCAG already on your agenda? Last week we hosted a roundtable and a workshop to give product leaders a better understanding of the compliance process, where to start, who to involve and how to set up your audit system. 👇 The 5 key takeaways 👇 To help, we've create an audit template to give you a head start. Leave your name in the comments if you'd like to receive it and I'll send it to you!

🚀 Need a template to get your platform ready for WCAG compliance? Get it here! In 2025, the European Accessibility Act will come into effect, with enforcement starting on June 28, 2025, in the Netherlands. To help businesses prepare, we've worked with several clients on quick scans, workshops, and structured guidance on WCAG implementation. As a starting point for your organization, we're offering a WCAG template with 50+ checkpoints to help ensure your platform meets accessibility standards. 📝 Request your free WCAG checklist via our website or comment “WCAG” to this post, and I’ll send it your way. https://lnkd.in/esT2D_rx #WCAG #Accessibility #EuropeanAccessibilityAct #InclusiveDesign #DigitalInclusion

The Accessibility Guidelines Working Group (AG WG) published an updated WCAG 3 Working Draft. This draft includes potential outcomes being explore. https://buff.ly/3WUTm22 #WCAG #WCAG3 #DigitalAccessibility #A11y #Accessibiity

The days of getting an accessibility audit and frantically fixing issues are over. The focus is now on shifting left, maturing accessibility as a capability, and baking it into the DNA of your organization. Here are some great tips on how to do just that!

I wish clients didn't put so much emphasis on WCAG conformance. I wish the emphasis was on making products accessible. I mean, sure, WCAG conformance is important. But it's just a tool to help you make your product more accessible. It's also the very minimum you can do to ensure some level of accessibility. Beyond that - I wish people understood how this standard is being made. Some things that I'm being asked about are not included in the standard. Not because they aren't important to accessibility. But because there were other topics that were addressed first. Or because one interest group was able to be more vocal and convincing than another. Please stop thinking "if it's not in WCAG, it doesn't matter for accessibility".

Nic hits upon a huge issue. The Web Content Accessibility Guidelines (WCAG) are international standards used to measure accessibility. These standards are of course important, but there are many things that WCAG does not measure. WCAG is important for your accessibility goals, but it's a starting goal, rather than the end goal. Treating WCAG as a checklist is not accessibility. A site might every success criteria, but that doesn't mean it will be a good user experience, or that people with disabilities will consider this an accessible site. Centering WCAG as one's main goal for accessibility will de-center disabled people, especially people whose accessibility needs are not thoroughly addressed by WCAG.

🚨 Everyone that DOESN’T work in the public sector – keep scrolling! 🚨 . . . Right, if you’re in the public sector we have one question for you: 💻 Does your website meet WCAG 2.1 AA accessibility requirements? We’re sure you’re already aware of the new WCAG 2.2 guidelines set to be released later this year to make sure all public sector websites are accessible (and if you didn’t know, well, now you do!). It’s now pretty clear that accessibility is not only a nice to have, but it’s a must-have requirement as we work to building a more digitally inclusive space for everyone. ClerksWell has partnered with many of our public sector clients to improve and uphold their WCAG accessibility standards 🤝 Drop us a comment or a DM if you’re interested in having a chat and someone from the team will reach out to you 👇 #webaccessibility #wcag

The WCAG 3 Working Draft update is ready for your review. For background and up-to-date information on W3C Accessibility Guidelines (WCAG) 3, please see:    WCAG 3 Introduction    https://lnkd.in/d8mqtuFk The Accessibility Guidelines Working Group (AG WG) published an updated WCAG 3 Working Draft at:    https://lnkd.in/gNMZ9_g This draft includes potential outcomes that we are exploring. The final set of outcomes in WCAG 3 will be different from this draft. Outcomes will be edited, added, combined, and removed. The purpose of this draft is to: * better understand the scope of user needs and how they could be addressed in an accessibility standard, * request assistance in identifying gaps, and * request assistance locating and conducting research to validate or invalidate the drafted outcomes. Some of the outcomes are marked as needing research. We are particularly interested in assistance identifying or conducting research to support or refute them. For your review: When reviewing this update, please focus on the Guidelines section. We did not make changes to conformance related sections. Please consider the following questions when reviewing the outcomes in this draft: * What outcomes needed to make web content accessible are missing? * What research supports or refutes these outcomes? * Are any of these outcomes out of scope for accessibility standards? If so, please explain why. To provide input, please file GitHub issues at:    https://lnkd.in/eyd-HefV Or, if you are unable to use GitHub, send email to public-agwg-comments@w3.org Please create separate GitHub issues or email messages for each topic (rather than putting multiple topics in a single issue or email). Thank you in advance for your contributions to WCAG 3. This draft reflects ongoing work on WCAG 3. If you have questions or concerns, please contact the AG Chairs via email to: group-ag-chairs@w3.org

With US accessibility legislation now a reality, we've received a large influx of questions around Section 508, how it differs from WCAG, and if Stark helps you achieve that. For starters: yes, we do! We put together a guide to break it all down for you and help your team spearhead your way toward accessibility.

🚀 Is Your Website WCAG 2.0 AA Compliant? 🌐 Web accessibility is not just about inclusivity—it's a legal and business necessity! Here's what your site needs for WCAG 2.0 AA compliance: ✅ Readable Text: Contrast ratio of 4.5:1 or higher. ✅ Alt Text: Descriptive text for all images. ✅ Keyboard Navigation: Ensure full functionality without a mouse. ✅ Captions: Provide captions for videos. ✅ Error Handling: Clear error messages for forms. ✅ Logical Navigation: Predictable focus order and structure. If you want to know more, read my new article in the link below. #Accessibility #WCAG #InclusiveDesign #WebDevelopment