Re: Deprecating 4.1.1 - mapping

HI Sailesh,

I’ve incorporated some of that, a few points that I didn’t include:

> Reference: Tool authored by S. Faulkner that  filters all 4.1.1 issues
> into accessibility / non-accessibility issues.

Given the thread that kicked this off (2525<https://github.com/w3c/wcag/issues/2525>), I think that the tool includes things that weren’t intended to be caught by 4.1.1, such as content-model nesting. Assuming we go down the path of removing 4.1.1, the tool wouldn’t figure in the mapping document. It could be a linked-resource that’s helpful for testing.


> I am a strong advocate of G134 - validating Web pages before doing
> accessibility testing. It reduces the accessibility testing work if
> code is valid.

Validation is a useful tool and it can show areas for investigation. However, if you consider both testing and development work, there’s a lot of development work needed for full validation which does not improve accessibility outcomes. Particularly in some modern frameworks where the code can be pretty abstracted.


> It is an SC 1.3.1 issue, not 4.1.2 as info-relationships are wrongly conveyed.

I’ve added that it could be both/either. If the wrong name is conveyed it would be 4.1.2, if the wrong relationship is conveyed it would be 1.3.1, or both.


For:
> That's where SC 4.1.1 kicks in- to make content robust i.e.
> content behaves reliably across user agents / platforms.

And:
> Issue 10: Lack of closing tag.
> Sailesh: It causes accessibility issues quite often. Screen readers
> read invisible code / markup which makes content completely
> incomprehensible. I have seen it in  mobile Web too.

Error handling for missing end tags is well defined and browsers now seem to deal with this well. Or rather, they deal with it consistently so anything that doesn’t work, does not work for everyone.

Do you have any examples of where a screenreader would read out invisible code due to a missing closing tag?

I found that for other reasons (e.g. CSS), but not due to a missing end tag.

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<http://www.nomensa.com>