After a few months of having a test session on Monday’s we gathered a group of people discussing and fixing tickets and patches.
But limiting the testing to a weekly one hour session turns out to be not pracical.
Not eveyone has the time to be there and work on that exact hour, we are a global group.
@afercia is doing a ton of work on the tickets at the moment and we need more testing and more feedback.
So here’s a proposal for making better use of our time, coders and testers.
The Monday session will be a meeting to discuss the tickets/patches, like:
- what are tickets we need to work on, what has priority
- what tickets have a working, tested patch and needs dev feed back or assigned a milestone to
- what tickets need to be tested and on what AT and who can we ask for that
- what are the test results, and can we change / approve a patch
- people can ask for functionally to test or ask questions on how to fix stuff
Then after/during the test session we can install a patch on the test server in the trunk website and assign testers.
During the week the testers can look at the changes and report back as a comment with the ticket or to the #a11y team in slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. or by e-mail. Then everyone can test in their own time, we can give specific small tasks to test.
We can also ask the testers to look at specific functionality in the current version of WP to find what’s wrong or needs to be changed.
In this meeting we discussed:
Ticket #28599 (Better Visual Focus Indication in Admin Menu): This ticket has a working patch and needs dev and designers feedback. @ryan will also take a look at it this week. In it’s current state the patch is’t ready for production, for example it misses all the parts related to color schemes and SASS.
Ticket #30589 (Comments navigation template tags): We discussed if the landmark <nav> is appropriate for the comment navigation, <nav> is meant for main navigation. Now there is a risk that we overload a theme with nav’s @afercia will respond to that ticket with outline examples in Twenty Fifteen.
Ticket #29955 (Section 508 issues found on WordPress 4.0 admin page): This ticket will be closed and divided it into new separated tickets.
The patch on the test server this week will be for Ticket #28599 (Better Visual Focus Indication in Admin Menu). If you want to join in the testing, please contact @rianrietveld.
Screen Reader Text support:
This is an ongoing discussion and commented on by some of us in:
In the codex WordPress Generated Classes there is an example on how to implement the screen-reader-text class. We advice to remove the
.screen-reader-text:hover,
.screen-reader-text:active,
because they have no use in this context. Just keep the focus.
Clip is due to be deprecated in favor of clip-path, but clip-path is not very well browser supported yet. So lets stick to clip for the time being. Maybe a note of that in the codex will be useful.
@joedolson will discuss a11y 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) with @drewapicture this week, we also hope to get more dev feedback on some of the patches.
In the weekly Accessibility 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) Chat next Wednesday we want to discuss ticket priority.
#weekly-meetings
