Changes between Version 2 and Version 3 of Ticket #17611, comment 60
- Timestamp:
- 06/19/2011 12:43:50 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17611, comment 60
v2 v3 4 4 > I think that we are taking this ticket away from the subject and going back instead of forward. WordPress already stepped into HTML5 and this big improvement must not be degraded in any way, especially going back to HTML4, completely or just partially. ... 5 5 6 Who said anything about reverting the DOCTYPE? Using the HTML5 DOCTYPE and providing accessibility are not mutually exclusive. 6 Who said anything about reverting the DOCTYPE? 7 8 *** Using the HTML5 DOCTYPE and providing accessibility are not mutually exclusive. *** 7 9 8 10 All of the W3C documents about accessibility constantly advise using proven techniques until user agents catch up when new technology is introduced. Since few browsers and NO screen readers support the section / outline technology, traditional heading structures should be preferred. 9 11 10 My interest in this ticket arose from Jane Well 'srepeated call for accessibility experts. In both of the recent releases she has made the call to improve WP accessibility. Most recently here: http://make.wordpress.org/accessibility/2011/05/06/hello-accessibility-experts-we-were-re/ and here: http://make.wordpress.org/accessibility/2011/05/06/if-anyone-would-like-to-take-a-stroll-th/12 My interest in this ticket arose from Jane Wells' repeated call for accessibility experts. In both of the recent releases she has made the call to improve WP accessibility. Most recently here: http://make.wordpress.org/accessibility/2011/05/06/hello-accessibility-experts-we-were-re/ and here: http://make.wordpress.org/accessibility/2011/05/06/if-anyone-would-like-to-take-a-stroll-th/ 11 13 12 14 Yet, it seems that advancing to the latest and greatest technology is more important than improving accessibility. I think I'm done here.