The AccessibilityAccessibilityAccessibility (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) Team shares accessibility expertise across the project to improve the accessibility of WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and resources.
You can also ask questions during Accessibility Team Office Hours every Wednesday at 14:00 UTC in the accessibility channel in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
Discuss and validate GutenbergGutenbergThe 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/accessibilityAccessibilityAccessibility (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) feedback before publishing
Open floor
Bug scrub weekday/time
As the Accessibility meeting weekday/time has moved to every Fridays, 15:00 UTC, bug scrub meeting also moved to Friday, 1 hour before the meeting.
Accessibility bug scrub: Friday, 14:00 UTC Accessibility team meeting: Friday, 15:00 UTC
Please note that both will move after Day Saving Time end in the US.
Discuss and validate Gutenberg accessibility feedback before publishing
The aim of this document is to address in an objective and professional way the accessibility issues encountered with the BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor. The focus is set on the ability to author, edit, and publish posts, which is the primary purpose of WordPress.
The team tried to make this communication accessible to users with no or little accessibility expertise. If you have any question about this document, please comment it.
Open floor
The team discussed some best practices for a better accessibility in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. conversations:
Do not use threads as they are not accessible
Avoid large blocks of text
Give some time between messages
Consider people have different typing speed
Use formal beginning/end markers
Emojis: are they accessible?
Persons with accessibility needs are encouraged to give feedback and ask for improvements they would like to get.
