There must be a <!DOCTYPE> tag at the top of the page (if 'auto-detecting' then a best-fit <!DOCTYPE> will be used)
A <!DOCTYPE> tag should be placed before any other HTML tag or non-whitespace characters on the page. Sometimes the <!DOCTYPE> tag is in the wrong place, but is usually missing altogether in these cases. A correct <!DOCTYPE> tag is needed to ensure that the browser interprets the HTML correctly. See Recognised Doctypes.
E609
HTML Error
This tag or content is not allowed here. One of the following was expected: LIST OF VALID TYPES/TAGS
There are strict rules as to what tags may be nested within others, as well as the order and number of tags allowed. If this error is preceded by an E604 error (missing end tag) then correcting the earlier E604 error may correct this one. Otherwise either remove the item marked or nest it within one of the types or tags listed. LINK TO STANDARD.
E622
HTML Error
The ATTRIBUTE NAME attribute does not have a valid value: LIST OF VALID VALUES
The HTML specification being tested against defines certain valid values for each attribute. Usually a list of valid values will be displayed when you see this message. Note that many values must be in lower case in XHTML, including the 'x' in numeric hex entity references. Also note that what values are allowed varies from standard to standard.
E910
WCAG Error
1.4.4
[WCAG21 1.4.4 (AA)] Use relative rather than absolute units
Using relative units helps the page to be rendered correctly at different resolutions and allows people with sight difficulties to 'zoom in' to pages to read them. See Understanding 1.4.4.
W869
WCAG Warning
2.4.1
[WCAG21 2.4.1 (A)] Use heading elements to convey structure
Many assistive technologies provide navigation using headings, including skipping navigational links. If your document has any structure you should use heading markup to convey the structure of the content. Even a single header will make it easier for users. See WCAG 2.1 HTML Technique H69.
TV20220929164434.zip
Hi All
PFA the accessibility audit report that is run on below URL. This report will pinpoint in which line of code the error is observed. https://demo.pla.health/leaflet.html?gtin=02113100000011&batch=JUN2303&expiry=31%20-%20Dec%20-%202024
Along with accessibility errors, I have run the audit for HTML errors as well, as you might need the page to be W3C Compliant as well.
There are 3 HTML Error and 1 Accessibility Error and 1 Accessibility Warning. The test is run against WCAG 2.1AAA guidelines.
These errors are consistently observed across the pages https://demo.pla.health/ https://demo.pla.health/scan.html
Here is the summary of the audit report. Please feel free to reach out to me or Margaret if in case you have any questions on this.
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">