WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Can HTML tagged content conform to WCAG 2.0 without <body>, etc?

for

From: Jonathan Avila
Date: Apr 21, 2015 11:39AM

[Steve wrote]

> the first error is a failure of 4.1.1 Parsing <http://www.w3.org/TR/WCAG20/#ensure-compat-parses>;



Does SC 4..1.1 really require a doctype be defined?



SC 4.1.1 states

4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)



Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.



Can you explain which part of SC 4.1.1 is found in violation? My guess is that you are saying without a doctype you can't determine proper tag starting and ending requirements and nesting requirements, etc., is that correct?



Jonathan



--

Jonathan Avila

Chief Accessibility Officer

SSB BART Group

<EMAIL REMOVED>



703-637-8957 (o)

Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter





-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Steve Faulkner
Sent: Tuesday, April 21, 2015 1:14 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Can HTML tagged content conform to WCAG 2.0 without <body>, etc?



<p><p>



throws 2 errors when tested using http://validator.w3.org/nu/



*Error*: Start tag seen without seeing a doctype first. Expected e.g. <!DOCTYPE

html>.

*Error*: Element head is missing a required instance of child element title.



the first error is a failure of 4.1.1 Parsing <http://www.w3.org/TR/WCAG20/#ensure-compat-parses>;



Also note as the document does not define a default language its a failure of 3.1.1 language of page <http://www.w3.org/TR/WCAG20/#meaning-doc-lang-id>;







--



Regards



SteveF

HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;



On 21 April 2015 at 18:03, Duff Johnson < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:



> > It isn't best practice for HTML development but I'd say that while

> > the

> file meets most success criteria it would fail 2.4.2 (Page titled) as

> the HTML element needed to provide a title is absent.

>

> I'm not sure how missing a <title> affects the accessibility of the

> file per se (it seems more like a usability issue rather than a Level

> A accessibility concern), but I certainly accept that it's a violation

> of

> 2.4.2 as written - thanks.

>

> > HTML5 allows the body element to be omitted in some circumstances,

> > and

> this file would be one such example.

>

> What about <doctype>? It's missing as well…

>

> Essentially what I'm getting at is: what's the minimum required for

> (notionally) HTML content in order to meet WCAG 2.0?

>

> Thanks,

>

> Duff.

>
> > archives at http://webaim.org/discussion/archives

> >