Jb Audras 11:20 pm on March 27, 2020  

Accessibility Team meeting notes – March 27, 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). (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.

Feedback on the CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. audit being performed by the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-css team

Context: the Core CSS team proposed to launch a CSS audit of WP-Admin in the #core-css channel. They recently asked the design team for input on what they would like to see covered in the audit, and it would be great to also have some input from the accessibility team. They have a bunch of tickets to track everything audit-related:

  • Determine methodology recommendations for CSS audit – #49638
  • Create a report outline for CSS audit – #49637
  • Add visual regression testing to core – #49606

Everyone is welcome to comment on the above tickets.

@afercia shared some general considerations: while an admin CSS audit is extremely necessary, there’s also the risk to overdo and enter the “refactor for the sake of refactoring” territory. He would definitely recommend the css-team to start with baby steps and avoid bigger changes, at least at the beginning.
There are also some CSS properties that are a no-go. For example, all the ones that change the visual order e.g. flex order, flex-direction row-reverse, column-reverse and so on. Also simple things like list-style: none may significantly impact assistive technologies or the way some browsers expose information to assistive technologies.

@joedolson also wanted to ensure we are all on the same page concerning browsers support. @audrasjb answered WP-Admin doesn’t officially supports less than IE11 and @afercia added that it is safe to assume we can remove all CSS related to old IE and prepended with .ie7 – .ie8. See also this Trac ticket for reference.

5.4 post-mortem on Make/Core blog

The WordPress Accessibility team published their position concerning default fullscreen mode on the block editor.

As this change is going to land in WordPress 5.4 –it was announced during the last dev chat– @audrasjb pointed out that the content of the Accessibility Team’post could be used to write a 5.4 post-mortem, and he is going to coordinate with @francina to write this post on Make/Core. It will be a team effort to ensure that all the Accessibility Team viewpoints are captured. @ryokuhi is also available to help on this.

@mapk added he is also organizing some people from Automattic to help wrangle support forums for this releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. They will probably have some feedback there.

Accessibility team’s work kick-off for 5.5

The team defined the main projects to focus on for WordPress 5.5:

  • Accessible color schemes: Provide some accessible color schemes for WP-Admin. Lead: @joedolson. @ryokuhi also proposed to help on this project.
  • Alternative WP List Tables views: Propose an alternative way to display List Tables in WP-Admin – ticket #49715
  • “Howdy fly-out menu”: Refine/replace the upper-right WP-Admin fly-out menu.

There are also 29 other TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets milestoned for 5.5.

WP Accessibility Day update

Next meeting scheduled on Tuesday March 31, 2020 at 16:30 UTC.

Enrique Sánchez 9:59 pm on March 26, 2020
Tags:   

Accessibility Team Meeting Agenda: March 27, 2020

This is the proposed agenda for the weekly 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 on Friday, March 27, 2020, 16:00 UTC .

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday, March 27, 2020, 15:00 UTC .

This meeting is held in the #accessibility channel in the Making WordPress 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/. (requires registration).

#agenda

Jb Audras 9:39 am on March 24, 2020
Tags: ,   

WordPress Accessibility Team position on default full screen mode in the editor

During the last weekly meeting, the team discussed the recent change of default to the full-screen mode in the editor. There is a general concern about the usability and 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) implications this new default setting will have.

As a starting point, the WordPress Accessibility team is opposed to this change as it breaks some WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. success criteria:

  • Success criteria 3.2.3: Consistent navigation
    “The intent of this Success Criterion is to encourage the use of consistent presentation and layout for users who interact with repeated content within a set of Web pages and need to locate specific information or functionality more than once.”
  • Success criteria 3.2.4: Consistent identification
    “The intent of this Success Criterion is to ensure consistent identification of functional components that appear repeatedly within a set of Web pages. A strategy that people who use screen readers use when operating a Web site is to rely heavily on their familiarity with functions that may appear on different Web pages.”

The main issue is that the fullscreen mode (when it’s activated by default) removes the top bar and admin menus. Navigation should stay consistent in the whole admin experience. There is another similar issue in WordPress admin, but this change happened years ago. This is not a reason to reproduce such a mistake.

