Developer priorities by diagnostic Ashford
Developer priorities allow you to review the important aspects of your assessment from a technical view point. Typically, these priorities relate to changes that cannot be addressed by content editors easily.
Assessment completed on 12 Jul 2017 at 06:24 looking at http://www.ashford.gov.uk/.
125 pages
5,075 pages in 106 documents
12 documents
None found
3 documents
Five slowest URLs by time to first byte
Top five accessibility issues
Occurrences | What We Checked | |
---|---|---|
396 | F17 : Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML | |
266 | F77 : Failure of Success Criterion 4.1.1 due to duplicate values of type ID | |
266 | H93 : Ensuring that id attributes are unique on a Web page | |
180 | H30 : Providing link text that describes the purpose of a link for anchor elements | |
132 | PDF1 : Applying text alternatives to images with the Alt entry in PDF documents |
Top five code quality issues
Occurrences | What We Checked | |
---|---|---|
393 | Invalid attribute name | |
309 | Invalid attribute value | |
180 | A "301 Moved Permanently" response was received | |
25 | Fragment identifier not found | |
24 | Image file size or dimensions do not match |