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

Hi Alistair,

 

I appreciate your thoughts on this……

 

I happen to be one of those people who like to call errors under the major SC intent that it fails, which is often more than one SC. I would say that malformed is the 4.1.1 main issue with 4.1.2 and depending on the component we are talking about probably 1.3.1 as outcomes of a 4.1.1 error.

 

According to some 4.1.1 hardliners, who have seen it as limited to those 4 issues and on HTML only, they could call it a 4.1.2.

 

In my mind, 4.1.1 is about mistakes/unknowingly-invalid-use (other than custom design –which is clearly 4.1.2) in coding – whereas 4.1.2 is about designing specifically with user agents, AAPI and AT interoperability in mind when building custom components whether that is in HTML, scripting or what-have-you.

 

​​​​​My 2 cents….:-)

 

 

* katie *

 

Katie Haritos-Shea 
Senior Accessibility SME (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545

 

From: Alastair Campbell [mailto:acampbell@nomensa.com] 
Sent: Friday, January 29, 2016 9:52 AM
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Subject: Re: Question #2 on 4.1.1 Parsing - what it covers - ARIA? and How? - and SVG

 

Hi Katie,

 

Responding off list as I’m very late to the discussion – but wouldn’t 4.1.2 (Name/role/value) cover issues of malformed ARIA?

 

If the nesting is off and it doesn’t match an ARIA design pattern (I.e. cannot be programmatically determined), wouldn’t that catch errors of that nature?

 

I’m struggling to think of examples where something could be malformed but still be programmatically determined.

 

Cheers,

 

-Alastair

 

PS. Please feel free to reply on list if you think this is adding to the discussion.

 

 

From: Katie Haritos-Shea GMAIL 
Date: Wednesday, 13 January 2016 at 21:14

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

 

Christophe,

 

ARIA

Thanks. This is what I was getting at. I am trying to get folks to think about 4.1.1 Parsing in our current and near future web technology era.

 

You said “But if you use the same ARIA attribute twice on the same element, that would be covered by SC 4.1.1 and would be considered as a violation, unless you can find something in the ARIA spec that justifies duplicate attributes on the same element.”

 

​​​​​So we would agree that there are some aspects of 4.1.1 Parsing that would be applicable to ARIA.

 

It would be helpful to identify what those things might be for ARIA. Given the 4 items below, what do people think?:

This 4 things listed in 4.1.1 are:

1.       elements have complete start and end tags, 

2.       elements are nested according to their specifications, 

3.       elements do not contain duplicate attributes, ARIA YES?

4.       and any IDs are unique, 

except where the specifications allow these features.

In my mind #2 here is very applicable because the nesting of ARIA can wreck havoc on users of AT, but I would love to hear what others think……

 

SVG

Also, do others agree that all of 4.1.1 Parsing is applicable to SVG? I do, and as SVG continues to re-emerge and gain greater traction with improved WYSIWYG tools, and hopefully accessibility features, I think it can certainly have impacts on AT and their users.

 

 

* katie *

 

Katie Haritos-Shea 
Senior Accessibility SME (WCAG/Section 508/ADA/AODA)

 

Cell: 703-371-5545 |  <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545