Organization of W3

for the first time I  saw something today that seemed to make sense to me for the organization of WCAG3  
Thanks go everyone who contributed ideas to this


Outcomes:  What we want to be true in general 
Guidelines:  the things to be done toward achieving that outcome (whether testable to not) (category title) 
Requirments:  Things that are required by WCAG  (at some level named next to the item or always )
Recommendations:   Things we can’t require but are good and important to do
Assertions:  of Practices that are done to help achieve outcome 
(assertions can be made for each recommendation by default) 


When we actually implement it I THINK we will find some of the recommendations will relate directly to a requirement - and sometimes they won’t.

So we might keep in mind two approaches and see which one fits

1)  Recommendations go under Requirements (and at the end as  “other recommendations)
2)  Recommendations all go after Requirements and if they refer to the requirement they extend 
this latter one has two disadvantages I  think
the recommendations are not next to the requirement they extend - meaning when you read the requirement you don’t see the recommendations
it is too easy to just cut them off  and just leave requirements without recommendations


So suggested organization 
 
Outcomes:   What we want to be true in general 
Guidelines:  the things to be done toward achieving that outcome (whether testable to not) (category title) 
Requirments:  Things that are required by WCAG  (at some level named next to the item or always )
Recommendations specific to a requirement
Other Recommendations:   Things we can’t require but are good and important to do
Assertions:  of Practices that are done to help achieve outcome 
Note: Assertions can be made for each recommendation  
<other assertions we identify>


How we could relate this to Conformance levels
we can tag any items as belonging to a level if we identify specific things as required for a level
but we don’t separate things by level visually or in organization - to avoid the current common practice of separating required from recommended. 

Received on Tuesday, 1 October 2024 18:12:33 UTC