Page content: parsing errors in Discover your path
Many parsing errors in: Discover your path page. Departments and centers page. and Programs page https://artsandsciences.osu.edu/discover-your-path?field_ap_program_target_id=All&field_ap_interest_target_id%5B58%5D=58&field_ap_interest_target_id%5B63%5D=63&field_ap_interest_target_id%5B93%5D=93&field_ap_interest_target_id%5B101%5D=101 4.1.1 Parsing A Moderate
Specifically focus on the html nesting errors. (
s with illegal stuff)Tested with the NU HTML checker bookmarklet Comments:
- I'm not sure what this one means. We can meet to discuss when you get back (Brian Canini - Sep 25, 2023)
- Validating the html of page turns up some things. Some of these I'm pretty sure you've addressed already in the dev sites. Lemme know if you want to work on these together.
This link should show all the issues. Some will not cause an accessibility problem but some can. Therefore focus on the bolded ones.
The bold items should be looked into. For the fieldset
one I think you can just change to a <div>
. I think there is an existing ticket for that.
Errors (588)
- The element a must not appear as a descendant of an element with the attribute role=button.
- Duplicate ID edit-actions.
- Bad value for attribute href on element a: Illegal character in query: [ is not allowed. (5)
- Element fieldset not allowed as child of element span in this context. (Suppressing further errors from this subtree.) (193)
- End tag a violates nesting rules. (193)
- Stray end tag span. (193)
- End tag footer seen, but there were open elements.
- Unclosed element div.
Warnings (5)
- The banner role is unnecessary for element header.
- The first occurrence of ID edit-actions was here.
- Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections, or else use a div element instead for any cases where no heading is needed. (3) (Jeff Borisch - Sep 27, 2023)