Re: [techs] Test 37, 38, 39, 40 and 41

I'm suggesting we keep the tests at a fine level of granularity. For example these tests for header element could all be rolled into one but that might cause problems later. The test for H1 may change (perhaps we decide there should only be one H1 in the doc) and then we would have to modify the group test and create a new test for H1. If they are separate then it's easier to modify only the parts that change. My computer programmer instincts tell me to do it this way.

> I think we should have a single checklist item

> that says "there is alt text and it is not empty

> or filled with placeholder text."



I agree. In the checklist or techniques documents they should be combined so they are more human readable. If the user really wants to get down to the nitty gritty they can look at the test cases. With these 3 different views (techniques, checklists, test cases) the WCAG will be *very* clearly defined. Well, at least for HTML.



> Suggest we have a description in words - 

> followed by a section called "algorithm' 

> that details the test step by step.                     

>

I think we can do this now with our current materials. If we take text from the techniques, checklist and test case then mix them together we get something like:



Use the alt attribute of the img element to provide a text alternative for images. (from techs)

Each image must have alt text that is not empty of filled with placeholder text. (from checklist)

Check img element for the presence of an alt attribute. (from test case)

Compare the alt attribute value to the list of placeholder values (from test case).



Is that close to what you're suggesting?



Chris