Title: Accessibility Ready? Last modified: April 3, 2019 --- # Accessibility Ready? * Resolved [Lukasz](https://wordpress.org/support/users/wpfed/) * (@wpfed) * [7 years, 1 month ago](https://wordpress.org/support/topic/accessibility-ready-4/) * Hi, * I took a quick look, I see aria-references and other visual clues that this is a accessible theme, but I don’t see accessible ready tag, how would you rate this theme accessibility wise? * Great theme by the way. * Thanks. Viewing 1 replies (of 1 total) * Theme Author [David Vongries](https://wordpress.org/support/users/davidvongries/) * (@davidvongries) * [7 years, 1 month ago](https://wordpress.org/support/topic/accessibility-ready-4/#post-11388411) * Hi [@wpfed](https://wordpress.org/support/users/wpfed/), * thanks for your kind words! 🙂 * With the release of 2.0, Page Builder Framework is fully accessible 🙂 * We haven’t applied for the `accessibility-ready` tag yet because the requirements are quite strict & some of them are hard to meet, especially with backwards compatibility in mind. (see: [https://make.wordpress.org/themes/handbook/review/accessibility/required/](https://make.wordpress.org/themes/handbook/review/accessibility/required/)). * Let me go a little more into detail: * > Fails: Dropdown navigation menus are hidden using display:none; and brought > into view on :hover * I don’t see what’s wrong with that and changing this on our end would require a bit of work + may break things in terms of backwards compatibility. * Also we feel like some requirements are outdated, for instance: * [https://make.wordpress.org/themes/handbook/review/accessibility/required/#aria-landmark-roles](https://make.wordpress.org/themes/handbook/review/accessibility/required/#aria-landmark-roles) * It’s not necessary/recommended to apply aria markup to HTML5 elements like `< header>`, `