If this change is here to stay, it would be nice to add a modal to explain how to restore the normal mode as this is not easily discoverable for the moment.

The current mechanism to exit full screen is a “Go Back” button using the WordPress Logo that sends the user to the posts list. It is worth noting that users are not necessarily coming from the posts list, and the “go back” button (WordPress logo) is not relevant as it takes the users back to a screen that wasn’t necessarily visited before.

There is also a concern about the date on which this change was introduced. If it had been introduced during the development cycle, the Accessibility team could have provided proper information to 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/ team on the accessibility issues concerning this feature.

This change breaks the rule decided for WP 5.4: new features and enhancements can’t land during betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle. While the full-screen feature itself is not a new feature, the change to including it as the default behavior constitutes a significant change to the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. and how many users will use the editor. The related ticket was opened and merged only few hours before WordPress 5.4 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1.

If this feature is going to stay in WordPress 5.4, the accessibility team believes it will need a post mortem on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. The goal would be to avoid this situation (including changes that late in the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. cycle) being repeated in future releases and to make sure important changes introduced in WordPress are accessibility compliant.

Note also that this change was discussed in the #core Slack channel during the March 9, 2020 devchat meeting and the majority of the attendees appeared to be opposed to it. In conclusion @chanthaboune was going to give feedback to the project lead. As no decision has been communicated for now, the accessibility team assumes this change is probably going to stay in WordPress 5.4.

#core-editor, #gutenberg

Enrique Sánchez 6:34 pm on March 20, 2020
Tags:   

