Re: Question #2 on 4.1.1 Parsing - what it covers - ARIA? and How? - and SVG

I think it is cases like this that highlight the issue:

<div rol=“navigation"> (attribute mis-spelling)
Or
<div role=“navigaton”> (value mis-spelling)

I’m not even sure the second would be brought up as an HTML validation error as HTML probably doesn’t have a pre-defined set of values, those are defined in ARIA.

A coding error, but not ones covered by 4.1.1. I think the effect would found be under 4.1.2, but that doesn’t seem quite right.

-Alastair



From: Jonathan Avila <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>>
Date: Monday, 1 February 2016 at 13:25
To: Steve Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>>
Cc: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>>, Katie Haritos-Shea GMAIL <ryladog@gmail.com<mailto:ryladog@gmail.com>>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: RE: Question #2 on 4.1.1 Parsing - what it covers - ARIA? and How? - and SVG


Ø  I would like to agree with you Jon, but the criteria does not support this as written.

Understood on the duplicate attributes and missing quotes – but I do wonder if incorrect ARIA roles could potentially be seen as causing the elements to not be nested according to the specification.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
703.637.8957 (o)
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: Monday, February 01, 2016 8:20 AM
To: Jonathan Avila
Cc: Alastair Campbell; David MacDonald; Katie Haritos-Shea GMAIL; GLWAI Guidelines WG org
Subject: Re: Question #2 on 4.1.1 Parsing - what it covers - ARIA? and How? - and SVG


On 1 February 2016 at 13:05, Jonathan Avila <jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>> wrote:
I absolutely agree, a misspelled ARIA attribute or value would be a violation under SC 4.1.1 in my opinion.

I would like to agree with you Jon, but the criteria does not support this as written.

--

Regards

SteveF
Current Standards Work @W3C<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>