{"id":1256,"date":"2025-05-02T11:00:00","date_gmt":"2025-05-02T11:00:00","guid":{"rendered":"http:\/\/www.diveintoaccessibility.com\/?p=1256"},"modified":"2025-05-05T16:08:26","modified_gmt":"2025-05-05T16:08:26","slug":"wcag-3-0s-proposed-scoring-model-a-shift-in-accessibility-evaluation","status":"publish","type":"post","link":"http:\/\/www.diveintoaccessibility.com\/index.php\/2025\/05\/02\/wcag-3-0s-proposed-scoring-model-a-shift-in-accessibility-evaluation\/","title":{"rendered":"WCAG 3.0\u2019s Proposed Scoring Model: A Shift In Accessibility Evaluation"},"content":{"rendered":"<p>              <title>WCAG 3.0\u2019s Proposed Scoring Model: A Shift In Accessibility Evaluation<\/title><\/p>\n<article>\n<header>\n<h1>WCAG 3.0\u2019s Proposed Scoring Model: A Shift In Accessibility Evaluation<\/h1>\n<address>Mikhail Prosmitskiy<\/address>\n<p>                  2025-05-02T11:00:00+00:00<br \/>\n                  2025-05-05T15:33:02+00:00<br \/>\n                <\/header>\n<p>Since their introduction in <a href=\"https:\/\/www.w3.org\/TR\/WAI-WEBCONTENT\/\">1999<\/a>, the <a href=\"https:\/\/www.w3.org\/WAI\/standards-guidelines\/wcag\/\">Web Content Accessibility Guidelines<\/a> (WCAG) have shaped how we design and develop inclusive digital products. The WCAG 2.x series, released in <a href=\"https:\/\/www.w3.org\/TR\/WCAG20\/\">2008<\/a>, introduced clear technical criteria judged in a binary way: either a success criterion is met or not. While this model has supported regulatory clarity and auditability, its <strong>\u201call-or-nothing\u201d nature<\/strong> often fails to reflect the nuance of actual user experience (UX).<\/p>\n<p>Over time, that disconnect between technical conformance and lived usability has become harder to ignore. People engage with digital systems in complex, often nonlinear ways: navigating multistep flows, dynamic content, and interactive states. In these scenarios, checking whether an element passes a rule doesn\u2019t always answer the main question: can someone actually use it?<\/p>\n<p><a href=\"https:\/\/www.w3.org\/WAI\/standards-guidelines\/wcag\/wcag3-intro\/\">WCAG 3.0<\/a> is still in <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0\/#sotd\">draft<\/a>, but is evolving &mdash; and it represents a <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0\/#about-wcag-3-0\">fundamental rethinking<\/a> of how we evaluate accessibility. Rather than asking whether a requirement is technically met, it asks how well users with disabilities can complete meaningful tasks. Its new outcome-based model introduces a <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#additional-concepts\">flexible scoring system<\/a> that <strong>prioritizes usability over compliance<\/strong>, shifting focus toward the quality of access rather than the mere presence of features.<\/p>\n<h2 id=\"draft-status-ambitious-but-still-evolving\">Draft Status: Ambitious, But Still Evolving<\/h2>\n<p>WCAG 3.0 was first introduced as a public working draft by the <a href=\"https:\/\/www.w3.org\/\">World Wide Web Consortium<\/a> (W3C) <a href=\"https:\/\/www.w3.org\/WAI\/about\/groups\/agwg\/\">Accessibility Guidelines Working Group<\/a> in early <a href=\"https:\/\/www.w3.org\/TR\/2021\/WD-wcag-3.0-20210121\/\">2021<\/a>. The draft is still under active development and is not expected to reach <a href=\"https:\/\/www.w3.org\/standards\/about\/#what-are-web-standards\">W3C Recommendation status<\/a> for <a href=\"https:\/\/www.w3.org\/WAI\/standards-guidelines\/wcag\/wcag3-intro\/#timeline\">several years, if not decades<\/a>, by some accounts. This extended timeline reflects both the complexity of the task and the ambition behind it:<\/p>\n<blockquote><p>WCAG 3.0 isn\u2019t just an update &mdash; it\u2019s a paradigm shift.<\/p><\/blockquote>\n<p>Unlike WCAG 2.x, which focused primarily on web pages, WCAG 3.0 aims to cover a much <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#wcag-3-0-scope\">broader ecosystem<\/a>, including applications, tools, connected devices, and emerging interfaces like voice interaction and extended reality. It also <a href=\"https:\/\/www.w3.org\/WAI\/standards-guidelines\/wcag\/wcag3-intro\/#wcag-3-name\">rebrands itself<\/a> as the W3C Accessibility Guidelines (while the WCAG acronym remains the same), signaling that <strong>accessibility is no longer a niche concern<\/strong> &mdash; it\u2019s a baseline expectation across the digital world.<\/p>\n<p>Importantly, WCAG 3.0 <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#intro\">will not immediately replace 2.x<\/a>. Both standards will coexist, and conformance to WCAG 2.2 will continue to be valid and necessary for some time, especially in legal and policy contexts.<\/p>\n<p>This expansion isn\u2019t just technical.<\/p>\n<blockquote class=\"pull-quote\">\n<p>\n    <a class=\"pull-quote__link\" aria-label=\"Share on Twitter\" href=\"https:\/\/twitter.com\/share?text=%0aWCAG%203.0%20reflects%20a%20deeper%20philosophical%20shift:%20accessibility%20is%20moving%20from%20a%20model%20of%20compliance%20toward%20a%20model%20of%20effectiveness.%0a&amp;url=https:\/\/smashingmagazine.com%2f2025%2f05%2fwcag-3-proposed-scoring-model-shift-accessibility-evaluation%2f\"><\/p>\n<p>WCAG 3.0 reflects a deeper philosophical shift: accessibility is moving from a model of compliance toward a model of effectiveness.<\/p>\n<p>    <\/a>\n  <\/p>\n<div class=\"pull-quote__quotation\">\n<div class=\"pull-quote__bg\">\n      <span class=\"pull-quote__symbol\">\u201c<\/span><\/div>\n<\/p><\/div>\n<\/blockquote>\n<p>Rules alone can\u2019t capture whether a system truly works for someone. That\u2019s why WCAG 3.0 leans into <strong>flexibility<\/strong> and <strong>future-proofing<\/strong>, aiming to support evolving technologies and real-world use over time. It formalizes a principle long understood by practitioners:<\/p>\n<blockquote><p>Inclusive design isn\u2019t about passing a test; it\u2019s about enabling people.<\/p><\/blockquote>\n<div data-audience=\"non-subscriber\" data-remove=\"true\" class=\"feature-panel-container\">\n<aside class=\"feature-panel\">\n<div class=\"feature-panel-left-col\">\n<div class=\"feature-panel-description\">\n<p>Meet <strong><a data-instant href=\"\/printed-books\/image-optimization\/\">Image Optimization<\/a><\/strong>, Addy Osmani\u2019s new practical guide to optimizing and delivering <strong>high-quality images<\/strong> on the web. Everything in one single <strong>528-pages<\/strong> book.<\/p>\n<p><a data-instant href=\"https:\/\/www.smashingmagazine.com\/printed-books\/image-optimization\/\" class=\"btn btn--green btn--large\">Jump to table of contents&nbsp;\u21ac<\/a><\/div>\n<\/div>\n<div class=\"feature-panel-right-col\"><a data-instant href=\"https:\/\/www.smashingmagazine.com\/printed-books\/image-optimization\/\" class=\"feature-panel-image-link\"><\/p>\n<div class=\"feature-panel-image\">\n<img loading=\"lazy\" class=\"feature-panel-image-img\" src=\"https:\/\/archive.smashing.media\/assets\/344dbf88-fdf9-42bb-adb4-46f01eedd629\/87fd0cfa-692e-459c-b2f3-15209a1f6aa7\/image-optimization-shop-cover-opt.png\" alt=\"Feature Panel\" width=\"480\" height=\"697\" \/><\/p>\n<\/div>\n<p><\/a>\n<\/div>\n<\/aside>\n<\/div>\n<h2 id=\"a-new-structure-from-success-criteria-to-outcomes-and-methods\">A New Structure: From Success Criteria To Outcomes And Methods<\/h2>\n<p>WCAG 2.x is structured around <a href=\"https:\/\/www.w3.org\/WAI\/fundamentals\/accessibility-principles\/\">four foundational principles<\/a> &mdash; Perceivable, Operable, Understandable, and Robust (aka POUR) &mdash; and testable success criteria organized into <a href=\"https:\/\/www.w3.org\/WAI\/WCAG22\/Understanding\/conformance#levels\">three conformance levels<\/a> (A, AA, AAA). While technically precise, these criteria often emphasize implementation over impact.<\/p>\n<p>WCAG 3.0 <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0\/#conformance-0\">reorients this structure<\/a> toward user needs and real outcomes. Its hierarchy is built on:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0\/#guidelines\"><strong>Guidelines<\/strong><\/a>: High-level accessibility goals tied to specific user needs.<\/li>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#guidelines\"><strong>Outcomes<\/strong><\/a>: Testable, user-centered statements (e.g., \u201cUsers have alternatives for time-based media\u201d).<\/li>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#requirements-and-methods\"><strong>Methods<\/strong><\/a>: Technology-specific or agnostic techniques that help achieve the outcomes, including code examples and test instructions.<\/li>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#structure\"><strong>How-To Guides<\/strong><\/a>: Narrative documentation that provides practical advice, user context, and design considerations.<\/li>\n<\/ul>\n<p>This shift is more than organizational. It reflects a deeper commitment to aligning technical implementation with UX. Outcomes speak <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#readability\">the language of capability<\/a>, which is about what users should be able to do (rather than just technical presence).<\/p>\n<p>Crucially, outcomes are also where conformance scoring begins to take shape. For example, imagine a checkout flow on an e-commerce website. Under WCAG 2.x, if even one field in the checkout form lacks a label, <a href=\"https:\/\/www.w3.org\/WAI\/WCAG22\/Understanding\/info-and-relationships.html\">the process may fail AA conformance entirely<\/a>. However, under WCAG 3.0, that same flow might be evaluated <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#conformance-models\">across multiple outcomes<\/a> (such as keyboard navigation, form labeling, focus management, and error handling), with each outcome receiving a separate score. If most areas score well but the error messaging is poor, the overall rating might be \u201cGood\u201d instead of \u201cExcellent\u201d, prompting targeted improvements without negating the entire flow\u2019s accessibility.<\/p>\n<h2 id=\"from-binary-checks-to-graded-scores\">From Binary Checks To Graded Scores<\/h2>\n<p>Rather than relying on pass or fail outcomes, WCAG 3.0 <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#additional-concepts\">introduces a scoring model<\/a> that reflects how well accessibility is supported. This shift allows teams to <strong>recognize partial successes<\/strong> and prioritize real improvements.<\/p>\n<h3 id=\"how-scoring-works\">How Scoring Works<\/h3>\n<p>Each outcome in WCAG 3.0 is evaluated through <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#types-of-tests\">one or more atomic tests<\/a>. These can include the following:<\/p>\n<ul>\n<li><strong>Binary tests<\/strong>: \u201cYes\u201d and \u201cno\u201d outcomes (e.g., does every image have alternative text?)<\/li>\n<li><strong>Percentage-based tests<\/strong>: Coverage-based scoring (e.g., what percentage of form fields have labels?)<\/li>\n<li><strong>Qualitative tests<\/strong>: Rated judgments based on criteria (e.g., how descriptive is the alternative text?)<\/li>\n<\/ul>\n<p>The result of these tests produces a score for each outcome, often normalized on a 0-4 or 0-5 scale, with labels like Poor, Fair, Good, and Excellent. These scores are then aggregated across functional categories (vision, mobility, cognition, etc.) and user flows.<\/p>\n<p>This allows teams to measure progress, not just compliance. A product that improves from \u201cFair\u201d to \u201cGood\u201d over time shows real <strong>evolution<\/strong> &mdash; <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#broad-disability-support\">a concept<\/a> that doesn\u2019t exist in WCAG 2.x.<\/p>\n<h3 id=\"critical-errors-a-balancing-mechanism\">Critical Errors: A Balancing Mechanism<\/h3>\n<p>To ensure that severity still matters, WCAG 3.0 introduces <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#additional-concepts\">critical errors<\/a>, which are high-impact accessibility failures that can override an otherwise positive score.<\/p>\n<p>For example, consider a checkout flow. Under WCAG 2.x, a single missing label might cause the entire flow to fail conformance. WCAG 3.0, however, evaluates multiple outcomes &mdash; like form labeling, keyboard access, and error handling &mdash; each with its own score. Minor issues, such as unclear error messages or a missing label on an optional field, might lower the rating from \u201cExcellent\u201d to \u201cGood\u201d, without invalidating the entire experience.<\/p>\n<p>But if a user cannot complete a core action, like submitting the form, making a purchase, or logging in, that constitutes a <strong>critical error<\/strong>. These failures directly block task completion and significantly reduce the overall score, regardless of how polished the rest of the experience is.<\/p>\n<p>On the other hand, problems with non-essential features &mdash; like uploading a profile picture or changing a theme color &mdash; are considered lower-impact and won\u2019t weigh as heavily in the evaluation.<\/p>\n<div class=\"partners__lead-place\"><\/div>\n<h2 id=\"conformance-levels-bronze-silver-gold\">Conformance Levels: Bronze, Silver, Gold<\/h2>\n<p>In place of categorizing conformance in tiers of Level A, Level AA, and Level AAA, WCAG 3.0 proposes <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#additional-concepts\">three different conformance tiers<\/a>:<\/p>\n<ul>\n<li><strong>Bronze<\/strong>: The new minimum. It is <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#conformance-models\">comparable to WCAG 2.2 Level AA<\/a>, but based on scoring and foundational outcomes. The requirements are considered achievable via automated and guided manual testing.<\/li>\n<li><strong>Silver<\/strong>: This is a higher standard, requiring broader coverage, higher scores, and <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#design_principles\">usability validation from people with disabilities<\/a>.<\/li>\n<li><strong>Gold<\/strong>: The highest tier. Represents exemplary accessibility, likely requiring inclusive design processes, innovation, and extensive user involvement.<\/li>\n<\/ul>\n<p>Unlike in WCAG 2.2, where Level AAA is often seen as aspirational and inconsistent, these levels are intended to <strong>incentivize progression<\/strong>. They can also <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0\/#defining-conformance-scope\">be scoped<\/a> in the sense that teams can claim conformance for a checkout flow, mobile app, or specific feature, allowing iterative improvement.<\/p>\n<h2 id=\"what-you-should-do-now\">What You Should Do Now<\/h2>\n<p>While WCAG 3.0 is still being developed, its direction is clear. That said, it\u2019s important to acknowledge that the guidelines are not expected to be finalized in a few years. Here\u2019s how teams can prepare:<\/p>\n<ul>\n<li><strong>Continue pursuing WCAG 2.2 Level AA.<\/strong> <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0\/#about-wcag-3-0\">It remains<\/a> the most robust, recognized standard.<\/li>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#abstract\"><strong>Familiarize yourself<\/strong><\/a> <strong>with WCAG 3.0 drafts<\/strong>, especially the outcomes and scoring model.<\/li>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#oppotunities_usability\"><strong>Start thinking in outcomes.<\/strong><\/a> Focus on what users need to accomplish, not just what features are present.<\/li>\n<li><strong>Embed accessibility into workflows.<\/strong> Shift left. Don\u2019t test at the end &mdash; design and build with access in mind.<\/li>\n<li><a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#design_principles\"><strong>Involve<\/strong><\/a> <strong>users<\/strong> with disabilities early and regularly.<\/li>\n<\/ul>\n<p>These practices won\u2019t just make your product more inclusive; they\u2019ll position your team to excel under WCAG 3.0.<\/p>\n<h2 id=\"potential-downsides\">Potential Downsides<\/h2>\n<p>Even though WCAG 3.0 presents a bold step toward more <strong>holistic accessibility<\/strong>, several structural risks deserve early attention, especially for organizations navigating regulation, scaling design systems, or building sustainable accessibility practices. Importantly, many of these risks are interconnected: challenges in one area may amplify issues in others.<\/p>\n<h3 id=\"subjective-scoring\">Subjective Scoring<\/h3>\n<p>The move from binary pass or fail criteria to scored evaluations introduces room for <strong>subjective interpretation<\/strong>. Without standardized calibration, the same user flow might receive different scores depending on the evaluator. This makes comparability and repeatability harder, particularly in procurement or multi-vendor environments. A simple alternative text might be rated as \u201cadequate\u201d by one team and \u201cunclear\u201d by another.<\/p>\n<h3 id=\"reduced-compliance-clarity\">Reduced Compliance Clarity<\/h3>\n<p>That same subjectivity leads to a second concern: <strong>the erosion of clear compliance thresholds<\/strong>. Scored evaluations replace the binary clarity of \u201ccompliant\u201d or \u201cnot\u201d with a more flexible, but less definitive, outcome. This could complicate legal enforcement, contractual definitions, and audit reporting. In practice, a product might earn a \u201cGood\u201d rating while still presenting critical usability gaps for certain users, creating a disconnect between score and actual access.<\/p>\n<h3 id=\"legal-and-policy-misalignment\">Legal and Policy Misalignment<\/h3>\n<p>As clarity around compliance blurs, so does alignment with existing legal frameworks. Many current laws explicitly reference WCAG 2.x and its A, AA, and AAA levels (e.g. <a href=\"https:\/\/www.section508.gov\/manage\/laws-and-policies\/\">Section 508 of the Rehabilitation Act of 1973<\/a>, <a href=\"https:\/\/commission.europa.eu\/strategy-and-policy\/policies\/justice-and-fundamental-rights\/disability\/union-equality-strategy-rights-persons-disabilities-2021-2030\/european-accessibility-act_en\">European Accessibility Act<\/a>, <a href=\"https:\/\/www.gov.uk\/guidance\/accessibility-requirements-for-public-sector-websites-and-apps\">The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018<\/a>).<\/p>\n<p>Until WCAG 3.0 is formally mapped to those standards, its use in regulated contexts may introduce risk. Teams operating in healthcare, finance, or public sectors will likely need to maintain dual conformance strategies in the interim, increasing cost and complexity.<\/p>\n<h3 id=\"risk-of-minimum-viable-accessibility\">Risk Of Minimum Viable Accessibility<\/h3>\n<p>Perhaps most concerning, this ambiguity can set the stage for a \u201cminimum viable accessibility\u201d mindset. Scored models risk encouraging \u201cBronze is good enough\u201d thinking, particularly in deadline-driven environments. A team might deprioritize improvements once they reach a passing grade, even if essential barriers remain.<\/p>\n<p>For example, a mobile app with strong keyboard support but missing audio transcripts could still achieve a passing tier, leaving some users excluded.<\/p>\n<div class=\"partners__lead-place\"><\/div>\n<h2 id=\"conclusion\">Conclusion<\/h2>\n<p>WCAG 3.0 marks a <strong>new era in accessibility<\/strong> &mdash; one that better reflects the diversity and complexity of real users. By shifting from checklists to scored evaluations and from rigid technical compliance to <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-requirements\/#broad-disability-support\">practical usability<\/a>, it encourages teams to prioritize real-world impact over theoretical perfection.<\/p>\n<p>As one might say, <em>\u201cIt\u2019s not about the score. It\u2019s about who can use the product.\u201d<\/em> In my own experience, I\u2019ve seen teams pour hours into fixing minor color contrast issues while overlooking broken keyboard navigation, leaving screen reader users unable to complete essential tasks. WCAG 3.0\u2019s focus on outcomes reminds us that accessibility is fundamentally about <a href=\"https:\/\/www.w3.org\/TR\/wcag-3.0-explainer\/#goals\">functionality and inclusion<\/a>.<\/p>\n<blockquote class=\"pull-quote\">\n<p>\n    <a class=\"pull-quote__link\" aria-label=\"Share on Twitter\" href=\"https:\/\/twitter.com\/share?text=%0aAt%20the%20same%20time,%20WCAG%203.0%e2%80%99s%20proposed%20scoring%20models%20introduce%20new%20responsibilities.%20Without%20clear%20calibration,%20stronger%20enforcement%20patterns,%20and%20a%20cultural%20shift%20away%20from%20%e2%80%9cgood%20enough,%e2%80%9d%20we%20risk%20losing%20the%20very%20clarity%20that%20made%20WCAG%202.x%20enforceable%20and%20actionable.%20The%20promise%20of%20flexibility%20only%20works%20if%20we%20use%20it%20to%20aim%20higher,%20not%20to%20settle%20earlier.%0a&amp;url=https:\/\/smashingmagazine.com%2f2025%2f05%2fwcag-3-proposed-scoring-model-shift-accessibility-evaluation%2f\"><\/p>\n<p>At the same time, WCAG 3.0\u2019s proposed scoring models introduce new responsibilities. Without clear calibration, stronger enforcement patterns, and a cultural shift away from \u201cgood enough,\u201d we risk losing the very clarity that made WCAG 2.x enforceable and actionable. The promise of flexibility only works if we use it to aim higher, not to settle earlier.<\/p>\n<p>    <\/a>\n  <\/p>\n<div class=\"pull-quote__quotation\">\n<div class=\"pull-quote__bg\">\n      <span class=\"pull-quote__symbol\">\u201c<\/span><\/div>\n<\/p><\/div>\n<\/blockquote>\n<p>For teams across design, development, and product leadership, this shift is a chance to rethink what success means. Accessibility isn\u2019t about ticking boxes &mdash; it\u2019s about enabling people.<\/p>\n<p>By preparing now, being mindful of the risks, and focusing on user outcomes, we don\u2019t just get ahead of WCAG 3.0 &mdash; we build digital experiences that are truly usable, sustainable, and inclusive.<\/p>\n<h3 id=\"further-reading-on-smashingmag\">Further Reading On SmashingMag<\/h3>\n<ul>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2023\/10\/roundup-wcag-explainers\/\">A Roundup Of WCAG 2.2 Explainers<\/a>,\u201d Geoff Graham<\/li>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2024\/07\/getting-bottom-minimum-wcag-conformant-interactive-element-size\/\">Getting To The Bottom Of Minimum WCAG-Conformant Interactive Element Size<\/a>,\u201d Eric Bailey<\/li>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2024\/06\/how-make-strong-case-accessibility\/\">How To Make A Strong Case For Accessibility<\/a>,\u201d Vitaly Friedman<\/li>\n<li>\u201c<a href=\"https:\/\/www.smashingmagazine.com\/2024\/02\/web-designer-accessibility-advocacy-toolkit\/\">A Designer\u2019s Accessibility Advocacy Toolkit<\/a>,\u201d Yichan Wang<\/li>\n<\/ul>\n<div class=\"signature\">\n  <img src=\"https:\/\/www.smashingmagazine.com\/images\/logo\/logo--red.png\" alt=\"Smashing Editorial\" width=\"35\" height=\"46\" loading=\"lazy\" \/><br \/>\n  <span>(gg, yk)<\/span>\n<\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"<p>WCAG 3.0\u2019s Proposed Scoring Model: A Shift In Accessibility Evaluation WCAG 3.0\u2019s Proposed Scoring Model: A Shift In Accessibility Evaluation Mikhail Prosmitskiy 2025-05-02T11:00:00+00:00 2025-05-05T15:33:02+00:00 Since [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10],"tags":[],"_links":{"self":[{"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/posts\/1256"}],"collection":[{"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/comments?post=1256"}],"version-history":[{"count":1,"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/posts\/1256\/revisions"}],"predecessor-version":[{"id":1257,"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/posts\/1256\/revisions\/1257"}],"wp:attachment":[{"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/media?parent=1256"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/categories?post=1256"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.diveintoaccessibility.com\/index.php\/wp-json\/wp\/v2\/tags?post=1256"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}