Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

hanselman.com

Post reply on HN
Print view View original

101–102 of 102 posts

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#101

Post by sodosopa »

laken wrote: post #100
sodosopa wrote: post #99

Earlier quoted context omitted.

Thanks for the response. I think most web devs have always treated accessibility as "low priority". It's not top of mind until it becomes a part of your daily job. I've been there. How close is it to 2.0 A, currently?

It's tricky to even tell now, unfortunately. These are the issues that are remaining that we (the a11y team) want fixed prior to merge: https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is... When these issues were added to the merge proposal, they were what were left for 2.0 level A. But accessibility regressions have gotten introduced many times now while other developers are working on things from other me…

from earlier today "WordPress aims to make the WordPress Admin and bundled themes fully WCAG 2.0 AA compliant where possible."

https://wordpress.org/about/accessibility/

The jump from A to AA is difficult and to put the statement of AA out there, is bold (and probably naive).

Re: The Whole of WordPress Compiled to .NET Core and a NuGet Package with PeachPie

#102

Post by laken »

sodosopa wrote: post #101
laken wrote: post #100

Earlier quoted context omitted.

It's tricky to even tell now, unfortunately. These are the issues that are remaining that we (the a11y team) want fixed prior to merge: https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is... When these issues were added to the merge proposal, they were what were left for 2.0 level A. But accessibility regressions have gotten introduced many times now while other developers are working on things from other me…

from earlier today "WordPress aims to make the WordPress Admin and bundled themes fully WCAG 2.0 AA compliant where possible." https://wordpress.org/about/accessibility/ The jump from A to AA is difficult and to put the statement of AA out there, is bold (and probably naive).

Yes, that’s our new accessibility page!

I’ve heard the argument by many though that if someone needs WCAG AA, that they can just use the classic editor (which will be supported via a plugin maintained by wp.org). Will be interesting to see how it all plays out

Post reply on HN