You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WCAG 2’s conformance model is one of its biggest limitations. It works fine for individual pages, but scaled up to whole sites and apps as everyone needs to do, it often falls short. There are many complex challenges like for SPAs, authoring tools, third-party content, fast changing content, etc. WCAG 3.0 needs a conformance model that can work for full websites and apps, and which accounts for the limitations that come with doing accessibility at scale. The conformance model in this latest draft seems to be less certain than before even, with bronze / silver / gold levels now removed.
In response, I had said (/will say shortly):
There are likely to be 2 types of conformance: Per-view (similar to WCAG 2), and a site-level conformance. The per-view model is straightforward, the site-level we can work on in parallel once more guidelines are fleshed out.
This issues is being created to track this as a to-do item.
The text was updated successfully, but these errors were encountered:
From an email, creating this issue:
In response, I had said (/will say shortly):
This issues is being created to track this as a to-do item.
The text was updated successfully, but these errors were encountered: