Accessibility meeting agenda for 10 May 2019

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 10 May 2019 at 15:00.

  • WPCampus Accessibility Audit: discussion about how to organize both 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/, Accessibility and Design teams to handle accessibility issues (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/ issues but also fundamental issues found in the editor).
  • 5.3: main accessibility goals.

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 10 May 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

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).

Accessibility meeting agenda for 3 May 2019

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 3 May 2019 at 15:00

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 3 May 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

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).

X-post: 5.0 Release Retrospective Wrap Up

X-comment from +make.wordpress.org/updates: Comment on 5.0 Release Retrospective Wrap Up

Accessibility Meeting Notes for 4/26/2019

Meeting transcript on Slack

1) WordPress 5.2 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 work statement

Nobody was clear on what this was about, but believe that it may have been in reference to the accessibility team update published by @audrasjb on April 21st. Assuming it is, and moving on.

2) User Input Validation

Tickets have been raised recently that address this, and it’s something that we should handle much better throughout WordPress. Input validation and error reporting are addressed in two 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, both within the parameters we’re committed to meeting (Level A and AA.)

@greatislander will create a tracking ticket to get this started. It’s probably a large project to tackle, but having a ticket to reference for future planning is useful.

4) Update on Automated Testing

@greatislander Requested a change in agenda order. Based on feedback from @rianrietveld after WordCampWordCamp A WordCamp is a conference where the WordPress community come together to teach one another what they’ve learned throughout the year and share the joy. https://central.wordcamp.org/about/. London, is exploring ways of producing a more usable list of output. Currently, tests produce a massive quantity of terminal text. Need to reduce the scope of tests run at once and/or generate a reference file that can be used outside of terminal.

3) Uniform Search planning

@joedolson and @nrqsnchz worked on documenting the current user experience on each search model. Progress is being tracked on Google docs.

Next step is to elaborate the basic outline produced in the first phase to incorporate the assistive tech experience.

Noted that while the original project scoped 5 independent search experiences, changes to WordPress since the tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket was created have reduced this to 4. Yay!

5) Update on User Docs

While nobody had time to follow up on this during the week, @bemdesign noted that @chrisvanpatten posted a brief comment in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor 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 noting that progress is finally moving forward again.

6) W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. Alt Decision tree

Finalized decisions: We are going to copy the decision tree into the WordPress A11yAccessibility 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) handbook, then begin sourcing translations.

Question was raised whether we will share translations with the W3C – and yes, we will.

@audrasjb has volunteered to tackle the copying process.

7) Updated accessibility ticket spreadsheet

@nataliemac worked on updating the accessibility ticket spreadsheet, confirming resolution on numerous tickets.

Accessibility meeting agenda for 26 April 2019

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 26 April 2019 at 15:00

  • WordPress 5.2 Accessibility Team work statement (@audrasjb)
  • Discuss user input validation (see #47018) (@afercia)
  • Update on Uniform Search progress (@joedolson, @nrqsnchz)
  • Update on Automated testing (@greatislander)
  • Update on User Handbook (@karmatosed)
  • Continuing discussion: strategies for use of the W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. alt decision tree in translations. (@joedolson, @afercia)
  • Open Floor

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 26 April 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

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).

Accessibility Meeting Notes for 19 April 2019

Meeting transcript on Slack

Welcomed new contributors

Welcomed and got introductions from Enrique Sanchez & @nataliemac; gave them an introduction to 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 purview and operations.

1) WordPress 5.2 Accessibility Team work statement

@joedolson didn’t know what the intent behind this agenda item was, so tabled for next week.

2) WordPress 5.3 Goals

Reviewed goals for 5.3. @nataliemac will review & update spreadsheet of priorities. Enrique Sanchez volunteered to help with planning on Uniform Search.

3) Update on Automated Testing

@gziolo has made a pull request to incorporate Axe testing into 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/ e2e suite. Pending review.

4) Update on User Handbook

Discussed whether we should publish @abrightclearweb‘s documentation into our Handbook, since it’s now mid April and we still have no updates on user documentation.

Laid out scope of what this would take, which is significant.

@karmatosed will follow-up to try and get something moving next week. It would be preferable to not have to reduplicate this work, but we feel strongly that it needs to be published.

5) Continuing Discussion: W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. alt decision tree

Tabled due to shortage of time.

6) Update on Accessibility Team/Contributors Badges

All badges have been updated per discussion last week.

Accessibility meeting agenda for 19 April 2019

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 19 April 2019 at 15:00

  • WordPress 5.2 Accessibility Team work statement
  • WordPress 5.3 goals
  • Update on Automated testing
  • Update on User Handbook
  • Continuing discussion: strategies for use of the W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. alt decision tree in translations.
  • Update on Accessibility Team/Contributors badges assignment
  • Open Floor

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday 19 April 2019 at 14:00 and will be focused on WordPress 5.3 milestone.

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).

X-post: The Get Involved table at WCEU 2019

X-comment from +make.wordpress.org/community: Comment on The Get Involved table at WCEU 2019

Accessibility Meeting Notes for 12 April 2019

Continue discussion on WP.org profile badges

Reviewed criteria for Team/Contributor badges for the team:

1) Team badges:

  • Past team leads
  • Regular participation in meetings (at least once per month)
  • Leadership role
  • Writing documentation
  • Leading code contributions (project management for major tasks, significant code written, etc.)

2) Contributor Badge:

  • Occasional meeting participation
  • Code contributions 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/ or TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. (bug reporting, testing, and patching)
  • Assisting in 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) Support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. https://en.forums.wordpress.com/.
  • Performing A11yAccessibility 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) Theme Reviews

3) Update cycle

  • Badge assignments will be reviewed in mid April and mid October each year, and will be based on participation during the prior 6 months.

Additionally, we reviewed the badge assignments for the Accessibility team and contributors throughout the project. We believe that this is now up to date according to the above criteria.

If you’ve contributed to WordPress Accessibility and you do not have a badge assigned, please comment below and let us know! We assembled a lot of this from memory and searching through trackers, metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. activity, and 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/. conversations. It was definitely not an infallible process.

If the reason you don’t have an Accessibility badge is because your contribution isn’t covered by the above criteria, please let us know that, as well! The criteria are open to changes.

Open Floor

@greatislander Wanted to address an small accessibility improvement that we could add to the Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. immediately, since getting the complete API revamp is stalled at the moment. Team agreed that adding role="presentation" to make the settings tables presentational is probably a good choice, though we’ll want to test it.

Note

We got through only one item on our scheduled agenda for this week, since we spent most of the team getting our badges up to date. We’ve committed to a 6 month review cycle for badges, so that we never spend that much time on it again…

The rest of this week’s agenda will be addressed next week.

Accessibility meeting agenda for 12 April 2019

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, April 12, 2019 at 15:00.

  • Continue discussion on WP.org profile badges
  • Update on Automated testing
  • Update on User Handbook
  • Continuing discussion: strategies for use of the W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. alt decision tree in translations.
  • Uniform Search
  • Open Floor

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday, April 12, 2019 at 14:00.

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).