Closed iris-i closed 8 years ago
Hmm — thanks for that d.o link. Accessibility is one of the USWDS's key features (and legally required), so we definitely need to prioritize accessibility concerns.
The W3's notes on ARIA validation suggest using the W3C Nu Markup Checker. They further suggest:
It is recommended that if you encounter a result that conflicts with the ARIA conformance requirements in the ARIA specification or the HTML specification, please raise an issue.
Using templates and preprocess functions seems more straightforward, reliable and performant than architecting jQuery around the fact that many HTML validators are currently outdated when it comes to ARIA attributes.
What do you think of working with templates, etc., and following the approach above for validation?
I agree. If we have to choose between getting the theme validated/accessible, accessibility should be our top priority. We can open up an issue with the W3 if we encounter any problems. Also the linked d.o page is ~ 4 years old, a lot could have changed in this time.
I'll go ahead and close this issue, we will work with templates and preprocess functions to get Landmark roles in where necessary.
As a user with disabilities, I would like to access UI components and content on the webpage easily. This task is for tracking the accessibility of components, by making sure that they include Landmark roles for better navigation of content pages.
Proposed implementation We can add this using JQuery instead of in the templates. This will make it easier to add new classes & components and also make sure that the page passes validation https://www.drupal.org/node/471444