Transcript meeting in Slack
The meeting was somewhat impromptu as there was no agenda published. @lonelyvegan ran the meeting but it pretty much just covered Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ and his work on getting an audit done on Gutenberg.
Gutenberg Accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Audit
@lonelyvegan expressed his interest in doing an accessibility audit on Gutenberg, comparing the Classic Editor to Gutenberg. A focus of the audits/tests would be higher-level issues with the editing experience, regressions in functionality contained in the Classic Editor, and issues with frequently-used blocks. More info forthcoming as discussions with potential auditors happen and procurement is sorted out.
@lonelyvegan expressed the opinion that the Classic Editor plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party is the worst-case fallback for Gutenberg accessibility. But based on conversations it is unlikely Accessibility issues will delay release.