Adam Zieliński

This could be a Bun alternative, if Bun doesn't pan out for any reason (so far it seems great) https://bellard.org/quickjs/

@bgrgicak I wonder why that works with a "regular" WordPress and not with Playground. Could it be that Playground only resolves the URLs ending with `/` and `.php` as PHP...

Aha, the big problem here is Apache has immediate access to the filesystem and knows whether a static file exists or not. Playground doesn't. A chunk of static files is...

> @adamziel I planned to exclude static files in /wp- folders from being executed like PHP files. This would resolve the issue without a list. @bgrgicak How do you know...

@bgrgicak Makes sense as a stop-gap solution, as long as it wouldn't start dispatching 404 `/wp-content` requests to PHP.

@jonathanbossenger All the reported issues are now fixed. For a better read we'd need to test using actual assistive technologies like screen readers – what's your opinion on this @jonathanbossenger?...

@jonathanbossenger would you post a screenshot of these warnings? Here's what I see:

For context – we need to check whether Axe DevTools with "Best Practices" on report any issues, and then either: * Close this issue if there are no more problems...

@ironnysh fixed the last accessibility issues in https://github.com/WordPress/wordpress-playground/pull/1246, yay! Let's close this issue and use https://github.com/WordPress/wordpress-playground/issues/1248 to make sure no new issues get merged in the future.

 I think the changes are gone.