WebDevStudios
Accessibility checklist review
While this issue might serve as a reminder, it's not really a sufficiently detailed Issue such that it can be agreed to be addressed.
Consider a more pragmatic approach, like testing if all controls can be access with keyboard only. Either they all can, or at least one can't, and an Issue can be opened for that. Likewise, check if screen reader users can understand the UI and navigate correctly (turn your monitor off, or stick some paper over it) - again, either it's clear, or it's not, and an Issue can be opened if needed.
The accessibility checklist represents the technicals, like the use of semantic headings and alt attributes, but an acceptance / user test approach will highlight the issues that need to be addressed, which may then be at least partly solved with the technical items on the checklist.
