- From: Daniel Montalvo <dmontalvo@w3.org>
- Date: Wed, 9 Jun 2021 10:59:31 +0200
- To: "'David Sloan'" <dsloan@tpgi.com>
- Cc: <public-wai-curricula@w3.org>
Hey Dave, As per your comment about distinguishing functional and non-functional requirements. Currently I have capture this as follows. [[ Topic: Establishing Requirements Present the W3C accessibility standards. Discuss policies that apply in the students' region (if any). Explain functional and non-functional requirements related to people with disabilities. Learning Outcomes for Topic Students should be able to: * identify different non-functional accessibility requirements, for example those included in WCAG and in applicable accessibility policies * identify different functional requirements that relate to people with disabilities, for example: * appropriate contrast ratios * availability of content and functionality in different screen sizes and configurations * keyboard compatibility * compatibility with assistive technologies and adaptive strategies ]] For context, see https://deploy-preview-347--wai-curricula.netlify.app/curricula/designer-modules/understanding-and-involving-users/#topic-establish ing-requirements But I am a bit hesitant as to how this is going to be understood. On the one hand we could consider WCAG as non-functional (it does not tell you how to do things) but on the other hand WCAG does have specific requirements such as contrast ratios, descriptive labels and headings, that could be understood as functional. Could you please expand on this a bit more? How would you better capture the difference between functional and non-functional requirements for accessibility? Best. -- Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI
Received on Wednesday, 9 June 2021 08:59:58 UTC