Accessibility Team Meeting Notes: June 19, 2020

These are the weekly notes for the AccessibilityAccessibility 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). ( Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

New Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. 🎉

After accepting nominations, I’m happy to inform that @ryokuhi has been selected as our new Team Rep. Together, we’ll be sharing Team Rep responsibilities and helping the Accessibility team make WordPress better for everyone.

Discussion of Remove ‘Error:’ prefixes from error notices as they’re redundant

We discussed Remove ‘Error:’ prefixes from error notices as they’re redundant, a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket that is proposing remove type prefixes to error messages in wp-admin.

There are various opinions around whether type prefixes, such as ‘Error’, ‘Warning’, ‘Success’, etc. are needed, or are simply redundant on wp-admin messages and notifications.

The discussion was very constructive and informative, I encourage those interested to read it in full.

We agreed that uniformity was important and that this topic is closely related to the work happening on the WP Notify feature. For now, we decided to revert the removal of the ‘Error’ prefix and gather more feedback.