- From: <josh@interaccess.ie>
- Date: Tue, 10 May 2016 14:04:22 +0000
- To: "Alastair Campbell" <acampbell@nomensa.com>
- Cc: WCAG <w3c-wai-gl@w3.org>
- Message-Id: <em4f54336d-abe0-4436-bba3-00459e182bd0@josh_machine>
Josh wrote: > Again, to me it seems these items can be dovetailed. > >I think you’d be pulling at the thread of the “POUR” structure, one is structure based the other is content based. If you combine or categorise >those together, wouldn't you be re-structuring to a more functionality based approach? E.g. Put all the forms stuff together? Interesting. Maybe. ------ Original Message ------ From: "Alastair Campbell" <acampbell@nomensa.com> To: "josh@interaccess.ie" <josh@interaccess.ie> Cc: "WCAG" <w3c-wai-gl@w3.org> Sent: 10/05/2016 14:49:36 Subject: Re: Re[2]: Difference between SC 1.3.1 and SC 2.4.6? >Patrick wrote: >>1.3.1 is about making sure relationships are not simply conveyed >>visually, through styling, so the structure/relationship can be >>programmatically determined by, say, AT, and presented to users in >>different ways beyond just visual style. >> >>2.4.6 on the other hand is about making sure that users (sighted, >>non-sighted, etc) can actually understand content properly. It's not >>about how these headings/labels are coded (like "use proper <h1>-<h6> >>", as that falls under 1.3.1). >Josh wrote: > > Again, to me it seems these items can be dovetailed. > >I think you’d be pulling at the thread of the “POUR” structure, one is >structure based the other is content based. If you combine or >categorise those together, wouldn't you be re-structuring to a more >functionality based approach? E.g. Put all the forms stuff together? > >-Alastair
Received on Tuesday, 10 May 2016 14:02:47 UTC