There are changes coming to the ticket selection table, order summary, registration form, and edit form to improve the 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) of registering for a WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.. The changes will deploy Launching code from a local development environment to the production web server, so that it's available to visitors. tomorrow, March 3rd, around 16:00 UTC.
Right now, most form fields didn’t have an “accessible name”, instead the form relies on the table layout to show which question corresponds to each input. This only works for sighted users— for anyone using a screen reader, the form fields are functionally unlabelled.
After this change, all inputs will have labels attached, so screen readers and other assistive tech will be able to connect the questions (for example, First Name) to the text input for the answer. This also changes some of the markup, which might affect your WordCamp’s style, if you have any custom CSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site..
- All ticket questions are now wrapped in a
- All inputs have a unique ID (but this should not be used for styling)
- Questions with multiple answers (radio buttons or checkboxes) now have their answers wrapped in a
The ticket selection table has also been updated so navigating through selecting a ticket is easier.
- The quantity dropdown now uses the ticket name as the label
- The ticket name is now wrapped in a
label, instead of
strong, and that table cell is now a
th instead of
This fixes meta 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. ticket #1591, you can see the full changes on the GitHub PR. Please check your tickets page, especially if you’ve done any custom styling to it, and let us know in #meta-wordcamp on 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 here in the comments) if you see anything unexpected.
The task that was assigned to be at WCEU WordCamp Europe. The European flagship WordCamp event. was to draft documentation for the Camptix Notify functionality of WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. sites, including some notes on the date format for the Purchased Date field in the filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. conditions.
I’ve tried to keep the documentation as non technical as possible, but as a developer I would appreciate feedback from the rest of the community.
I therefore ask anyone interested to review the document via Google Drive and leave your comments/suggestions on this post so that we can discuss changes or improvements.
I’d like to give this a two week deadline for comments until Friday the 13th (dun dun dun!) of July, in order to move the process of having this included into the WordCamp docs along promptly.
I have a couple of observations about CampTix that I’d like to share with the team.
This is the first year we have used CampTix for WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Sydney and we have received quite a lot of queries from attendees asking 1) can we send them a proper invoice? and 2) where is my ticket?
1) There are no tax or currency on this receipt and the title of the email is “Your ticket to WordCamp Sydney 2016”. It’s not very intuitive that this is an invoice and not very helpful for claiming tax back as a business expense. It looks more like a payment notification. Perhaps the design could be tweaked to make it look more like an invoice.
There is also no way to regenerate this email if say the email gets intercepted by spam filters and the recipient never gets it. We tell them to login to their PayPal account and print the transaction but I’m sure it would be super easy to add a button to resend receipt/invoice.
2) where is my ticket?
The email’s title is “Your Ticket to WordCamp Sydney 2016”, however the body of the email looks more like a notification of purchase rather than a ticket.
We’ve had about 60 people saying that their ticket was not emailed, only to figure out that they didn’t realise that email was their ticket.
It could be due to the fact we’ve use eventbrite in the past which emails attendees something that looks like a conference ticket that they can print out and bring with them (name, event title, date, ticket type etc).
I’m sure the CampTix email could be designed better to make it look like an actual ticket.
Heads up! Today we’re changing the PayPal account that’s connected to CampTix from the account owned by the WordPress Foundation The WordPress Foundation is a charitable organization founded by Matt Mullenweg to further the mission of the WordPress open source project: to democratize publishing through Open Source, GPL software. Find more on wordpressfoundation.org. to an account owned by the Foundation’s subsidiary, WordPress Community Support WordPress Community Support PBC is a subsidiary of WordPress Foundation. It is created specifically to be the financial and legal support for WordCamps, WordPress Meetup groups, and any additional “official” events organized within the WordPress Community Events program., PBC.
Since we have already talked to PayPal about making this switch, they know to expect high volume on this new account, and we don’t anticipate any issues with payment processing for WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. tickets. If you notice issues with ticket purchasing, please notify us in wordpress.slack.com in the #meta-wordcamp channel, and we’ll investigate.
This change will, unfortunately, break self-serve refunds for folks who have purchased tickets in the past 2 months. We’re going to handle those refunds manually. This will be inconvenient, but we think the hassle is worth the benefit of creating a clean financial break with the Foundation for ticket revenue.
As of today, if you are contacted by an attendee requesting a refund for a ticket purchased between 1/1/2016 and 3/1/2016, please email email@example.com with the following info:
Purchaser’s email address:
PayPal Transaction ID for the ticket purchase:
Date of the ticket purchase:
Date of the event:
As long as the ticket purchase happened between between 1/1/2016 and 3/1/2016 and the refund request came in before the event, we will refund the ticket within a week of receiving the email to firstname.lastname@example.org. We’ll probably do refunds in batches on a weekly basis, I’m guessing on Fridays. 🙂
Got a question? Ask in the comments!