Re: Question on 4.1.1 Parsing - what it covers

Hi sailesh,

Apologies have been distracted. I did see your email and have put the
bookmarklet on GitHub

https://twitter.com/stevefaulkner/status/685507894838718466

Note the bookmarklet is constrained by the output of the validator, in the
case of unknown attributes it is difficult to filter, as there is no way to
differentiate between unknown and malformed.

I also recently wrote an article about what I think the parsing criteria
requires:
https://www.paciellogroup.com/blog/2015/11/wcag-2-0-parsing-criterion-is-a-pita/
On Tuesday, 12 January 2016, Sailesh Panchang <sailesh.panchang@deque.com>
wrote:

> About parsing only bookmarklet:
> I see it also flags errors like:
> Error: Attribute ng-controller not allowed on element  body  at this point.
> Error: Attribute ng-class not allowed on element  header  at this point.
> Error: Attribute ng-switch-when not allowed on element  span  at this
> point.
> Error: Attribute ng-href not allowed on element  a  at this point.
>
> I do not believe  flagging invalid attributes is within the scope of SC
> 4.1.1.
> I asked  Steve F about this  and hopefully will hear back.
> Thanks,
> Sailesh Panchang
>
>
> On 1/12/16, John Foliot <john.foliot@deque.com <javascript:;>> wrote:
> > +1 to Christophe.
> >
> > (Although I also agree with Jason that this meets the technical
> requirement
> > defined by 4.1.1, but that there may remain some User Agent issues not
> > captured or addressed)
> >
> >
> >
> > JF
> >
> >
> >
> >
> >
> > From: Christophe Strobbe [mailto:strobbe@hdm-stuttgart.de <javascript:;>
> ]
> > Sent: Tuesday, January 12, 2016 11:50 AM
> > To: w3c-wai-gl@w3.org <javascript:;>
> > Subject: Re: Question on 4.1.1 Parsing - what it covers
> >
> >
> >
> > Hi Katie,
> >
> > As far as I understand, SC 4.1.1 covers only the four parsing errors that
> > are explicitly mentioned, and no other ones.
> >
> > Best regards,
> >
> > Christophe
> >
> > On 12/01/2016 18:28, Katie Haritos-Shea GMAIL wrote:
> >
> > Folks,
> >
> >
> >
> > Do we as the Working Group consider 4.1.1 Parsing to include ONLY the 4
> > specific examples identified in the Success Criteria, or, do we believe
> that
> > 4.1.1 Parsing to includes those 4 examples plus other things where
> parsing
> > failures might affect AT?  (I know that a doctype declaration is NOT a
> > parsing failure).
> >
> >
> >
> > ​​​​​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,
> >
> > 4.      and any IDs are unique,
> >
> > except where the specifications allow these features.
> >
> >
> >
> > I have been at organizations where this is broader than those 4 items,
> and
> > at places where those 4 sre strickly adhered to, and no other parsing
> issue
> > are identified as failing 4.1.1.
> >
> >
> >
> > Steve Faulkners tool and blog
> > (
> https://www.paciellogroup.com/blog/2015/11/wcag-2-0-parsing-criterion-is-a-pita/
> )
> > seem to support the 4 items only.
> >
> >
> >
> >
> >
> > * katie *
> >
> >
> >
> > Katie Haritos-Shea
> > Senior Accessibility SME (WCAG/Section 508/ADA/AODA)
> >
> >
> >
> > Cell: 703-371-5545 | ryladog@gmail.com <javascript:;> <mailto:
> ryladog@gmail.com <javascript:;>>  | Oakton,
> > VA |  <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile |
> > Office: 703-371-5545
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Christophe Strobbe
> > Akademischer Mitarbeiter
> > Responsive Media Experience Research Group (REMEX)
> > Hochschule der Medien
> > Nobelstraße 10
> > 70569 Stuttgart
> > Tel. +49 711 8923 2749
> >
> > “It is possible to make a living making free software for freedom
> > instead of closed-source proprietary malware for cops.”
> > Jacob Appelbaum,
> > <
> http://dissenter.firedoglake.com/2012/12/28/jacob-appelbaum-on-resisting-the-surveillance-state/
> >
> > <
> http://dissenter.firedoglake.com/2012/12/28/jacob-appelbaum-on-resisting-the-surveillance-state/
> >
> >
>
>

-- 
--

Regards

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