Accessibility Team meeting notes – March 20, 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). (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.

Discussion and next steps on the team’s position about the new default full screen mode in the editor

Continuing the discussion from two weeks ago, the team agreed to formulate in writing our position opposing this change and the accessibility implications it will have.

@audrasjb volunteered to start a document to summarize our position.

Suggest follow-up tasks and improvements for the Table blockBlock Block 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.

The team discussed and agreed to reopen this issue about missing important features in the Table block.

@joedolson volunteered to reopen and summarize what still needs to be done.

Discussion of the new permalink UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.

We discussed this issue about improvements to the permalink UI in the block editor. We feel the new UI works pretty well now and we’d like to see the inaccessible one be removed.

@nrqsnchz will pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the issue and request for the removal of the old UI.

#meeting-notes

Enrique Sánchez 7:11 pm on March 19, 2020
Tags:   

Accessibility Team Meeting Agenda: March 20, 2020

This is the proposed agenda for the weekly 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 on Friday, March 20, 2020 at 16:00 UTC

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday, March 20, 2020 at 15:00 UTC

This meeting is held in the #accessibility channel in the Making WordPress 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/. (requires registration).

#agenda

Enrique Sánchez 9:18 pm on March 13, 2020  

Accessibility Team meeting notes – March 13, 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). (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.

Discussion of changing date for WP Accessibility Day

The team discussed the possibility of changing the date for the WordPress Accessibility Day event, currently planned for Saturday, September 26. It was recently brought up that a Saturday might impact some members’ participation due to religious observance.

Considering that the other option would be to move the event to a weekday, it is unclear to us if this will also have an impact on folks who wouldn’t be able to attend due to work-related activities.

We agreed to follow up with the Community team and ask for advice.

Accessibility feedback on the new <LinkControl> component

The team was asked to help with testing and feedback on the new LinkControl component.

Accessibility feedback on a proposal to include date as context for link search results

The team reviewed this proposal to include date as context for link search results. While we don’t see adding the date as an accessibility concern, we found a couple of issues with the current UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. Our feedback was added to the issue.

Accessibility feedback on proposed improvements to the color picker.

The team discussed these proposed semantic improvements to the color picker. We don’t have a strong preference and think that using radio buttons could work with some caveats. We left feedback on the issue.

+make.wordpress.org/core/

Enrique Sánchez 6:10 pm on March 12, 2020
Tags:   

Accessibility Team Meeting Agenda: March 13, 2020

This is the proposed agenda for the weekly 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 on Friday March 13, 2020 at 16:00UTC.

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday March 13, 2020 at 15:00UTC.

This meeting is held in the #accessibility channel in the Making WordPress 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/. (requires registration).

#agenda

Enrique Sánchez 7:16 pm on March 6, 2020
Tags:   

Accessibility Team meeting notes – March 6, 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). (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.

Discussion on the accessibility implications of the recent change to the full-screen mode in the editor

The team discussed the recent change to the full-screen mode in the editor. There is a general concern about the usability and accessibility implications this new default setting will have. In particular, this change potentially violates WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.’s success criteria of Consistent navigation and Consistent identification.

@audrasjb volunteered to summarize the team’s feedback and create an issue on 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/’s GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ repository.

Planning for the upcoming start and end of daylight saving time (DST) in some countries and regions

The team agreed to not change our meeting times for the time being. We’ll revisit this topic and adjust if necessary once all countries and regions have changed DST observance.

#meeting-notes

Enrique Sánchez 6:22 pm on March 5, 2020
Tags:   

Accessibility Team Meeting Agenda: March 6, 2020

This is the proposed agenda for the weekly 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 on Friday March 6, 2020 at 16:00 UTC.

If you’d like to add an item for discussion, please add a comment and we’ll add it to the agenda.

The Accessibility bug scrub will be held on Friday March 6, 2020 at 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress 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/. (requires registration).

#agenda

Jb Audras 11:17 pm on March 4, 2020  

Accessibility Team meeting notes – February 28, 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). (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.

Improve the Handbook recommendation for abbreviations and acronyms

@afercia raised that in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket #46980, the accessibility team set some new practices for abbreviations (and acronyms). That would be relevant to add them to the Core Handbook section about abbreviations as well.

Basically:

  • Evaluate which abbreviations can be removed in favor of full text
  • For the other cases: provide an expansion of the abbreviation/acronym/neuronym in plain text on first use
  • Use an <abbr> to mark up the abbreviation (which provides a hint to user agents on how to announce/display the content)
  • Do not use title attributes

@audrasjb to touch base with the Docs team on Monday, to see how the handbook page could be improved.

Edit from Monday: the Docs team doesn’t manage the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook, it’s under Core team responsibility.

Accessibility team goals for WP 5.5

All the accessibility tickets in the 5.5 milestone can be found using this Trac query.

@joedolson noted that it would make sense to have as a goal is more aggressive work during alpha, so that we can dedicate more attention to the final product during betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. & RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge..

@afercia added that apart from bugfixes, it would be nice to have at least a couple user-facing accessibility improvements for 5.5.

@audrasjb noted that milestone 5.5 will be open for commit right after WP 5.4 Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1 is out.

The team tried to summarize the main current projects of the team for Core and to get somebody to take point on each project:

  • Accessible color schemes: Provide some accessible color schemes for WP-Admin. Milestoned to WP 5.5. Lead: @joedolson
  • Alternative WP List Tables views: Propose an alternative way to display List Tables in WP-Admin. Milestoned to WP 5.5.
  • “Howdy fly-out menu”: Refine/replace the upper-right WP-Admin fly-out menu. Milestoned to WP 5.5. Needs someone to take the lead on this task.
  • Uniform Search: Redesign of the search in WP-Admin. Milestoned to WP 5.6 as it will need a lot of work ahead of the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. development cycle.
  • WP-Admin Colors: Not milestoned for the moment.

Update on WP Accessibility Day

Quick update from @joedolson: It’s moving forward. Goal is to announce on March 25th; there’s a design in the works, so we’re on target. The website is currently under construction, thanks to @xkon. Regular meetings are hosted on #accessibility-events 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/. channel (requires registration).

Not much else to report right now. There is a budget mostly worked out, looking for sponsors to cover the captioning & transcription costs, etc.

Open floor

@joedolson: Ticket #49517 needs some discussion with the editor team, although it’s a very clear cut issue from the accessibility side.

@ellatrix is going to revert the related pull request on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/.