- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 19 Jul 2022 18:01:31 +0000
- To: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <PR3PR09MB5347EC65F177FE7DD587E8A7B98F9@PR3PR09MB5347.eurprd09.prod.outlook.com>
Hi everyone, We had a question on the categorisation exercise at the end of the call: What is a sub-guideline? The aim is that a sub-guideline is a part (or whole) of a WCAG 2.2 guideline, but broken down by the categories that we defined previously. The explanation and an example are within the presentation (linked from each template doc): https://docs.google.com/presentation/d/1sGLpBwAAsZfhANpWO3jo0zMOdwDtckhjSmsYpisQfFU/edit#slide=id.g11f44e61c34_0_6 An example based on alt text Based on the understanding document, alt text was given functional needs of: * Use without vision * Comprehend Written language - Use with limited ability to, * Math and numeric concepts - Use with limited understanding of, User needs: * Perceivable > content, * Perceivable > controls Units of: * Component, * View. Test types of: * Objective, * Condition. There didn’t seem to be any point in separating an evaluation by functional need. In this case, the sub-guidelines were based on trying to make granular evaluations for the units, test types, and user-need, e.g: * Has alt text (component, objective, perceivable content) * Conveys appropriate meaning (component, condition, perceivable content) * Provides descriptive identification (component, condition, perceivable control), could be combined with a guideline on having accnames for controls. * Conveys complex non-text content, e.g. longer description for infographics (view, condition, perceivable content) For some (e.g. language of the parts), there may not be any useful sub-guidelines, and you could just note in the 1st sub-guideline: no change. I hope that helps, -Alastair -- @alastc / www.nomensa.com<http://www.nomensa.com>
Received on Tuesday, 19 July 2022 18:02:15 UTC