Accessibility Team Meeting Notes: May 14, 2021

About Us

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). (https://en.wikipedia.org/wiki/Accessibility) Team shares their expertise to improve the accessibility of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and resources.

WordPress targets WCAG 2.2 at level AA as the standard for development.

Learn More

Ask general questions during the Team Office Hours every Wednesday at 14:00 UTC in the accessibility channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

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). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.

Accessibility discussion around the GutenbergGutenberg 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/ GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue Post Title Block: add typography formatting options

The focus of this discussion is around whether it’s a good idea to allow underlining of text that is not a link as underline can strongly indicate that the text is a clickable link and may lead to confusion if non-links are underlined.

It was decided that it would be better to remove the underline formatting option from the pull request for now and maybe revisit implementation later if there is a greater need.

How to move forward with Proposal: new workflow keyword to exclude tickets until review is needed

At this point, the proposal was posted a couple weeks ago. The best way forward is likely to choose a keyword name. Another suggestion was brought up to just mark tickets as Future Release milestone. A list of keywords that the team is considering can be found in a comment on the original post: comment posted here.

Updates from the team’s working groups

Due to a time shortage, this agenda item was skipped for today.

Open floor

FSE Updates

Both are part of Full Site Editing Go/No Go: Next steps which makes these crucial for Accessibility team feedback.

Documentation

Accessibility Standards documentation updated via the GitHub PR: Update accessibility.md.

Media

The infinite scroll removal has been committed for 5.8. If you notice any issues during testing, please report them via Core TRAC.

Next Bug Scrub/Meeting (Friday, May 21, 2021)

Because of concurring tasks, @ryokuhi and @alexstine won’t be able to facilitate the Accessibility bug scrub or meeting on May 21. @chaion07 has offered to lead the bug scrub and @joedolson has offered to lead the meeting.

#meeting-notes