The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
…2:0:0:-1:0:0">29 Fev 2020 // 16:00<br>HEARTH FESTIVAL - TARDE POÉTICO-MUSICAL<…
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
…:56:2:0:0:-1:0:0">29 Fev 2020 // 16:00<br>HEARTH FESTIVAL - TARDE POÉTICO-MUSI…
…:2:0:0:-1:0:0">09 mar 2020 // 17:30<BR>APRESENTAÇÃO DO LIVRO "IMAGENS IMAGINAD…
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:
… // 17:30<BR>APRESENTAÇÃO DO LIVRO "IMAGENS IMAGINADAS" DE PEDRO MEXIA</a></h1>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
…:55:2:0:0:-1:0:0">09 mar 2020 // 17:30<BR>APRESENTAÇÃO DO LIVRO "IMAGENS IMAGI…