Ø this is fine (i think), but why one would need to do so is unclear. I’m thinking of situations where we have to fix things after the fact – for example with JavaScript injection and changing the HTML elements might introduce visual changes to a site that are harder to detect. Jonathan -- Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com> Phone 703.637.8957 Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP> From: Steve Faulkner [mailto:faulkner.steve@gmail.com] Sent: Friday, August 21, 2015 2:14 PM To: Jonathan Avila Cc: GLWAI Guidelines WG org; Michael[tm] Smith Subject: Re: Thoughts on roles and conformance to SC 4.1.1 Parsing On 21 August 2015 at 20:08, Jonathan Avila <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>> wrote: <div role=”list”> <p role=”listitem”>Apples</p> <p role=”listitem”>Oranges</p> <p role=”listitem”>Bananas</p> </div> this is fine (i think), but why one would need to do so is unclear. -- Regards SteveF Current Standards Work @W3C<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
Received on Friday, 21 August 2015 18:24:56 UTC