HTML Checking for Large Sites
Rocket Validator automatically scans your sites for accessibility issues using the W3C Validator,
hosted on our own servers and integrated into our web crawler.
Bad value “X” for attribute “accept” on element “input”: Expected a token character or “/” but saw “,” instead.
The accept attribute may be specified to provide browsers with a hint of what file types will be accepted on an <input> element. It expects a comma-separated list of allowed file types. Refer to the list of media types to check the accepted tokens. In this example, the first line is invalid while the second is valid:
<input name='file' type='file' accept='doc, docx, pdf' />
<input name='file' type='file' accept='text/doc, text/docx, application/pdf' />Related W3C validator issues
- Attribute “maxlength” is only allowed when the input type is “email”, “password”, “search”, “tel”, “text”, or “url”.
- Attribute “pattern” is only allowed when the input type is “email”, “password”, “search”, “tel”, “text”, or “url”.
- Bad value “street-address” for attribute “autocomplete” on element “input”: The autofill field name “street-address” is not allowed in this context.
- Bad value “tel-national” for attribute “autocomplete” on element “input”: The autofill field name “tel-national” is not allowed in this context.
- Bad value “X” for attribute “href” on element “a”: Illegal character in path segment: space is not allowed.
- Bad value “X” for attribute “href” on element “a”: Illegal character in query: space is not allowed.
- Bad value “X” for attribute “src” on element “img”: Illegal character in path segment: space is not allowed.
- Bad value “X” for attribute “src” on element “img”: Illegal character in scheme data: space is not allowed.
- Bad value “zip” for attribute “type” on element “input”.
- Element name “X” cannot be represented as XML 1.0.
- Internal encoding declaration “windows-1251” disagrees with the actual encoding of the document (“utf-8”).
- Text run is not in Unicode Normalization Form C.