Accessibility Meeting Notes for 4/26/2019

Meeting transcript on Slack

1) WordPress 5.2 Accessibilitya11y Accessibility (https://a11yproject.com/). A11y is an acronym for accessibility. The 11 represents the 11 letters that were removed between the a and y to make accessibility shorter to write particularly on social media. 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 A11ya11y Accessibility (https://a11yproject.com/). A11y is an acronym for accessibility. The 11 represents the 11 letters that were removed between the a and y to make accessibility shorter to write particularly on social media. 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.