report todos

[scottaohara]

Add tests and results for

• img alt=sometext
• img alt=""
• img w/out alt
• td within table / treegrid / grid (tests need publishing)
• td within table[role=presentation]
• tr within table / treegrid / grid (tests need publishing)
• tr within table[role=presentation]
• th within table / treegrid / grid (tests need publishing)
• th within table[role=presentation]
• Element that is a candidate for constraint validation but that does not satisfy its constraints
• tests for kinds of content / descendant restrictions (related to define nesting conformance requirements for roles when used in HTML #54)

[scottaohara]

• file issue with html validator for image results
• file issue with html validator for tr, td, th (after tests published)
• file issue with ibm for image results
• file issue with ibm for tr, td, th (after tests published)

[stevefaulkner]

@scottaohara img with some text does not allow role=radio, deliberate omission? If not will add and reup test

[scottaohara]

Probably an oversight when we looked at tightening them up. Don’t think it makes much sense in practice but since we allow other similar roles, yeh. Add it @stevefaulkner

[LJWatson]

I'm chasing outstanding reviews in #273. If we have not heard from the relevant groups by the start of next week, I'll go ahead an open a CFC with WebApps to transition this to CR.

We typically allow one week for WG CFC, which will put us safely on the other side of the AC meeting publishing moratorium (23 to 29 April).

At that point we'll officially request transition, so the report should have at least two documented implementations for each feature, and the features where the implementation experience is TBC should be marked as "at risk" (so if we have not documented implementations by the time we want to move out of CR, we can do so without returning to WD first).

[scottaohara]

with PR #322, the todos are now complete